Modem Hangs

mickeyboymel

I have an ongoing problem with my pc's internal modem. It is a aopen 56k plx v92 on windows xp home. I am on dialup via eircomnet anytime 150.

When I try to close the connection, it hangs for ages with no response. I have all the updates to windows drivers and aopen but I cannot resolve this.

The fault is intermittent and very annoying. This is an example of the log

03-29-2004 15:41:17.312 - TSP(0000): Dropping Call
03-29-2004 15:41:17.312 - Hanging up the modem.
03-29-2004 15:41:17.312 - Hardware hangup by lowering DTR.
03-29-2004 15:41:27.312 - A timeout has expired waiting to comm event to occour.
03-29-2004 15:41:27.312 - WARNING: After lowering DTR to hangup, the modem did not drop CD with in 10 seconds, Attempting software hangup.
03-29-2004 15:41:27.312 - Send: +++
03-29-2004 15:41:27.312 - TSP(0000): Closing Call
03-29-2004 15:41:37.312 - A timeout has expired waiting to comm event to occour.
03-29-2004 15:41:37.312 - Recv: <cr><lf>OK<cr><lf>
03-29-2004 15:41:37.312 - Interpreted response: OK
03-29-2004 15:41:37.328 - Send: ATH<cr>
03-29-2004 15:41:42.328 - Timed out waiting for response from modem
03-29-2004 15:41:42.328 - Send: ATH<cr>
03-29-2004 15:41:47.328 - Timed out waiting for response from modem
03-29-2004 15:41:47.343 - Send: ATH<cr>
03-29-2004 15:41:52.343 - Timed out waiting for response from modem
03-29-2004 15:41:52.359 - Send: ATH<cr>
03-29-2004 15:41:57.359 - Timed out waiting for response from modem
03-29-2004 15:41:57.375 - Send: at#ud<cr>
03-29-2004 15:42:07.375 - Timed out waiting for response from modem
03-29-2004 15:42:07.375 - 115200,8,N,1, ctsfl=1, rtsctl=2
03-29-2004 15:42:07.375 - Initializing modem.
03-29-2004 15:42:07.375 - CD is high while initializing modem.
03-29-2004 15:42:07.390 - Send: AT<cr>
03-29-2004 15:42:09.390 - Timed out waiting for response from modem
03-29-2004 15:42:09.390 - The modem failed to respond to the initialization command, Retrying one more time
03-29-2004 15:42:09.390 - 115200,8,N,1, ctsfl=1, rtsctl=2
03-29-2004 15:42:09.406 - CD is high while initializing modem.
03-29-2004 15:42:09.406 - Send: AT<cr>
03-29-2004 15:42:11.406 - Timed out waiting for response from modem
03-29-2004 15:42:11.406 - The modem failed to respond to the initialization command, Retrying one more time
03-29-2004 15:42:11.406 - 115200,8,N,1, ctsfl=1, rtsctl=2
03-29-2004 15:42:11.406 - CD is high while initializing modem.
03-29-2004 15:42:11.421 - Send: AT<cr>
03-29-2004 15:42:13.421 - Timed out waiting for response from modem
03-29-2004 15:42:13.421 - TSP(0000): LINEEVENT: LINECALLSTATE_DISCONNECTED(0x1)
03-29-2004 15:42:13.421 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE
03-29-2004 15:42:13.421 - TSP Completing Async Operation(0x00010189) Status 0x00000000
03-29-2004 15:42:13.437 - Session Statistics:
03-29-2004 15:42:13.437 - Reads : 0 bytes
03-29-2004 15:42:13.437 - Writes: 9 bytes

kmb

Did you try downloading updated drivers?TRy aopen site.

mickeyboymel

I have the latest drivers from the site, although they are a few years old (nov 2002)

I think it may be an issue with V92 as Eircom do not support it. I have inserted the +MS=v90 string, but it still hangs occassionaly.

I had a friends pc here doing some work on it and it had a v90 modem, which was very stable, never hung or dropped a connection.

I have been advised by Iqon to change to IOL or UTVip as this may resolve the issue.

I have googled the problem, and found several other complaints similar to this, from v92 internal modem users of various modem manufacturers.

There are reports of batch problems with the FM56 PLX model on the Aopen support forum, so I think Iam stuck with it. Its not a major issue, but you have to monitor it to make sure it actually hangs up, and it is an intermittent fault, not present all the time.

ColmOT [MSFT]

When yoiu installed the drivers, were they digitally signed? (i.e. were you prompted to click Install Anyway to a dialog warning you abotu stability issues with untested drivers)?

It looks like it's a driver issue from the log. Windows sends the hang-up signal, but the driver isn't interpreting it correctly (or just doesn't know what to do with the signal!).

Sleipnir

Did this happen suddenly or after anything specific happened like a driver upgrade?
OS upgrade?
Does a telephone work on that line?
Have you tried a different dialup connection such as Esat/IOL's?
You need to eliminate either a possible hardware fault or a possible software fault. The easiest one to eliminate is hardware in the first instance.

I would remove the card from Device manager, shut down the PC, open the case, remove the modem and put it in another slot.
Then reboot and let windows install it (if it has the drivers already)
Then re-install the dialup and try to connect.
Still not working? install updated drivers if available and try again.
Try the modem in a different PC if you can.

mickeyboymel

No Colum, the drivers are not signed, and I was warned at installation, but there is no other driver available for the modem, on Xp.


Sleipnir, this has always been a problem from day one with the pc,it is still under warranty from iQon, and as such I do not really want to open it up in case I void the guarentee. Their only suggestion is to change ISP., and indeed they accept no responsibility for any issues related to dialup, unless you use IOL. Having been involved in lenghty discussion with them in this regard, they say its because of Eircom not preforming well in dialup tests they ran on v92 modems,whereas IOL (and recently UTVip though not yet offically recommended) preformed well.

I have not tried any other dialup for a long enough period to determine if the problem still persists. As I said, it is intermittent, and therefore very hard to moniter.

The line is working , and the other pc I had here(with the older modem) downloaded two years worth of Windows updates, without dropping/hanging once, so the line cannot be at fault.

I might buy an external modem, for the moment, then change the internal card later, when the warranty expires.

Thanks for all the help.

mickeyboymel

Sorry for dragging this up but I finally solved the problem after months and months of trying.

There is a hotfix from Microsoft due to be released in the upcoming SP2: http://support.microsoft.com/default.aspx?scid=kb;en-us;332176&Product=WinXP

I rang Microsoft, and was transferred to the US callcentre, where they sent a link and password to download the patch and it solves the problem.

It is such a relief to finally have the problem fixed after all this time and hopefully this information may be useful to someone else:D