About a week ago, several (but not all) XP machines in my network began losing connections to printing and other network resources that reside on separate servers. I've been pulling my hair out trying to track down the answer.
Some of the behaviors: I do not lose Internet connection. I can ping all network resources and printers with good response times. Rebooting the computer restores the connections and everything works fine, but only lasts anywhere from 5 - 30 minutes. While connection is lost, if I try to open the properties of a networked printer, I get a message that the print spooler is not running (but it shows as started in the services window).
Here are the things I've tried:
1. Searched MSKB, but didn't find anything.
2. Scanned each computer for viruses and spyware. None.
3. Checked DNS settings to make sure they did not get corrupted. They appear OK, but I am far from comfortable in my knowledge of DNS.
4. Flushed DNS on DNS server and local machine.
4. Expanded the DHCP scope on the network, as the number of leases have grown to use up all available addresses. (Interesting what you find out while solving another problem.)
5. Restored one computer using a restore point back about a week before the problem appeared. The computer remained connected for most of the day, so I thought I had licked the problem, but lost connection late in the day.
I am out of options. Does anyone have other ideas?? I would be very appreciative. Thank you.
Randy Davis, MCP
IT Director
Lubbers Auto Group
Some of the behaviors: I do not lose Internet connection. I can ping all network resources and printers with good response times. Rebooting the computer restores the connections and everything works fine, but only lasts anywhere from 5 - 30 minutes. While connection is lost, if I try to open the properties of a networked printer, I get a message that the print spooler is not running (but it shows as started in the services window).
Here are the things I've tried:
1. Searched MSKB, but didn't find anything.
2. Scanned each computer for viruses and spyware. None.
3. Checked DNS settings to make sure they did not get corrupted. They appear OK, but I am far from comfortable in my knowledge of DNS.
4. Flushed DNS on DNS server and local machine.
4. Expanded the DHCP scope on the network, as the number of leases have grown to use up all available addresses. (Interesting what you find out while solving another problem.)
5. Restored one computer using a restore point back about a week before the problem appeared. The computer remained connected for most of the day, so I thought I had licked the problem, but lost connection late in the day.
I am out of options. Does anyone have other ideas?? I would be very appreciative. Thank you.
Randy Davis, MCP
IT Director
Lubbers Auto Group