Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

XP machines lose connection to network resources

Status
Not open for further replies.

rrdavis07

MIS
Jun 2, 2004
88
US
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

 
Just for diagnosis (boy, I'm sounding like a broken record on this one)... try turning down your network speed on your NIC's. Turn them down to 10-baseT, and see if your problem goes away.

If it does, look at the following:
o "Proper" cabling... that conforms to 586B Specs
o Cabling not too close to flourescent lights, or other equipment generating RF
o Did I mention to check the cabling? ;)



Just my 2¢

"In order to start solving a problem, one must first identify its owner." --Me
--Greg
 
I agree that cabling is very important. These old buildings were cabled by the guy who had the job before me and he did not follow proper specs. We do have cables too close to flourescent lights, etc. However, these problems starting showing up last Friday all at the same time. There is no correlation as to location that I can tell.


Randy Davis, MCP
IT Director
Lubbers Auto Group

 
As to the comment regarding DHCP, the answer is that I prefer it, but as a test, I removed one of the offending computers from DHCP and assigned his IP address manually. No change.


Randy Davis, MCP
IT Director
Lubbers Auto Group

 
Any progress on this problem, we are having the same problem on our network at the moment. Started noticing it about a month back but may have been happening for a couple of weeks beforehand.

Restarting the local spooler sorts the problem but I can't see what is causing the problem in the first place!
 
I had the same problem not so long. In my case I replaced a suspect data port, reterminated my cable and havent had the issue since...

"Have you ever imagined a world with no hypothetical situations?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top