System error 53

[Steve Jenkins]

Hi,
Wonder if anyone can help.

We have one Windows 2000 Advanced Server domain controller,
MAINSERVER, which is our fileserver. We are getting a problem along

the following lines:

- Periodically, Windows users cannot "see" MAINSERVER, i.e. if they
type "\\MAINSERVER" on a Windows client (Windows 2000, XP,

whatever - all get the same error), they get the error "path not
found".

- In a console window of Windows client typing "net view \\MAINSERVER"
produces the error: "System error 53 has occurred" -

error message displayed in the console window.

- To fix this, we go to MAINSERVER, disable the OURDOMAIN card,
re-enable and we can gain access again. Rebooting has the same

effect.

- When we cannot type "\\MAINSERVER" and get access:
----- We can type "ping MAINSERVER" and see it.
----- We can type:
net use \\ServerIP
net use * \\ServerIP\share

and we *can* access the server.

----- Typing:
nbtstat -R
ipconfig/displaydns

Attempt the following commands:
net use * \\ServerName\share
nbtstat -c
ipconfig/registerdns

makes no difference whatsoever.


- When we cannot get access, if we type:
nbtstat -n on MAINSERVER, we get the following:

Name Type Status
---------------------------------------------
MAINSERVER <00> UNIQUE Registered
MAINSERVER <03> UNIQUE Registered
OURDOMAIN <00> GROUP Registered
OURDOMAIN <1C> GROUP Registered
MAINSERVER <20> UNIQUE Registered
OURDOMAIN <1E> GROUP Registered
OURDOMAIN <1B> UNIQUE Registered
OURDOMAIN <1D> UNIQUE Registered
..__MSBROWSE__.<01> GROUP Registered



- Anyone any ideas what's going on? Might this be caused by a virus or
something? Could it be the OURDOMAIN card?

 

[Jetro]

Answered in networking NG.