Net View works, then sometime later returns error 53, reboot router, works again.

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Net View works, then sometime later returns error 53, reboot router, works again.
Net View works, then sometime later returns error 53, reboot router, works again.
2021-01-27 18:47:24
Model: Archer A20
Hardware Version: V1
Firmware Version: 1.1.1 Build 20191026 rel.10453(5553)

OK, I've got an ODD problem, and it could be router connected.

 

In a nutshell, I lose NetBios connection (I think) to the router sometime after I boot the PC. Rebooting the router 'reconnects' them and NET VIEW again works.

 

Details:

 

===============

On W10 2h20 with all the latest fixes as of today.

Don't know when this has started, but it is annoying.

Only 2 PC's on the network LAN and a Printer (wireless) at this time.

Just booted right now and it does work:

=================
C:\>net view
Server Name Remark

--------------------------------------
\\HP7855 Samba 3.0.37
\\IRV8700 Irv's 8700
\\TP-SHARE samba server
The command completed successfully.
==================

I've started the other computer and it still works:

===================
C:\>net view
Server Name Remark

---------------------------------------------
\\HP7855 Samba 3.0.37
\\IRV8700 Irv's 8700
\\LA-XPS8500 La XPS8500
\\TP-SHARE samba server
The command completed successfully.
==================

Sometime during the day it will not and I get an ERROR 53. NET VIEW on other PC still works fine?

If I reboot, it again works. If I just reboot the router, it again works.

Don't know when it actually stops working?

I've searched the web for the error 53 and none of the pages help or address this?

As far as I can tell, it started around the time of the 2h20 update? I am focusing on my PC alone, not the other one. I think it never has a problem. My PC is running the HOME version, the other PRO.

I've done the NBTSTAT -RR as well. Only the ROUTER reboot or this PC reboot fixes it it seems? Since this is a wireless PC I even switched SSID's and it doesn't help?

 

Right now, since it is working, I can use the NetBios names:

===========
C:\>net view
Server Name Remark

-----------------------------------------------------------
\\HP7855 Samba 3.0.37
\\IRV8700 Irv's 8700
\\LA-XPS8500 La XPS8500
\\TP-SHARE samba server
The command completed successfully.

C:\>ping tp-share

Pinging tp-share [192.168.0.1] with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3ms, Average = 2ms
====================

This what I see now using Explorer:
 
 
I have no control how the Router (TP-SHARE) or the HP printer is discovered. Both PC's are using WSD in Windows as well as NetBios SMB 1 is enabled.
 
I waited a few hours, and it has now failed, get the error using NET VIEW.
 
Never had a problem before, and it is 'back' now...

CMD prompt copy:

============================
C:\>net view
System error 53 has occurred.

The network path was not found.


C:\>ping tp-share

Pinging tp-share [192.168.0.1] with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

C:\>net view \\tp-share
System error 53 has occurred.

The network path was not found.


C:\>net view \\192.168.0.1
System error 53 has occurred.

The network path was not found.


C:\>net view \\192.168.0.166
Shared resources at \\192.168.0.166

Irv's 8700

Share name Type Used as Comment

-----------------------------------------------------------
C_8700 Disk
K_disk Disk
L_disk Disk
Users Disk
The command completed successfully.

===================

All the shares have no blanks or special characters. Besides, why would it work and then someone not work later?

Really odd, my PC knows where tp-share is but I can't 'net view' to it, but I can PING it with the share name of the router?

Of course, once I reboot the router it will work again.

No, nothing changed on the router (TP-LINK Archer A20), same f/w and no changes anywhere made for a long time.

I can even net view to the other PC using the share name:

================
C:\>net view \\la-xps8500
Shared resources at \\la-xps8500

La XPS8500

Share name Type Used as Comment

-----------------------------------------
C_disk Disk
D_Drive Disk
E_Drive Disk
F_Drive Disk
Users Disk
The command completed successfully.
=============

Makes no sense to me? It can resolve NetBios names, but it seems only NET VIEW has a problem? Suspect somehow the Router to PC NetBios connection has been lost? However I can access the Router's GUI fine?

Just checked the other PC, same problem, Error 53?
 
Router IS on a UPS, and I last rebooted it YESTERDAY trying to so some debug on this.
 
I wonder if I need to do the RESET on router or there is someother problem? I would save the settings before doing the RESET but I am reluctant to do that as restoring the settings could bring the problem back. Other thought is a router failure?
0
0
#1
Options
9 Reply
Re:Net View works, then sometime later returns error 53, reboot router, works again.
2021-01-28 19:38:44

@IrvSp 

 

Usually, this is seen on accessing NAS storage files.

 

Have you tried accessing the router files with FTP?

 

Even though your computer is able to see the other computer shares it doesn't seem like the computer can't see anything which is odd.

 

Have you tried the potential fixes such as:

-Disabling IPV6 for your network card? (ignore if you are using IPv6)

-Checking the firewall settings if the computer has any such as McAfee or Norton?

 

Do you happen to have another router to see if the issue still happens?

0
0
#2
Options
Re:Net View works, then sometime later returns error 53, reboot router, works again.
2021-01-28 20:02:20

@Tony 

 

Thanks for the reply.

 

" Usually, this is seen on accessing NAS storage files."

 

Although I do have a USB drive on the 3.0 port, I'm not accessing normally. Used basically as a Media Server and an occasional transfer of some files from a PC to it. Possible when I open Explorer it could do that, but when I open up 'Network' it clearly is the only time it tries to access the router? Doesn't explain why a REBOOT of the router fixes it either? USB drive has been on the Router since Day one over a year ago with this not happening until recently?

 

" Have you tried accessing the router files with FTP? "

 

No, but my iPad using a DLNA client has no problem accessing the USB drive.

 

"

 

Have you tried the potential fixes such as:

-Disabling IPV6 for your network card? (ignore if you are using IPv6)

-Checking the firewall settings if the computer has any such as McAfee or Norton?"

 

Yes, IPv6 is enabled and has been for quite awhile. Doesn't explain why it is working and then isn't?

 

Matter of fact, it is working now,

 

=============

C:\>net view
Server Name            Remark

-----------------------------------------
\\HP7855               Samba 3.0.37
\\IRV8700              Irv's 8700
\\LA-XPS8500      La XPS8500
\\TP-SHARE             samba server
The command completed successfully.

============

 

Has been working fine since I rebooted the A20 just before Noon EST today:

 

 

3 hours later and still working?

 

If a Firewall or even a Security suite was the problem, wouldn't it always be a problem?

 

" Do you happen to have another router to see if the issue still happens? "

 

Yeah, have one (not a good). Didn't think of that? Maybe I'll do it?

 

I am really stumped here, never heard of this, an Google searches turn up nothing about it being intermittant.

 

I've already ruled out the Network drivers and I've used both wire and wireless with the same problem. Problem exists on 2 PC's we have (only 2 we have), and one is a Home edition, the other Pro.

 

When the problem is noticed, both PC's have the problem.

 

 

0
0
#3
Options
Re:Net View works, then sometime later returns error 53, reboot router, works again.
2021-01-28 23:51:56

@IrvSp 

 

Right now it is difficult to really narrow down where it might be coming from.

 

I would probably try various things as it may work, but more or less one less thing to exclude.

 

If you do have the other router, that would help so the focus can be on the A20. 

0
0
#4
Options
Re:Net View works, then sometime later returns error 53, reboot router, works again.
2021-01-29 12:50:14

@Tony 

 

I'll switch routers later, but it was ROCK SOLID yesterday after rebooting.

 

My 'logic' I'm working under is 'something' changed recently. I've never known a router cause something like this either. Google searches get no hits. So it had to be unique to out h/w and usage.

 

Usually I'm the first up and powering up my PC. Wife's powered up after mine. Since this happened a month or two ago, I've been checking daily first thing after powering up running NET VIEW. Always works, randomly I'd check later and at some point it fails.

 

I'll usually notice the fail when I have to get or put something on her computer. I'll use Windows Explorer and open NETWORK. When NET VIEW has failed, I might only see her PC under NETWORK or just our 2 PC's. Router and Printer do not appear.

 

Just can't understand how this 'breaks'? Her PC, my PC, router? Has to be one or some combo. A combo would be an operation, but that is very rarely using the USB drive on the router?

 

I have NO PROBLEMS now, I can use Explorer to look at her PC and read files at this time and NET VIEW still works?

 

I did make 2 PC changes, and one I'm sure wasn't needed.

 

  1. On both PC's I enabled the SMB 1 Server feature. It isn't really needed, and that is the feature that has the most exposure to exploits. I was thinking some MS change might require that to keep SMB 1 working between PC's? Normally the LAST computer up will become the MASTER BROWSER who keeps the NetBIOS names list which is needed for NET VIEW. When ALL PC's are off, the Router holds that. First PC that turns on gets than and becomes the MASTER BROWSER (at least that is how I recall it worked?). So I hoped that would fix it.
  2. When enabling that on my wife's PC I see something I had NOT seen before, SMB Direct was enabled under SMB 1? NEVER saw that before? That is appears is a Windows Server feature. I disabled that. Wonder if this is a Window 10 2H20 addition? Would fit the timeframe of my problem starting?

 

Since making those changes and rebooting the router I've NOT seen the problem?

 

After today, and I'll be checking often, if there is no problem, I'll uncheck SMB 1 Server on each PC and test the next day. I'm hoping that one feature was the cause. If not, I'll put back my garbage Netgear R8000 and test. Right now, I'm not sure it is the router at all.

0
0
#5
Options
Re:Net View works, then sometime later returns error 53, reboot router, works again.
2021-01-29 23:09:14

@Tony 

 

Looks like the changes I made have made a difference.

 

Up 11 hours and it has not had the error!!!

 

Although this is old, https://www.reddit.com/r/sysadmin/comments/8lwgne/smb_direct_windows_10_1803_affecting_printers_and/?ref_source=embed&ref=share, the link has basically the same problem and pointed a finger at SMB Direct being enabled?

 

I do NOT recall seeing that enabled before though?

 

I suspect that was the culprit here. Certainly not the router. Have no clue why rebooting the router fixed it, unless it forced everyone to reconnect. First use of the router via a GUI probably broke SMB 1 connections I assume.

 

I might test in a day or two turning it back on to verify.

2
2
#6
Options
Re:Net View works, then sometime later returns error 53, reboot router, works again.
2021-02-01 17:04:23

@IrvSp 

 

Well, problem back, seems as long as my wife's PC is the First to turn-on (the PRO PC) I have the problem now. With SMB Direct feature on on that PC, the problem exists all the time.

 

Something about that PC and NetBios support is probably the cause I'll assume?

 

I'll have to live with this if it is, until MS fixes it, but I can't find any other reports like this on the web?

 

Doubt it is the router, but I'll probably swap it out later when I'm ready to attack this problem more. Almost resigned to this is what it is now.

0
0
#7
Options
Re:Net View works, then sometime later returns error 53, reboot router, works again.
2021-02-01 22:03:53 - last edited 2021-02-01 22:06:44

Well, it is back unfortunately.

 

As far as I can tell, at least now without any way I can think of further debugging this, is that the Router is the common component that when rebooted the problem goes away immediately and possibly over a few days? This morning my wife's PC W10 Pro was booted first, mine later, and we both get the fail:

 

===================

 

C:\>net view System error 53 has occurred.

The network path was not found.

C:\>

============

 

Rebooting router now....

==================

C:\>net view

Server Name Remark

------------------------------------

\\IRV8700 Irv's 8700

\\TP-SHARE samba server

The command completed successfully.

====================

 

It does take time for all devices (wife's PC and Printer) to appear. They did by the time I put the above in:

 

============

C:\>net view

Server Name Remark

-----------------------------------------

\\HP7855 Samba 3.0.37

\\IRV8700 Irv's 8700

\\LA-XPS8500 LaXPS8500

\\TP-SHARE samba server

The command completed successfully.

==============

 

This IS NOT a new router, 16 months only, no new f/w either? Could the router be running out of RAM/Resources? All of a sudden?

0
0
#8
Options
Re:Net View works, then sometime later returns error 53, reboot router, works again.
2021-02-02 23:40:11

@IrvSp 

 

I'll see what I can find for you given the information you provided.

0
0
#9
Options
Re:Net View works, then sometime later returns error 53, reboot router, works again.
2021-04-29 01:24:30

@IrvSp Thanks for the detailed reply.  What I observe is similar to what you observe when your router becomes ill. 

 

Summary of my observations:

 

  • I have never had intra-LAN connectivity with the new AX50 router; re-booting does not fix the issue.
  • Net view command without option(s) returns the originating computer only
  • System error 53 is the result for every net view inquiry, including when the router IP address is used
  • The router responds to a ping, but no other device on the network responds to ping

 

 

 

0
0
#10
Options