Internet Problems

[Crispy Critters]

I wasn't really sure to put this in hardware to software, but nonetheless this issue is starting to piss me off. My internet just keeps cutting out at least once an hour, and restarting my modem doesn't rememdy the problem. My dad's machine is coming off the same modem, and he isn't having a problem. I've called my ISP, and after messing around on the phone for an hour, the only solution they have is to send a tech to my house and inspect my wiring which doesn't seem to be the problem if my dad is having no problem.

I do have a few errors:
DHCP Warning: (semaphore timeout perioud expired, unable to renew)
TCPIP Warning: (reached the security limit imposed on the number of concurrent TCP connects)
DCOM Error: (server did not register with DCOM within the required timeout.)

Those three errors occur in that same order everytime my internet goes out.

I don't remember when this problem started, at least a month, but lately it's been getting worse. I'm using XP Pro. Does anyone have any suggestions while I wait for an apointment with the tech?

[Wamplet]

Quite a few things to try:

If you use a router, try a different port. Also, try another network cable, update the nic drivers, etc.

[NutWrench]

I bet this will fix it. (http://mitglied.lycos.de/lvllord/download-mirror.htm)

[Crispy Critters]

What is it?

[Inanimate Carbon Rod]

Try a different port on your router and/or replace your NIC card.

[NutWrench]

Crispy Critters said:
What is it?



It patches your TCPIP.SYS file to remove the 10 connection limit imposed by Service Pack 2 over transient TCP/IP outbound connections. The new default setting is 50, allthough if you are using P2P software, you might want to set that to 100. The patch makes a backup copy of tcpip.sys, so you can restore it if there any problems.


Limited number of simultaneous incomplete outbound TCP connection attempts

Detailed description

The TCP/IP stack now limits the number of simultaneous incomplete outbound TCP connection attempts. After the limit has been reached, subsequent connection attempts are put in a queue and will be resolved at a fixed rate. Under normal operation, when applications are connecting to available hosts at valid IP addresses, no connection rate-limiting will occur. When it does occur, a new event, with ID 4226, appears in the system’s event log.


http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx


Check your event viewer. I bet you have a bunch of 4226 timeout errors. After you apply the patch, windows will complain that one of the system files (tcpip.sys) has been altered. Just hit "Cancel."

[Tedski]

Crispy Critters said:
What is it?


A patch.

If you are using a broadband connection, it is quite likely that somewhere along the lines you are also using software that tkaes advantage of this fact, and 'opens up' a good deal more connections than some might deem desireable. I'm particularly thinking of download managers here. It may not just be you, it may also be your father. Fact remains that one of you is probaly exceeding the standard windows 'concurrent connections' limit. It may even be related to the use of different AV software, or anti-spyware stuff. Generally speaking, those sorts of software view increasing amount of connections to your pc rather unfavourably - and probably rightly so. Therefore you need to apply something like the aforementioned patch to deal with it. This shouldn't be about to make your pc less secure, rather it allows more connections to be made. If you are running AV software and anti-spyware stuff, it is conceivable you need to make that aware of what you are doing, but it should take the hint from the OS. You should still be 'covered' by your AV and anti-spyware software even if you appluy the patch. http://forums.3drealms.com/ubbthreads/images/graemlins/wink.gif