Solved

Modem will not dial

Posted on 2004-09-19
13
5,059 Views
Last Modified: 2013-12-27
A PC came in with a fault that dialling gave the error 'no dialtone', so I thought that would be a quick one.

I swapped  the cable and it is working on a known good phone socket, but still the same, so I swapped the modem.

Now when I dial the modem eventually times out with error 777 suggesting that the modem at the other end is faulty.   I have tried 2 more modems all with the same result

I have copied the modem log below, both of the original modem and a new one.  Please has anyone any suggestions.
Many thanks  John

Log of original modem
09-19-2004 22:03:26.203 - File: C:\WINDOWS\System32\tapisrv.dll, Version 5.1.2600  
09-19-2004 22:03:26.203 - File: C:\WINDOWS\System32\unimdm.tsp, Version 5.1.2600  
09-19-2004 22:03:26.203 - File: C:\WINDOWS\System32\unimdmat.dll, Version 5.1.2600  
09-19-2004 22:03:26.203 - File: C:\WINDOWS\System32\uniplat.dll, Version 5.1.2600  
09-19-2004 22:03:26.203 - File: C:\WINDOWS\System32\drivers\modem.sys, Version 5.1.2600  
09-19-2004 22:03:26.203 - File: C:\WINDOWS\System32\modemui.dll, Version 5.1.2600  
09-19-2004 22:03:26.250 - File: C:\WINDOWS\System32\mdminst.dll, Version 5.1.2600  
09-19-2004 22:03:26.250 - Modem type: MSP3885-E 56K PCI Modem
09-19-2004 22:03:26.250 - Modem inf path: oem4.inf
09-19-2004 22:03:26.250 - Modem inf section: ModemX
09-19-2004 22:03:26.250 - Matching hardware ID: pci\ven_14f1&dev_2f00&subsys_8d88122d
09-19-2004 22:03:26.500 - 115200,8,N,1, ctsfl=1, rtsctl=2
09-19-2004 22:03:26.500 - Initializing modem.
09-19-2004 22:03:26.500 - DSR is low while initializing the modem. Verify modem is turned on.
09-19-2004 22:03:26.515 - Send: AT<cr>
09-19-2004 22:03:26.515 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 22:03:26.515 - Interpreted response: OK
09-19-2004 22:03:26.531 - Send: AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2<cr>
09-19-2004 22:03:26.671 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 22:03:26.671 - Interpreted response: OK
09-19-2004 22:03:26.687 - Send: ATS7=60M1+ES=3,0,2;+DS=3;+IFC=2,2;X4<cr>
09-19-2004 22:03:26.703 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 22:03:26.703 - Interpreted response: OK
09-19-2004 22:03:26.703 - Waiting for a call.
09-19-2004 22:03:26.718 - Send: ATS0=0<cr>
09-19-2004 22:03:26.734 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 22:03:26.734 - Interpreted response: OK
09-19-2004 22:03:26.765 - 115200,8,N,1, ctsfl=1, rtsctl=2
09-19-2004 22:03:26.765 - Initializing modem.
09-19-2004 22:03:26.765 - DSR is low while initializing the modem. Verify modem is turned on.
09-19-2004 22:03:26.781 - Send: AT<cr>
09-19-2004 22:03:26.796 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 22:03:26.796 - Interpreted response: OK
09-19-2004 22:03:26.812 - Send: AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2<cr>
09-19-2004 22:03:26.968 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 22:03:26.968 - Interpreted response: OK
09-19-2004 22:03:26.984 - Send: ATS7=60M1+ES=3,0,2;+DS=3;+IFC=2,2;X4<cr>
09-19-2004 22:03:27.000 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 22:03:27.000 - Interpreted response: OK
09-19-2004 22:03:27.000 - Dialing.
09-19-2004 22:03:27.015 - Send: ATDT###########<cr>
09-19-2004 22:03:34.031 - Recv: <cr><lf>NO DIALTONE<cr><lf>
09-19-2004 22:03:34.031 - Interpreted response: No Dialtone
09-19-2004 22:03:34.031 - Hanging up the modem.
09-19-2004 22:03:34.031 - Send: ATH<cr>
09-19-2004 22:03:34.046 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 22:03:34.046 - Interpreted response: OK
09-19-2004 22:03:34.046 - 115200,8,N,1, ctsfl=1, rtsctl=2
09-19-2004 22:03:34.046 - Initializing modem.
09-19-2004 22:03:34.046 - DSR is low while initializing the modem. Verify modem is turned on.
09-19-2004 22:03:34.046 - Send: AT<cr>
09-19-2004 22:03:34.046 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 22:03:34.046 - Interpreted response: OK
09-19-2004 22:03:34.062 - Send: AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2<cr>
09-19-2004 22:03:34.203 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 22:03:34.203 - Interpreted response: OK
09-19-2004 22:03:34.218 - Send: ATS7=60M1+ES=3,0,2;+DS=3;+IFC=2,2;X4<cr>
09-19-2004 22:03:34.234 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 22:03:34.234 - Interpreted response: OK
09-19-2004 22:03:34.234 - Waiting for a call.
09-19-2004 22:03:34.250 - Send: ATS0=0<cr>
09-19-2004 22:03:34.265 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 22:03:34.265 - Interpreted response: OK
09-19-2004 22:03:34.265 - Session Statistics:
09-19-2004 22:03:34.265 -                Reads : 24 bytes
09-19-2004 22:03:34.265 -                Writes: 86 bytes

Log of replacement modem

09-19-2004 21:50:10.906 - File: C:\WINDOWS\System32\tapisrv.dll, Version 5.1.2600  
09-19-2004 21:50:10.906 - File: C:\WINDOWS\System32\unimdm.tsp, Version 5.1.2600  
09-19-2004 21:50:10.906 - File: C:\WINDOWS\System32\unimdmat.dll, Version 5.1.2600  
09-19-2004 21:50:10.906 - File: C:\WINDOWS\System32\uniplat.dll, Version 5.1.2600  
09-19-2004 21:50:10.906 - File: C:\WINDOWS\System32\drivers\modem.sys, Version 5.1.2600  
09-19-2004 21:50:10.906 - File: C:\WINDOWS\System32\modemui.dll, Version 5.1.2600  
09-19-2004 21:50:10.906 - File: C:\WINDOWS\System32\mdminst.dll, Version 5.1.2600  
09-19-2004 21:50:10.906 - Modem type: Generic 56K HCF Data Fax Modem
09-19-2004 21:50:10.906 - Modem inf path: mdmrpci.inf
09-19-2004 21:50:10.906 - Modem inf section: Modem1005
09-19-2004 21:50:10.906 - Matching hardware ID: pci\ven_127a&dev_1005
09-19-2004 21:50:13.515 - 115200,8,N,1, ctsfl=1, rtsctl=2
09-19-2004 21:50:13.515 - Initializing modem.
09-19-2004 21:50:13.515 - DSR is low while initializing the modem. Verify modem is turned on.
09-19-2004 21:50:13.531 - Send: AT<cr>
09-19-2004 21:50:13.562 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 21:50:13.562 - Interpreted response: OK
09-19-2004 21:50:13.578 - Send: AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2<cr>
09-19-2004 21:50:13.625 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 21:50:13.625 - Interpreted response: OK
09-19-2004 21:50:13.640 - Send: ATS7=60M1+ES=3,0,2;+DS=3;+IFC=2,2;X4<cr>
09-19-2004 21:50:13.671 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 21:50:13.671 - Interpreted response: OK
09-19-2004 21:50:13.671 - Waiting for a call.
09-19-2004 21:50:13.687 - Send: ATS0=0<cr>
09-19-2004 21:50:13.718 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 21:50:13.718 - Interpreted response: OK
09-19-2004 21:50:13.718 - 115200,8,N,1, ctsfl=1, rtsctl=2
09-19-2004 21:50:13.734 - Initializing modem.
09-19-2004 21:50:13.734 - DSR is low while initializing the modem. Verify modem is turned on.
09-19-2004 21:50:13.750 - Send: AT<cr>
09-19-2004 21:50:13.781 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 21:50:13.781 - Interpreted response: OK
09-19-2004 21:50:13.796 - Send: AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2<cr>
09-19-2004 21:50:13.843 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 21:50:13.843 - Interpreted response: OK
09-19-2004 21:50:13.859 - Send: ATS7=60M1+ES=3,0,2;+DS=3;+IFC=2,2;X4<cr>
09-19-2004 21:50:13.890 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 21:50:13.890 - Interpreted response: OK
09-19-2004 21:50:13.890 - Dialing.
09-19-2004 21:50:13.906 - Send: ATDT###########<cr>
09-19-2004 21:51:33.921 - Timed out waiting for response from modem
09-19-2004 21:51:33.921 - Hanging up the modem.
09-19-2004 21:51:33.937 - Send: ATH<cr>
09-19-2004 21:51:33.968 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 21:51:33.968 - Interpreted response: OK
09-19-2004 21:51:34.000 - Send: at#ud<cr>
09-19-2004 21:51:34.046 - Recv: <cr><lf>DIAG <2A4D3263 0=10><cr><lf>DIAG <2A4D3263 1=4><cr><lf>DIAG <2A4D3263 2=0><cr><lf>DIAG <2A4D3263 3=0><cr><lf>DIAG <2A4D3263 4=""><cr><lf>DIAG <2A4D3263 5=""><cr><lf>DIAG <2A4D3263 10=0 11=0 12=0><cr><lf>DIAG <2A4D3263 18=0><cr><lf>DIAG <2A4D3263 20=FF 22=0 24=FFFF><cr><lf>DIAG <2A4D3263
09-19-2004 21:51:34.046 - Unknown Response
09-19-2004 21:51:34.046 - 115200,8,N,1, ctsfl=1, rtsctl=2
09-19-2004 21:51:34.046 - Initializing modem.
09-19-2004 21:51:34.046 - DSR is low while initializing the modem. Verify modem is turned on.
09-19-2004 21:51:34.250 - Send: AT<cr>
09-19-2004 21:51:34.281 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 21:51:34.281 - Interpreted response: OK
09-19-2004 21:51:34.296 - Send: AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2<cr>
09-19-2004 21:51:34.343 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 21:51:34.343 - Interpreted response: OK
09-19-2004 21:51:34.359 - Send: ATS7=60M1+ES=3,0,2;+DS=3;+IFC=2,2;X4<cr>
09-19-2004 21:51:34.390 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 21:51:34.406 - Interpreted response: OK
09-19-2004 21:51:34.406 - Waiting for a call.
09-19-2004 21:51:34.421 - Send: ATS0=0<cr>
09-19-2004 21:51:34.453 - Recv: <cr><lf>OK<cr><lf>
09-19-2004 21:51:34.453 - Interpreted response: OK
09-19-2004 21:51:34.468 - Session Statistics:
09-19-2004 21:51:34.468 -                Reads : 24 bytes
09-19-2004 21:51:34.468 -                Writes: 86 bytes
0
Comment
Question by:jcolles
  • 3
  • 2
  • 2
  • +5
13 Comments
 
LVL 6

Expert Comment

by:Danny Kon
ID: 12100265
First it will be handy to know what operating system you are using and the comm port used, but to give it a try

open a cmd or command prompt
"Use comX as the X is the port used"
"use telephonenumber any telephone what you can hear ringing"

type
 
echo atz > comX
echo atdt"telephonenumber" > comX (so something like echo atdt123456789 > com1)

See if the telephone number you are dialing is giving a call out

if this is the case lower the speed of your modem and check if it make connection to the other computer
If this is not the case please state the error message ,modem/com port settings and operating system

Good-Luck

Dan
0
 
LVL 10

Expert Comment

by:tfjeff
ID: 12100419
I'd try dialing out using hyperterminal...
dial a number like 18007160023 which is the AOL toll free number, if it works correctly it should come up and ask for a login/username...if this happens you know the modem is working fine on a hardware level.
good luck
jeff
0
 

Author Comment

by:jcolles
ID: 12100520
I have tried hyperterminal to a local phone, and it does not dial out with any of the modems.
John
0
 
LVL 10

Expert Comment

by:tfjeff
ID: 12104957
very strange, what OS are you running?  Maybe try the modems in a different slot on the motherboard?  
0
 

Author Comment

by:jcolles
ID: 12105681
I'm running Win XP.  Yes I've also tried a different stot - same result

The original modem I can hear the relay click when it attempts to seize the line, the other ones I cannot hear anything
0
 
LVL 17

Expert Comment

by:rayt333
ID: 12106069
Does any conflicts show in Device Manager? for anything?

You could try removing the comm ports and the modem from Device Manager and reboot and see if they are reinstall correctly and they may now work.
 
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
LVL 8

Expert Comment

by:ddrdan
ID: 12112877
Never had so many prob's with modems till XP reared it's ugly head. That's what you get when you try to build software for idiots! A software that even the pro's can't figure out.


Trick #1 - Try setting the com port in BIOS from 3F8 to 3E8

Trick #2 - Go to Internet Explorer and in tools-internet options-connections check to make sure "never dial a connection"
                is "not" checked. (gotta feeling this is the prob)

Trick #3 - This link has info on setting up WIN XP for their site but you can use it as an example for your setup in WIN XP.
                http://www.camden.rutgers.edu/HELP/Documentation/Dialups/xp-dialup.html

GOOD LUCK
DDR DAN
0
 
LVL 5

Expert Comment

by:lidsky
ID: 12113671
Looking at the log file, it looks like you have an Aztech modem. Is that correct?
If it is, then it looks like the wrong inf file is being loaded ( oem4.inf ). Aztech inf files are named Azt????.inf

I suggest that you download the correct inf file (driver) from http://www.aztech.com/download.htm 

Providing that this is indeed an Aztech modem.
0
 
LVL 5

Expert Comment

by:XSINUX
ID: 12121537
Ok Try this .

Go to Control Panel > Phone and Modems > Click on the Modems Tab > Click on the "Properties" Button on the Modems Tab  > Click on the Modems Tab again and there you should find the Wait for Dial tone. Uncheck it from there.

If you have troubles finding the Tab then click here for assistance in Grafix.

http://www.laptoptravel.com/Article.aspx?ID=379

If you get some other Problems, then go to Go to Control Panel > Phone and Modems > Click on the Modems Tab > Click on the "Properties" Button on the Modems Tab  > Click on the advance Tab and in  the Extra Initialization Command put this setting " +MS=v90,0 "  Why we are doing this is because a v92 Modem may communicate much faster and there could be data mismatches. Hence the command would help the modem to work like a v90 modem. Probably this should help.

Also Make sure that there is no Line Disturbance and your Phone line that is connected to the Modem is less than 6ft to avoid data / signal loss. This is another reason why modems report no dial tone. The dial tone degrades having passed through longer lines and the modem may fail to detect it. But all my suggestions and troubleshooting would help you resolve this.

Hope this Helps

Cheers
Sinu.
0
 
LVL 5

Expert Comment

by:XSINUX
ID: 12121542
If you still have problem , then also Remove the Driver from  the Device Manager and Just Restart your computer. This will help if this is a Driver Related problem and if you are using the same Drivers

Good Luck

Sinu
0
 

Author Comment

by:jcolles
ID: 12334770
I found the solution!
All 3 modems which I had in stock were faulty.   2 had been removed from working systems with failed motherboards, and the third one was new in original box.   All were stored in anti-static bags.

I find this hard to believe, but I tried them all in another system, then bought a new modem and all worked fine.
Thanks to all of you for your suggestions, my apologies for not closing the question
0
 

Accepted Solution

by:
ee_ai_construct earned 0 total points
ID: 12335003
Question answered by asker or dialog valuable.
Closed, 125 points refunded.
ee_ai_construct (replacement part #xm34)
Community Support Admin
0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Connected but can't ping...interconnect between HP and Cisco Switch 2 55
ACS vs NAC 2 69
Create remote access home server 4 94
How much power fluctionation is too much? 4 56
 One of the main issues with network wires is that you never have enough.  You run plenty and plan for the worst case but you still end up needing more.  What many people do not realize is with 10BaseT and 100BaseT (but not 1000BaseT) networks you …
This article is a how to to configure a UCS Ethernet-uplink portchannel via the console. It is easy to do and can be done quite quickly. In certain versions of the UCS manager the portchannel has issues coming up and this is a workaround. I am…
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.
The Email Laundry PDF encryption service allows companies to send confidential encrypted  emails to anybody. The PDF document can also contain attachments that are embedded in the encrypted PDF. The password is randomly generated by The Email Laundr…

932 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now