|
web
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
System Keeps droping off network.Have a problem with a system that is the second one to start doing this, first one did it about 1.5 years ago (finally replaced it). Running WIndows 2000 on a Dell 8200 (1.7Ghz P4). The system works fine for about 10 minutes after booting. Walk away from it for 10 minutes and it drops off the network. Log off and back on and it is back on the network. Click on either of the mapped network drives (mapped to SBS 2003 Server) and it gets an error that the connection is not accessible. If you try and get on the web it works. If you ping the Router or the Server it works, and if you ping the server it will usually reconnect to the server and you can then access the mapped drives again. Tried changing the cable, port it is using on the switch, bought a different switch, moved to different desk in office, still having problem. Changed out Network card with new one, that didn't help, tried a different slot, that didn't help. Have installed a different server (SBS 2003) since the first one had the problem (server running NT then), that one never was resolved, finally replaced the system. While this is the second system on this network that has had this problem, I have yet to see this problem with any other system anywhere and these are Dell systems (8200 Models) that I have used at 50+ different places. They have 5 other identical systems in the office and none has the problem (yet). Anyone have a clue about what could cause this? It looks like you have checked about everything possible.
This is just a thought and you probably have already checked this numerous times but might the power management settings for the NIC be set to power off the device to save power? Show quoteHide quote "JeffM" wrote: > I am posting this again with some updates. > > Have a problem with a system that is the second one to start doing this, > first one did it about 1.5 years ago (finally replaced it). Running WIndows > 2000 on a Dell 8200 (1.7Ghz P4). > > The system works fine for about 10 minutes after booting. Walk away from it > for 10 minutes and it drops off the network. Log off and back on and it is > back on the network. > > Click on either of the mapped network drives (mapped to SBS 2003 Server) and > it gets an error that the connection is not accessible. > > If you try and get on the web it works. If you ping the Router or the Server > it works, and if you ping the server it will usually reconnect to the server > and you can then access the mapped drives again. > > Tried changing the cable, port it is using on the switch, bought a different > switch, moved to different desk in office, still having problem. > > Changed out Network card with new one, that didn't help, tried a different > slot, that didn't help. > > Have installed a different server (SBS 2003) since the first one had the > problem (server running NT then), that one never was resolved, finally > replaced the system. > > While this is the second system on this network that has had this problem, I > have yet to see this problem with any other system anywhere and these are > Dell systems (8200 Models) that I have used at 50+ different places. > > They have 5 other identical systems in the office and none has the problem > (yet). > > Anyone have a clue about what could cause this? > I wish that was it, but this Nic doesn't have that option and 10 minutes
while the screen is active is definintely too soon for it. It is so weird...this has happend to 2 different systems, and one of them started doing it about 13 months after it was purchased (just after the warranty expired). Show quoteHide quote "Bill" wrote: > It looks like you have checked about everything possible. > > This is just a thought and you probably have already checked this numerous > times but might the power management settings for the NIC be set to power off > the device to save power? > > > "JeffM" wrote: > > > I am posting this again with some updates. > > > > Have a problem with a system that is the second one to start doing this, > > first one did it about 1.5 years ago (finally replaced it). Running WIndows > > 2000 on a Dell 8200 (1.7Ghz P4). > > > > The system works fine for about 10 minutes after booting. Walk away from it > > for 10 minutes and it drops off the network. Log off and back on and it is > > back on the network. > > > > Click on either of the mapped network drives (mapped to SBS 2003 Server) and > > it gets an error that the connection is not accessible. > > > > If you try and get on the web it works. If you ping the Router or the Server > > it works, and if you ping the server it will usually reconnect to the server > > and you can then access the mapped drives again. > > > > Tried changing the cable, port it is using on the switch, bought a different > > switch, moved to different desk in office, still having problem. > > > > Changed out Network card with new one, that didn't help, tried a different > > slot, that didn't help. > > > > Have installed a different server (SBS 2003) since the first one had the > > problem (server running NT then), that one never was resolved, finally > > replaced the system. > > > > While this is the second system on this network that has had this problem, I > > have yet to see this problem with any other system anywhere and these are > > Dell systems (8200 Models) that I have used at 50+ different places. > > > > They have 5 other identical systems in the office and none has the problem > > (yet). > > > > Anyone have a clue about what could cause this? > > Sounds very strange. You say you have other identical systems on the same
network that do not have the problem. It sounds like you need to try and narrow down the main cause. Firstly is the bios the same on all the systems if not download the latest bios version and see if that works. It maybe worth going to the bios manufacturers website and seeing if there is anything there. I had a server that kept disconnecting and rebooting and it turned out to be the bios. Secondly it maybe worth making a ghost image off one of the working machines and putting it on the suspect machine, this should rule out any software problems. If this does cure it, are you able to use one of the other machines for testing. Try changing components one at a time until the fault transfers across to the other machine, hopefully. If after doing that you have not transfered the fault then it will probably be the motherboard. You then have the option of replacing this or using some diagnostic software on it. If none of these work then ? Chris Show quoteHide quote "JeffM" <je***@discussions.microsoft.com> wrote in message news:14869EF9-7880-42EE-B7BE-F7A96A468AE2@microsoft.com... >I am posting this again with some updates. > > Have a problem with a system that is the second one to start doing this, > first one did it about 1.5 years ago (finally replaced it). Running > WIndows > 2000 on a Dell 8200 (1.7Ghz P4). > > The system works fine for about 10 minutes after booting. Walk away from > it > for 10 minutes and it drops off the network. Log off and back on and it is > back on the network. > > Click on either of the mapped network drives (mapped to SBS 2003 Server) > and > it gets an error that the connection is not accessible. > > If you try and get on the web it works. If you ping the Router or the > Server > it works, and if you ping the server it will usually reconnect to the > server > and you can then access the mapped drives again. > > Tried changing the cable, port it is using on the switch, bought a > different > switch, moved to different desk in office, still having problem. > > Changed out Network card with new one, that didn't help, tried a different > slot, that didn't help. > > Have installed a different server (SBS 2003) since the first one had the > problem (server running NT then), that one never was resolved, finally > replaced the system. > > While this is the second system on this network that has had this problem, > I > have yet to see this problem with any other system anywhere and these are > Dell systems (8200 Models) that I have used at 50+ different places. > > They have 5 other identical systems in the office and none has the problem > (yet). > > Anyone have a clue about what could cause this? > The BIOS is the same on all of them, as are all the components.
The biggest problem is that these 1.8Ghz P4's are now 3 years old, and only worth a couple of hundred dollars. A replacement system is only around $600. It would cost them 2-3 hours of my time to try and troubleshoot the system further swapping hardware and trying different things (Cost $300 and up), I have considered just wiping the drive and rebuilding it, which would take about an hour, but I don't think it will help, I am interested in doing it just to see if it would work however (since I can rebuild it in my office in spare time). A lot of good ideas, but I also suspect it is the motherboard, it just may make more economical sense to just replace it. I was hoping someone might come up with something similar they had run into, that might be a quick fix...something related to Windows XP having some sort of brain fault....but it really does point more to hardware than software I suspect. Show quoteHide quote "CHRISTOPHER AHERN" wrote: > Sounds very strange. You say you have other identical systems on the same > network that do not have the problem. > > It sounds like you need to try and narrow down the main cause. > > Firstly is the bios the same on all the systems if not download the latest > bios version and see if that works. It maybe worth going to the bios > manufacturers website and seeing if there is anything there. I had a server > that kept disconnecting and rebooting and it turned out to be the bios. > > Secondly it maybe worth making a ghost image off one of the working machines > and putting it on the suspect machine, this should rule out any software > problems. > > If this does cure it, are you able to use one of the other machines for > testing. Try changing components one at a time until the fault transfers > across to the other machine, hopefully. If after doing that you have not > transfered the fault then it will probably be the motherboard. You then > have the option of replacing this or using some diagnostic software on it. > > If none of these work then ? > > Chris > > > "JeffM" <je***@discussions.microsoft.com> wrote in message > news:14869EF9-7880-42EE-B7BE-F7A96A468AE2@microsoft.com... > >I am posting this again with some updates. > > > > Have a problem with a system that is the second one to start doing this, > > first one did it about 1.5 years ago (finally replaced it). Running > > WIndows > > 2000 on a Dell 8200 (1.7Ghz P4). > > > > The system works fine for about 10 minutes after booting. Walk away from > > it > > for 10 minutes and it drops off the network. Log off and back on and it is > > back on the network. > > > > Click on either of the mapped network drives (mapped to SBS 2003 Server) > > and > > it gets an error that the connection is not accessible. > > > > If you try and get on the web it works. If you ping the Router or the > > Server > > it works, and if you ping the server it will usually reconnect to the > > server > > and you can then access the mapped drives again. > > > > Tried changing the cable, port it is using on the switch, bought a > > different > > switch, moved to different desk in office, still having problem. > > > > Changed out Network card with new one, that didn't help, tried a different > > slot, that didn't help. > > > > Have installed a different server (SBS 2003) since the first one had the > > problem (server running NT then), that one never was resolved, finally > > replaced the system. > > > > While this is the second system on this network that has had this problem, > > I > > have yet to see this problem with any other system anywhere and these are > > Dell systems (8200 Models) that I have used at 50+ different places. > > > > They have 5 other identical systems in the office and none has the problem > > (yet). > > > > Anyone have a clue about what could cause this? > > > > > You can burn up the difference of funds and still be forced to upgrade. Why wait?
Gates says to replace every 2 1/2 years. LOL. No kidding, give yourself a treat. You'll be glad you did. don "JeffM" <je***@discussions.microsoft.com> wrote in message The BIOS is the same on all of them, as are all the components.news:05B46293-1F63-4330-A1DD-41F23762EBAA@microsoft.com... The biggest problem is that these 1.8Ghz P4's are now 3 years old, and only worth a couple of hundred dollars. A replacement system is only around $600. It would cost them 2-3 hours of my time to try and troubleshoot the system further swapping hardware and trying different things (Cost $300 and up), I have considered just wiping the drive and rebuilding it, which would take about an hour, but I don't think it will help, I am interested in doing it just to see if it would work however (since I can rebuild it in my office in spare time). A lot of good ideas, but I also suspect it is the motherboard, it just may make more economical sense to just replace it. I was hoping someone might come up with something similar they had run into, that might be a quick fix...something related to Windows XP having some sort of brain fault....but it really does point more to hardware than software I suspect. Show quoteHide quote "CHRISTOPHER AHERN" wrote: > Sounds very strange. You say you have other identical systems on the same > network that do not have the problem. > > It sounds like you need to try and narrow down the main cause. > > Firstly is the bios the same on all the systems if not download the latest > bios version and see if that works. It maybe worth going to the bios > manufacturers website and seeing if there is anything there. I had a server > that kept disconnecting and rebooting and it turned out to be the bios. > > Secondly it maybe worth making a ghost image off one of the working machines > and putting it on the suspect machine, this should rule out any software > problems. > > If this does cure it, are you able to use one of the other machines for > testing. Try changing components one at a time until the fault transfers > across to the other machine, hopefully. If after doing that you have not > transfered the fault then it will probably be the motherboard. You then > have the option of replacing this or using some diagnostic software on it. > > If none of these work then ? > > Chris > > > "JeffM" <je***@discussions.microsoft.com> wrote in message > news:14869EF9-7880-42EE-B7BE-F7A96A468AE2@microsoft.com... > >I am posting this again with some updates. > > > > Have a problem with a system that is the second one to start doing this, > > first one did it about 1.5 years ago (finally replaced it). Running > > WIndows > > 2000 on a Dell 8200 (1.7Ghz P4). > > > > The system works fine for about 10 minutes after booting. Walk away from > > it > > for 10 minutes and it drops off the network. Log off and back on and it is > > back on the network. > > > > Click on either of the mapped network drives (mapped to SBS 2003 Server) > > and > > it gets an error that the connection is not accessible. > > > > If you try and get on the web it works. If you ping the Router or the > > Server > > it works, and if you ping the server it will usually reconnect to the > > server > > and you can then access the mapped drives again. > > > > Tried changing the cable, port it is using on the switch, bought a > > different > > switch, moved to different desk in office, still having problem. > > > > Changed out Network card with new one, that didn't help, tried a different > > slot, that didn't help. > > > > Have installed a different server (SBS 2003) since the first one had the > > problem (server running NT then), that one never was resolved, finally > > replaced the system. > > > > While this is the second system on this network that has had this problem, > > I > > have yet to see this problem with any other system anywhere and these are > > Dell systems (8200 Models) that I have used at 50+ different places. > > > > They have 5 other identical systems in the office and none has the problem > > (yet). > > > > Anyone have a clue about what could cause this? > > > > > |
|||||||||||||||||||||||
Other interesting topics