>The receive light is not blinking but if one picks up the telephone on >that line, one can hear the modem still connected.
Chances are then the remote side has dropped. If you know what you are listening for, you can usually tell if the sound is from the local side or remote site. But I wouldn't be surprised if it is just the local side trying to figure out where the remote went. Basically, its the same idea as a handshake loop. >A handshake loop? Would that possibly be the "ka-bonging?" Basically, its just when the modem connects. It has to "handshake" with the remote side. This is the time when it figures out what compression is acceptable, what speed to connect at, and other fun things like that. With modern modems, they usually start at the best option, and keep trying to make a connection while stepping down options until it succeeds. During this time, one or the other side may give up and drop the connection. Usually the side that didn't drop will realize this, and also disconnect. However, sometimes the modem will get stuck and not realize the other side hung up. Instead it will just keep trying to handshake. If you pick up the phone, you will usually hear lots of hissing at different tones, as well as squeals, and your "ka-bong" noise. Although unless you are used to the sounds, it will all probably sound the same as the noise that is generated during the connection. (I used to be able to tell you what speed a modem connected at based on the sounds during connection... I doubt I could still do it however). >>What modem are you using, >US Robotics Sportster X2 flashed to a v.90. USR modems are usually pretty solid and standard, so it shouldn't by itself be an issue. However that doesn't rule out poor phone lines as a possible problem. >>what OS version? >OS 8.6 Well, that rules out it being an OS X -> Classic interface problem :-) >The modem usually connects at 50666 or occasionaly at 52xxx. I'm not >sure I know how to force a lower speed using tcp/ip either. Check the modem profiles, there may be a USR 33.6 profile. If you have it, choose it. See if the problem goes away. Of course, you said it is not a regular problem, so then it may be REALLY hard to see if it is solved, and if it is rare enough, you may not really care (because going to 33.6 will involve a speed drop, so there is a sacrifice involved in "fixing" it. If it is rarely broke, why sacrifice anything). If there isn't a profile for 33.6, you can make one. But you will have to look up the AT codes to do it for your modem. Again, probably more work then it is worth if you don't have the problem often. And that is all assuming it is even a modem problem, which you aren't convinced it is. Being that it seems to revolve around heavy IE use, that would seem more like IE is somehow screwing up the active TCP/IP stack and preventing use of the connection. -chris <http://www.mythtech.net> ___________________________________________________________________________ To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
