T
Tim Moen
We get the error: "The server was unable to find a free
connection 10 times in the last 60 seconds." "It's event
id 2022" on one of our 2000 servers. The number of times
varies. Also, when other computers try to connect to
shared drives, it hangs for a while and then give the
error, "\\<servername> is not accessible. The network
path was not found. At net view \\<servername> comes back
with a 'system error 53 has occurred. The network path
was not found.'
When you 'ping <servernam>' it works just fine. Telnet
connections and WinVNC both work to this server. A web
server that connects to a database on this server works
also.
While on this server net view works as well as looking at
directories shared on other servers.
Does anyone have any idea why this is happening? After a
reboot everything works fine for about an hour or so.
Other machines can see the drives, but then it goes down.
On the Microsoft support site on article says something
about "This behavior occurs because the Server service is
unable to keep up with the demand for connections. " and
gives a registry edit solution. I'm not so sure about
this. It also mentions LanmanServer.
connection 10 times in the last 60 seconds." "It's event
id 2022" on one of our 2000 servers. The number of times
varies. Also, when other computers try to connect to
shared drives, it hangs for a while and then give the
error, "\\<servername> is not accessible. The network
path was not found. At net view \\<servername> comes back
with a 'system error 53 has occurred. The network path
was not found.'
When you 'ping <servernam>' it works just fine. Telnet
connections and WinVNC both work to this server. A web
server that connects to a database on this server works
also.
While on this server net view works as well as looking at
directories shared on other servers.
Does anyone have any idea why this is happening? After a
reboot everything works fine for about an hour or so.
Other machines can see the drives, but then it goes down.
On the Microsoft support site on article says something
about "This behavior occurs because the Server service is
unable to keep up with the demand for connections. " and
gives a registry edit solution. I'm not so sure about
this. It also mentions LanmanServer.