Net View works, then sometime later returns error 53, reboot router, works again.
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?
===========
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:
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?