Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Modem can't complete connection

Status
Not open for further replies.

tsurikov

Technical User
Jul 10, 2003
97
US
Hello everyone,

I need help with a baffling modem problem. I have an Elsa MicroLink 56k Fun IIa modem, external, serial (not USB), connected to a PC running Windows XP Pro. This modem used to work fine for connecting to the Internet. Last week, it ceased to function properly. Namely, it can't connect to any ISP - it dials the number, but never progresses beyond the stage where you hear the high-pitched squeals as the modems try to connect. It just keeps making those shrill beeping noises (of various sorts); I've let it run for about two minutes like this, but the modem on the other end appears to hang up the line after that.

I can connect to the Internet using the same phone line with my laptop's modem without any problems. I can successfully communicate with the modem using HyperTerminal; it responds to all AT commands normally. The modem can also send and receive faxes without any problems. I've checked all COM port settings (all seem normal) and tried the modem on both COM1 and COM2, without any difference. The Elsa Web site is down, but other sources on the Internet seem to suggest no special drivers are needed under WinXP for this modem. (Just for the heck of it, I also tried the Win2K drivers that came on the CD-ROM with the modem; no difference.) I've uninstalled and reinstalled the modem driver (Windows autodetects the modem), to no effect.

This, as I said, baffles me. Do y'all have any suggestions or pointers? Thanks very much!
--Michael
 
Sounds like the modem might be shot, or the ISP has upgraded to incompatible equipment. It sounds like it's failing at the hardware level because it cannot complete the connection to another modem. I don't think any software affects the modem to modem communication.
 
Thanks for the insight, kiddpete, that's sort of the direction I've been leaning in myself. What holds me back from fully believing that is that the modem has no problem with faxes (sending or receiving) - and I imagine the same hardware has to be used for data and fax, no? Anyway, I'm going to do one more test with another computer and another phone line, and post with the results.

Cheers!
--Michael
 
OK, everyone, issue's closed - the modem itself is messed up, hardware-wise. Tested it on another system and phone line. This time it couldn't dial a zero - i.e., it makes a sound where a zero should be, but the phone line doesn't detect that a number has been dialed. I'd say that's enough evidence to chuck the thing.

Cheers,
--Michael
 
There is a controller chip that monitors line status that used to be quite expensive, and was after a time copied and mass-produced to lower modem costs and create clones of the "big" modem producers at much lower cost.

When that little line status IC goes, toss the modem.
They have an irratating "light-bulb" quality to them, as they are indirectly exposed to your phone line voltages.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top