"no dial tone error" w/ 5610B Modem Win XP

[conlan]

I'm replacing a USR 5699B WinModem w/ a USR 5610B Hardware Modem. I uninstalled the 5699 and it's drivers, then installed the 5610B, flashed it to the latest version and updated the driver to the latest. I can successfully query the modem. however when i try to connect, i get a "no dial tone" error. I also tried rolling back the driver, trying different PCI slots, and changing COM Ports. I re-installed the 5699B, and here i am. System specs below:

Asus A7N8X rev. 2.0
Athlon XP 2700+
2x512 MB PC-3200

Thanks in advance for any help.

 

[Zepper]

Make sure you plug the phone cord from the wall into the correct jack on the modem. USR's jacks used to be marked - Telco and Phone, the wall cord goes into the Telco jack. Some other modems are marked Line and Phone - on those, the wall cord goes into the one marked Line. An extension Phone can be plugged into the jack marked Phone. In any case, with properly designed modems, the Phone jack is disconnected by a relay when the modem goes online, so if you have the wall cord plugged into the Phone jack, no dial tone... To make sure there is actually a dial tone, plug an extension phone into the Phone jack and see if there is a dial tone by listening.
. On cheap modems the jacks are just wired in parallel - which is dangerous because if you pick up the phone while online, you can cause your modem session to be dropped. So I recomend against using an extension phone with that type of modem. And on my current modem, they were too cheap to even include a jack for an extension phone. Hard to make a mistake that way.

.bh.

 

[corkyg]

To make sure there is actually a dial tone, plug an extension phone into the Phone jack and see if there is a dial tone by listening.

Exactly! If you can't hear it on the phone, you can bet the modem can't here it because it isn't there.

 

[conlan]

Thanks for the replies, i did however already check that. It acts like some sort of Hardware conflict, although i cannnot seem to pinpoint it.

 

[corkyg]

Have you changed the cable? Are the right drivers installed? Too bad you didn't try it before flashing the firmware.

 

[conlan]

Yes, Yes and i did

 

[corkyg]

OK - if it ain't the cable, and it ain't the flash upgrade, and it ain't the line - things really point to the drivers. This is really a mystery now.

 

[conlan]

A very aggravating mystery at that :disgust:

 

[Sensai]

RMA it.... i have the preformance pro which had the same problem.. it seems like it was a known issue... lol.. the center is run by canadians

 

[conlan]

Haaaaaallllpppppppp!!!