dbetz
asked on
TCP/IP stops, but I am still connected on dialup? HELP!
This has been happening for months now and I am SICK OF IT!!!
When I connect via Dialup- with my modem I get on the Internet fine, but after a random periond of time I can do nothing. I am still connected, but it is like the TCP/IP is dead. I also noticed that if I download for a long period of time, it will stay connected.
Sometimes I can disconnect then reconnct and get back one, other times I need to reboot.
I switched ISPs and the problem is still there.
I need this fixed, I have a WinGate LAN on this machine.
All points are on this one.
When I connect via Dialup- with my modem I get on the Internet fine, but after a random periond of time I can do nothing. I am still connected, but it is like the TCP/IP is dead. I also noticed that if I download for a long period of time, it will stay connected.
Sometimes I can disconnect then reconnct and get back one, other times I need to reboot.
I switched ISPs and the problem is still there.
I need this fixed, I have a WinGate LAN on this machine.
All points are on this one.
ASKER
No dude...This is actually Win98 RC4...Been happening sinse my Win95B w/ dialup 1.2. No version changes it
ASKER
It is Win98 RC4 that is not the problem, I have had this problem since Win95B w/ dialup 2.1
I am betting on some software problem and I bet that it will go away when I have to redo my HD when Win98 final comes out...I would just like to fix it now and get a TID written on it.
I am betting on some software problem and I bet that it will go away when I have to redo my HD when Win98 final comes out...I would just like to fix it now and get a TID written on it.
I've seen the following solve several weird tcp/ip issues. Remove the following registry keys:
HKEY_LOCAL_MACHINE\System\
HKEY_LOCAL_MACHINE\System\
Remove TCP/IP from network properties FIRST!
I agree that this will go away when you redo you HD.
HKEY_LOCAL_MACHINE\System\
HKEY_LOCAL_MACHINE\System\
Remove TCP/IP from network properties FIRST!
I agree that this will go away when you redo you HD.
ASKER
You fried my computer dude, thanks for nothing.
I reinstalled Win98 and it worked fine...THEN IT DID IT AGAIN after I reinstaleld all my crap...
Forget it...
I reinstalled Win98 and it worked fine...THEN IT DID IT AGAIN after I reinstaleld all my crap...
Forget it...
I had a similar problem, and you wouldn't credit what it was.
I tried new winsock, reinstall, I even had the phone company around to look at the lines !
It turned out that my Modem (which was a netcomm Smart Modem) had some fairly funky firmware designed to filter packets of data. My phone line isn't what it should be anyway, so what was happening was that the modem would transmit in a "pack burst". I upgraded the firmare on my modem and it solved my problem.(after a long time just putting up with it, and just reconnecting.
When you reboot, you are probably forcing a modem reset, so that this why that would would solve your problem.
Trust me. It is not software.
I tried new winsock, reinstall, I even had the phone company around to look at the lines !
It turned out that my Modem (which was a netcomm Smart Modem) had some fairly funky firmware designed to filter packets of data. My phone line isn't what it should be anyway, so what was happening was that the modem would transmit in a "pack burst". I upgraded the firmare on my modem and it solved my problem.(after a long time just putting up with it, and just reconnecting.
When you reboot, you are probably forcing a modem reset, so that this why that would would solve your problem.
Trust me. It is not software.
ASKER
Its is your modem........If you get a connection with TCP/IP, Then the transport protocol is functioning. It won't cause the problem you decribed. It will either work (even for a short time), or not work. It would be a consistant measurable problem. you are get transport. Therefore it can't be TCP/IP.
Its is your modem........If you get a connection with TCP/IP, Then the transport protocol is functioning. It won't cause the problem you decribed. It will either work (even for a short time), or not work. It would be a consistant measurable problem. you are getting transport. Therefore it can't be TCP/IP.
Well, it always works when I am downloading for an extended period of time. It locks up when I stop downloading and go browseing, e-mail, chat, or another download.
ASKER
Do you have any power management software running?
No, all APM is off.
ASKER
Do you by any chance have Novell client software installed to connect to a Novell network remotely?
No NetWare anywhere. I redid my entire machine Thursday.
ASKER
Have you updated your firmware yet ???
Have you updated your firmware yet ???
There is no update. Motorola Modem Surfer 288
ASKER
Try a different modem..
This brings to mind three things.
1)Check the status sent/received after you connect through TCP/IP, make sure you are not receiving packets while your system is idle. Make sure TCP/IP is the only protocol your dial up adapter is bound to. NO IPX, NO Netbeui.
2) If the modem is consistantly becoming unresponsive after a set period of time, (not just idleing), then it is possible it has malfunctioned or something is overheating on the boards circuitry. You may need to replace the modem. Is it under warranty? If so this should be a mute point for you.
3) How did you do your dial up setup. Who is your ISP? If there connectivity software installs an adapter into your network neighboorhood check to see that it is functioning properly.
4) Check your modem device properties, Make sure there are no device conflicts. Is the modem on a secured IRQ. None of this shared ComPort stuff.
Finally, I have seen this problem occur before when Norton Antivirus was installed on the system. Did you know that Norton posted info about dialup connections and their software.
Finally Finally, make sure when and if the modem becomes unresponsive a little bastard named MPREXE is "not responding" when you press Control Alt Del....
Goodhunting and post more info. It's hardware, it's software, the problem can be solved...
Best Regards, TakiRenzo.
1)Check the status sent/received after you connect through TCP/IP, make sure you are not receiving packets while your system is idle. Make sure TCP/IP is the only protocol your dial up adapter is bound to. NO IPX, NO Netbeui.
2) If the modem is consistantly becoming unresponsive after a set period of time, (not just idleing), then it is possible it has malfunctioned or something is overheating on the boards circuitry. You may need to replace the modem. Is it under warranty? If so this should be a mute point for you.
3) How did you do your dial up setup. Who is your ISP? If there connectivity software installs an adapter into your network neighboorhood check to see that it is functioning properly.
4) Check your modem device properties, Make sure there are no device conflicts. Is the modem on a secured IRQ. None of this shared ComPort stuff.
Finally, I have seen this problem occur before when Norton Antivirus was installed on the system. Did you know that Norton posted info about dialup connections and their software.
Finally Finally, make sure when and if the modem becomes unresponsive a little bastard named MPREXE is "not responding" when you press Control Alt Del....
Goodhunting and post more info. It's hardware, it's software, the problem can be solved...
Best Regards, TakiRenzo.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The solution is for you to upgrade your winsock
Goto http://www.microsoft.com/windows95/info/updates.htm
and download the Dial Up Networking 1.2 upgrade and install this.
This should fix the problem.
If if doesn't then the only thing for you to do is either try another modem or drop the connection speed of the current one.