If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
XP Pro machine will not stay connected to network for more than 30
I have a computer that was running normally for several years. Suddenly, it
started off the network after about 30 mins after boot. It couldn't see other machines and they couldnt see it. Rebooting solves the problem for another 30 mins or so. I put a second PCI network card in the machine and connected to that - and the problem remained, so it is not the hardware. I replaced the network switches. I ran SPYBOT S&D and several WINSOCK repair utilities. Event log showed another computer on the net trying to become a browser master. I shut that machine off. None of the other machines on my network (6) have this problem. The only possible clue I have is that I'm getting an WARNING (in event log) that I'm exceeding the maximum number of connection attempts. NETSCAN shows 7 devices connected - but XP allows 10, right? I have tried both static and dynamic ips, What can I try next? |
Ads |
#2
|
|||
|
|||
XP Pro machine will not stay connected to network for more than 30
Exdairyfarmer wrote:
I have a computer that was running normally for several years. Suddenly, it started off the network after about 30 mins after boot. It couldn't see other machines and they couldnt see it. Rebooting solves the problem for another 30 mins or so. I put a second PCI network card in the machine and connected to that - and the problem remained, so it is not the hardware. I replaced the network switches. I ran SPYBOT S&D and several WINSOCK repair utilities. Event log showed another computer on the net trying to become a browser master. I shut that machine off. None of the other machines on my network (6) have this problem. The only possible clue I have is that I'm getting an WARNING (in event log) that I'm exceeding the maximum number of connection attempts. NETSCAN shows 7 devices connected - but XP allows 10, right? I have tried both static and dynamic ips, What can I try next? The inbound connection limitation is not for *devices*; it is for *connections*. So while you are correct that the limitation in XP Pro is 10, you are incorrect about the number of connections your computers are making. Each computer can - and usually does - make more than one connection to a pseudo-server/server. So you are bumping into the concurrent inbound connection limitation. The way to solve this is to replace the XP Pro pseudo-server with a real server operating system such as Small Business Server or, if the pseudo-server is only used as a file server, you can replace it with one of the many Linux distros since Linux has no such limitation. Malke -- MS-MVP Elephant Boy Computers www.elephantboycomputers.com Don't Panic! |
#3
|
|||
|
|||
XP Pro machine will not stay connected to network for more tha
I shut off several of the machines in my home network, so I don't get that message anymore. But the problem remains. There is really nothing in the error log that would indicate the problem. "Malke" wrote: Exdairyfarmer wrote: I have a computer that was running normally for several years. Suddenly, it started off the network after about 30 mins after boot. It couldn't see other machines and they couldnt see it. Rebooting solves the problem for another 30 mins or so. I put a second PCI network card in the machine and connected to that - and the problem remained, so it is not the hardware. I replaced the network switches. I ran SPYBOT S&D and several WINSOCK repair utilities. Event log showed another computer on the net trying to become a browser master. I shut that machine off. None of the other machines on my network (6) have this problem. The only possible clue I have is that I'm getting an WARNING (in event log) that I'm exceeding the maximum number of connection attempts. NETSCAN shows 7 devices connected - but XP allows 10, right? I have tried both static and dynamic ips, What can I try next? The inbound connection limitation is not for *devices*; it is for *connections*. So while you are correct that the limitation in XP Pro is 10, you are incorrect about the number of connections your computers are making. Each computer can - and usually does - make more than one connection to a pseudo-server/server. So you are bumping into the concurrent inbound connection limitation. The way to solve this is to replace the XP Pro pseudo-server with a real server operating system such as Small Business Server or, if the pseudo-server is only used as a file server, you can replace it with one of the many Linux distros since Linux has no such limitation. Malke -- MS-MVP Elephant Boy Computers www.elephantboycomputers.com Don't Panic! |
#4
|
|||
|
|||
XP Pro machine will not stay connected to network for more tha
Exdairyfarmer wrote:
I shut off several of the machines in my home network, so I don't get that message anymore. But the problem remains. There is really nothing in the error log that would indicate the problem. When you shut off the other machines, does netscan show the reduced number of connections? Are you sure about the 30 minutes time period? If it isn't exactly 30 minutes, perhaps there's some hardware issue. Overheating? Problem with your switch/router? Just WAGs there. Malke -- MS-MVP Elephant Boy Computers www.elephantboycomputers.com Don't Panic! |
#5
|
|||
|
|||
XP Pro machine will not stay connected to network for more tha
Netscan did show that the other machines were turned off. I changed cables
and switches. And like I said, I changed network HARDWARE. I normally use the GIGE port on the motherboard, but when the symptoms appeared, I plugged in a PCI GigE card. Same results. The machine is rock-solid and always has been. It has got to be a software issue somewhere. I just can't find it. Is there any sort of diagnostic tool that can help the "non C programmer" find Winsock errors? "Malke" wrote: Exdairyfarmer wrote: I shut off several of the machines in my home network, so I don't get that message anymore. But the problem remains. There is really nothing in the error log that would indicate the problem. When you shut off the other machines, does netscan show the reduced number of connections? Are you sure about the 30 minutes time period? If it isn't exactly 30 minutes, perhaps there's some hardware issue. Overheating? Problem with your switch/router? Just WAGs there. Malke -- MS-MVP Elephant Boy Computers www.elephantboycomputers.com Don't Panic! |
#6
|
|||
|
|||
XP Pro machine will not stay connected to network for more tha
Exdairyfarmer wrote:
Netscan did show that the other machines were turned off. I changed cables and switches. And like I said, I changed network HARDWARE. I normally use the GIGE port on the motherboard, but when the symptoms appeared, I plugged in a PCI GigE card. Same results. The machine is rock-solid and always has been. It has got to be a software issue somewhere. I just can't find it. Is there any sort of diagnostic tool that can help the "non C programmer" find Winsock errors? When it comes to sophisticated testing of network errors, I'm out of my area of expertise. I'll need to bow out and leave you to the true advanced networking brains who hang out here. I'm sorry I was unable to help you. Malke -- MS-MVP Elephant Boy Computers www.elephantboycomputers.com Don't Panic! |
#7
|
|||
|
|||
XP Pro machine will not stay connected to network for more tha
Thanks. I do appreciate your time in trying to help me. I'll start it in
SAFE MODE and see what happens. With enough time, I just might be able to find it. Each iteration will take me 20-30 minutes on the average. "Malke" wrote: Exdairyfarmer wrote: Netscan did show that the other machines were turned off. I changed cables and switches. And like I said, I changed network HARDWARE. I normally use the GIGE port on the motherboard, but when the symptoms appeared, I plugged in a PCI GigE card. Same results. The machine is rock-solid and always has been. It has got to be a software issue somewhere. I just can't find it. Is there any sort of diagnostic tool that can help the "non C programmer" find Winsock errors? When it comes to sophisticated testing of network errors, I'm out of my area of expertise. I'll need to bow out and leave you to the true advanced networking brains who hang out here. I'm sorry I was unable to help you. Malke -- MS-MVP Elephant Boy Computers www.elephantboycomputers.com Don't Panic! |
#8
|
|||
|
|||
XP Pro machine will not stay connected to network for more tha
Found it!
It was BitTorrent 5.09. I upgraded to the latest version, and things are back to normal. "Exdairyfarmer" wrote: Thanks. I do appreciate your time in trying to help me. I'll start it in SAFE MODE and see what happens. With enough time, I just might be able to find it. Each iteration will take me 20-30 minutes on the average. "Malke" wrote: Exdairyfarmer wrote: Netscan did show that the other machines were turned off. I changed cables and switches. And like I said, I changed network HARDWARE. I normally use the GIGE port on the motherboard, but when the symptoms appeared, I plugged in a PCI GigE card. Same results. The machine is rock-solid and always has been. It has got to be a software issue somewhere. I just can't find it. Is there any sort of diagnostic tool that can help the "non C programmer" find Winsock errors? When it comes to sophisticated testing of network errors, I'm out of my area of expertise. I'll need to bow out and leave you to the true advanced networking brains who hang out here. I'm sorry I was unable to help you. Malke -- MS-MVP Elephant Boy Computers www.elephantboycomputers.com Don't Panic! |
#9
|
|||
|
|||
XP Pro machine will not stay connected to network for more tha
Exdairyfarmer wrote:
Found it! It was BitTorrent 5.09. I upgraded to the latest version, and things are back to normal. I never would have guessed this since you didn't mention that you were torrenting. Glad you got it sorted and thanks for posting the solution. Malke -- MS-MVP Elephant Boy Computers www.elephantboycomputers.com Don't Panic! |
#10
|
|||
|
|||
XP Pro machine will not stay connected to network for more tha
It started automatically, and I had it hidden on the taskbar. I used the
program so infrequently that I didn't even think about it. What is weird is that I don't ever remember updating the program, yet the problem "magically" appeared one day. I suppose it is possible that it's P2P "engine" got corrupted somehow. "Malke" wrote: Exdairyfarmer wrote: Found it! It was BitTorrent 5.09. I upgraded to the latest version, and things are back to normal. I never would have guessed this since you didn't mention that you were torrenting. Glad you got it sorted and thanks for posting the solution. Malke -- MS-MVP Elephant Boy Computers www.elephantboycomputers.com Don't Panic! |
Thread Tools | |
Display Modes | |
|
|