Windows 2000 server not accepting new smb connections

  • Thread starter Thread starter arkman
  • Start date Start date
A

arkman

Periodically over the last two weeks, one of our windows 2000 servers
has stopped accepting new SMB connections. Existing connections
continue working fine. Other services like apache work fine. I
can't even map a local share on the server itself. Rebooting fixes
the issue.

Clients that were connected but timed-out receive "The local device
name is already in use". When attempting to make a new connection in
explorer, I get repeated password prompts. When connecting using NET
USE in dos, I get a password prompt then "System error 53 - network
path was not found".

There are no messages in the event log. There are no run-away
processes in the task manager. It looks like the system is clean of
viruses or trojans.

I don't believe it's a "network" issue since existing
connections continue to work and other services act normally.
 
Update: Last night I applied a nic driver update through windows
update. This fixed the issue without rebooting.

I have a hunch that restarting the network subsystem fixed it as
opposed to the new driver fixing it - but I'm holding out hope that
maybe it was as simple as a driver.

Either way, I'm definately interested in other solutions or ways to
furthur analyze or troubleshoot the problem.
 
Back
Top