Workstations lose network connection

[Guest]

We have a small office with one server which runs Win2000. We have 7
workstations and all but one are running XP Pro (other runs Win2000). All
have updates installed (except IE7). Most of the machines lose their
connection to the server daily. Generally a reboot will reconnect the
workstation, although some times several reboots are required. Often if we
cannot reach the server we can still access the internet. The server
connects to a linksys router w/ switch, which connects to both the actiontec
dsl modem & linksys switch that patches the server upstairs to the
workstations downstairs.
Any ideas would be helpful!

 

[Chuck]

We have a small office with one server which runs Win2000. We have 7
workstations and all but one are running XP Pro (other runs Win2000). All
have updates installed (except IE7). Most of the machines lose their
connection to the server daily. Generally a reboot will reconnect the
workstation, although some times several reboots are required. Often if we
cannot reach the server we can still access the internet. The server
connects to a linksys router w/ switch, which connects to both the actiontec
dsl modem & linksys switch that patches the server upstairs to the
workstations downstairs.
Any ideas would be helpful!

Chelsea,

OK, you have 8 computers, 6 Windows XP Pro, one Windows 2000 is a client, one
Windows 2000 is a server. Is the server a domain controller, or just a file
server?

Do the computers lose connectivity to the server only? Do multiple computers
lose connectivity simultaneously? Are the computers from the same, or
different, vendors?

Define "lose connection". Can't access files, can't connect to shares, can't
ping by name, can't ping by IP address?
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html

From your problem description, I'd suspect multiple problems. You may need to
attack the problems using a layered problem analysis.
<http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html>
http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html

I'd start by checking for the "power down the Ethernet adapter when idle"
setting.
<http://nitecruzr.blogspot.com/2005/06/does-your-computer-lose-network.html>
http://nitecruzr.blogspot.com/2005/06/does-your-computer-lose-network.html

Then, define "lose connection". Can't access files, can't connect to shares,
can't ping by name, can't ping by IP address?
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html

 

[Guest]

Thanks for your reply.

Chelsea,

OK, you have 8 computers, 6 Windows XP Pro, one Windows 2000 is a client, one
Windows 2000 is a server. Is the server a domain controller, or just a file
server?

The server is just a file server - it has our quickbooks file on it, which
everyone needs access to.

Do the computers lose connectivity to the server only?

Sometimes - we cannot connect to the server through quickbooks, but can
access the internet. Reboot usually fixes.
Do multiple computers

lose connectivity simultaneously?

No - usually someone cannot connect while everyone else is OK. It doesn't
seem to be related to a particular numbers of users attached, either.
Are the computers from the same, or

different, vendors?

All the new computers are Dells - three laptops and three workstations. The
older computer is a no brand.

Define "lose connection". Can't access files, can't connect to shares, can't
ping by name, can't ping by IP address?

We can't access files or connect to shares, but I think I can ping by IP.
When trying to connect I used to get a message about the time not being
in-synch, but I think I have fixed that.

<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html

From your problem description, I'd suspect multiple problems. You may need to
attack the problems using a layered problem analysis. I will review this - thanks.
<http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html>
http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html

I'd start by checking for the "power down the Ethernet adapter when idle"
setting.

I have unchecked the box in question on all the workstations - all the
laptops connected this AM w/o problem. But one of the other workstations
still required a reboot to connect.

 

[Chuck]

Thanks for your reply.


The server is just a file server - it has our quickbooks file on it, which
everyone needs access to.
Sometimes - we cannot connect to the server through quickbooks, but can
access the internet. Reboot usually fixes.
Do multiple computers
No - usually someone cannot connect while everyone else is OK. It doesn't
seem to be related to a particular numbers of users attached, either.
Are the computers from the same, or
All the new computers are Dells - three laptops and three workstations. The
older computer is a no brand.
We can't access files or connect to shares, but I think I can ping by IP.
When trying to connect I used to get a message about the time not being
in-synch, but I think I have fixed that.
I have unchecked the box in question on all the workstations - all the
laptops connected this AM w/o problem. But one of the other workstations
still required a reboot to connect.

Without seeing the exact text of the "cannot connect" message, but looking at
your population, I'd say 6 or 7 clients could possibly populate a 10 incoming
connection limit in Windows 2000.
<http://support.microsoft.com/kb/122920/>
http://support.microsoft.com/kb/122920/

So, I'll bet that you have exceeded the limit. Unless you're running Server
2000, and then I'd ask how many licenses you have. You can use the Shared
Folders wizard on the server, and next time one computer loses connection, take
a look at what connections are open.
<http://nitecruzr.blogspot.com/2006/09/know-whos-accessing-server.html>
http://nitecruzr.blogspot.com/2006/09/know-whos-accessing-server.html

If it is a maximum connections limit problem, try reducing the timeout period.
<http://nitecruzr.blogspot.com/2005/07/server-availability-affected-by.html>
http://nitecruzr.blogspot.com/2005/07/server-availability-affected-by.html

And if the server is running Professional 2000, get a real server OS. If it's
Server 2000, get more licenses.

 

[Guest]

Without seeing the exact text of the "cannot connect" message, but looking at
your population, I'd say 6 or 7 clients could possibly populate a 10 incoming
connection limit in Windows 2000.
<http://support.microsoft.com/kb/122920/>
http://support.microsoft.com/kb/122920/

So, I'll bet that you have exceeded the limit. Unless you're running Server
2000, and then I'd ask how many licenses you have. You can use the Shared
Folders wizard on the server, and next time one computer loses connection, take
a look at what connections are open.

We are running Server 2000 - next time someone cannot connect I will check
the connections. I have just connected all three laptops and three
workstations successfully...

<http://nitecruzr.blogspot.com/2006/09/know-whos-accessing-server.html>
http://nitecruzr.blogspot.com/2006/09/know-whos-accessing-server.html

If it is a maximum connections limit problem, try reducing the timeout period.
<http://nitecruzr.blogspot.com/2005/07/server-availability-affected-by.html>
http://nitecruzr.blogspot.com/2005/07/server-availability-affected-by.html

And if the server is running Professional 2000, get a real server OS. If it's
Server 2000, get more licenses.

Thanks for your input - this has helped. We may just need more licenses.
How can I tell how many we have?
The machine running server 2000 is getting quite outdated and I would like
to eliminate it altogether soon. If I have a new dedicated Dell running XP
and everyone configured peer to peer to access the shared quickbooks file on
that machine, should I have any problems?

 

[Chuck]

We are running Server 2000 - next time someone cannot connect I will check
the connections. I have just connected all three laptops and three
workstations successfully...
Thanks for your input - this has helped. We may just need more licenses.
How can I tell how many we have?
The machine running server 2000 is getting quite outdated and I would like
to eliminate it altogether soon. If I have a new dedicated Dell running XP
and everyone configured peer to peer to access the shared quickbooks file on
that machine, should I have any problems?

Chelsea,

Assuming that everybody wouldn't connect to everybody else's share every time,
making the entire LAN into one big distributed server would make sense.

Except for the administration headache. I speak from experience here - one of
the most interesting (and unstable) applications I ever worked with was a
distributed financial inventory system, where each specialist had their own
database, shared from their own computer, and the coworkers connected to each as
necessary. Auuuuugghhhhhh.

Don't do that, please. Just don't. Get a new server, and more server licenses.

If this is Server 2000 with licenses, there should be a license tracking tool.
If not, or if you can't find it, I'll suggest that you post in
microsoft.public.windows.server.general. Hopefully, they can help you there.
<http://www.microsoft.com/technet/co...px?dg=microsoft.public.windows.server.general>
http://www.microsoft.com/technet/co...px?dg=microsoft.public.windows.server.general

 

[Guest]

Chelsea,

Assuming that everybody wouldn't connect to everybody else's share every time,
making the entire LAN into one big distributed server would make sense.

Except for the administration headache. I speak from experience here - one of
the most interesting (and unstable) applications I ever worked with was a
distributed financial inventory system, where each specialist had their own
database, shared from their own computer, and the coworkers connected to each as
necessary. Auuuuugghhhhhh.

Don't do that, please. Just don't. Get a new server, and more server licenses.

Chuck -
If this is just a licensing issue why would everyone be able to connect most
of the time? For instance, our last worker arrived this morning after
everyone else had already logged on to the server and was actively working.
She could not connect, so rebooted her computer. Everyone else continued to
work and after her reboot she connected just fine. And everyone else was
still connected and working.

If this is Server 2000 with licenses, there should be a license tracking tool.
If not, or if you can't find it, I'll suggest that you post in
microsoft.public.windows.server.general. Hopefully, they can help you there.

Thanks again - I will check here and see what else I can learn. I really
appreciate all the help!