 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Forum / Windows XP / Networking and Web / March 2004Modem connections always fail
Using any dialer (AOL, AT&T, MSN, etc.) cannot maintain a connection. The telephone number is dialed and modem negotiation occurs, one of three error messages occurs. All other networking operates OK, including a wireless card. The error message 20027 is reported elsewhere on the Internet without and solutions. The Knowledge Base is mute. Error 6 - the handle is invalid Error 50 - the request is not supported (Usually) Error 720 - No PPP control protocols configured These messages are reported in the "Event Log" Event Type: Warning Event Source: Rasman Event Category: None Event ID: 20027 Date: 3/26/2004 Time: 7:02:37 AM User: N/A Computer: ODIEMOBILE Description: Remote Access Connection Manager failed to start because NDISWAN could not be opened. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 02 00 00 00 .... Event Type: Warning Event Source: Rasman Event Category: None Event ID: 20027 Date: 3/26/2004 Time: 7:01:59 AM User: N/A Computer: ODIEMOBILE Description: Remote Access Connection Manager failed to start because NDISWAN could not be opened. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 02 00 00 00 .... Event Type: Error Event Source: NetBT Event Category: None Event ID: 4321 Date: 3/26/2004 Time: 6:54:00 AM User: N/A Computer: ODIEMOBILE Description: The name "GARUDA :1d" could not be registered on the Interface with IP address 192.168.1.102. The machine with the IP address 192.168.1.100 did not allow the name to be claimed by this machine. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 00 00 00 00 04 00 56 00 ......V. 0008: 00 00 00 00 e1 10 00 c0 ....á..À 0010: 01 01 00 00 01 00 00 c0 .......À 0018: 01 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ Event Type: Warning Event Source: Rasman Event Category: None Event ID: 20027 Date: 3/26/2004 Time: 6:53:46 AM User: N/A Computer: ODIEMOBILE Description: Remote Access Connection Manager failed to start because NDISWAN could not be opened. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 02 00 00 00 .... Event Type: Error Event Source: NetBT Event Category: None Event ID: 4311 Date: 3/26/2004 Time: 6:52:48 AM User: N/A Computer: ODIEMOBILE Description: Initialization failed because the driver device could not be created. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 00 00 00 00 01 00 58 00 ......X. 0008: 00 00 00 00 d7 10 00 c0 ....×..À 0010: 13 01 00 00 34 00 00 c0 ....4..À 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ Does device manager show any bad adapters under network adapters?  SignatureKen Wickes [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. Using any dialer (AOL, AT&T, MSN, etc.) cannot maintain a connection. The telephone number is dialed and modem negotiation occurs, one of three error messages occurs. All other networking operates OK, including a wireless card. The error message 20027 is reported elsewhere on the Internet without and solutions. The Knowledge Base is mute. Error 6 - the handle is invalid Error 50 - the request is not supported (Usually) Error 720 - No PPP control protocols configured These messages are reported in the "Event Log" Event Type: Warning Event Source: Rasman Event Category: None Event ID: 20027 Date: 3/26/2004 Time: 7:02:37 AM User: N/A Computer: ODIEMOBILE Description: Remote Access Connection Manager failed to start because NDISWAN could not be opened. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 02 00 00 00 .... Event Type: Warning Event Source: Rasman Event Category: None Event ID: 20027 Date: 3/26/2004 Time: 7:01:59 AM User: N/A Computer: ODIEMOBILE Description: Remote Access Connection Manager failed to start because NDISWAN could not be opened. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 02 00 00 00 .... Event Type: Error Event Source: NetBT Event Category: None Event ID: 4321 Date: 3/26/2004 Time: 6:54:00 AM User: N/A Computer: ODIEMOBILE Description: The name "GARUDA :1d" could not be registered on the Interface with IP address 192.168.1.102. The machine with the IP address 192.168.1.100 did not allow the name to be claimed by this machine. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 00 00 00 00 04 00 56 00 ......V. 0008: 00 00 00 00 e1 10 00 c0 ....?..? 0010: 01 01 00 00 01 00 00 c0 .......? 0018: 01 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ Event Type: Warning Event Source: Rasman Event Category: None Event ID: 20027 Date: 3/26/2004 Time: 6:53:46 AM User: N/A Computer: ODIEMOBILE Description: Remote Access Connection Manager failed to start because NDISWAN could not be opened. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 02 00 00 00 .... Event Type: Error Event Source: NetBT Event Category: None Event ID: 4311 Date: 3/26/2004 Time: 6:52:48 AM User: N/A Computer: ODIEMOBILE Description: Initialization failed because the driver device could not be created. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 00 00 00 00 01 00 58 00 ......X. 0008: 00 00 00 00 d7 10 00 c0 ....?..? 0010: 13 01 00 00 34 00 00 c0 ....4..? 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ Ken, NO -- all modem diagnostics work OK, and the model dials and connects correctly (I checked the modem log). The PPP protocol seems to fail after a small amount of information. See partial log attached. 03-20-2004 09:56:55.361 - File: C:\WINDOWS\System32 \tapisrv.dll, Version 5.1.2600 03-20-2004 09:56:55.361 - File: C:\WINDOWS\System32 \unimdm.tsp, Version 5.1.2600 03-20-2004 09:56:55.361 - File: C:\WINDOWS\System32 \unimdmat.dll, Version 5.1.2600 03-20-2004 09:56:55.361 - File: C:\WINDOWS\System32 \uniplat.dll, Version 5.1.2600 03-20-2004 09:56:55.361 - File: C:\WINDOWS\System32 \drivers\modem.sys, Version 5.1.2600 03-20-2004 09:56:55.361 - File: C:\WINDOWS\System32 \modemui.dll, Version 5.1.2600 03-20-2004 09:56:55.371 - File: C:\WINDOWS\System32 \mdminst.dll, Version 5.1.2600 03-20-2004 09:56:55.371 - Modem type: Agere Win Modem 03-20-2004 09:56:55.371 - Modem inf path: ltw2kg.inf 03-20-2004 09:56:55.371 - Modem inf section: Modem_PNP_DSVD 03-20-2004 09:56:55.371 - Matching hardware ID: pci\ven_11c1&dev_0448&cc_0780 03-20-2004 09:56:55.521 - Opening Modem 03-20-2004 09:56:55.521 - 115200,8,N,1, ctsfl=1, rtsctl=2 03-20-2004 09:56:55.521 - Initializing modem. 03-20-2004 09:56:55.531 - Send: AT<cr> 03-20-2004 09:56:55.541 - Recv: AT<cr> 03-20-2004 09:56:55.541 - Command Echo 03-20-2004 09:56:55.541 - Recv: <cr><lf>OK<cr><lf> 03-20-2004 09:56:55.541 - Interpreted response: OK 03-20-2004 09:56:55.551 - Send: AT &F E0 &C1 &D2 V1 S0=0 \V1<cr> 03-20-2004 09:56:55.551 - TSP(0000): Making Call 03-20-2004 09:56:55.711 - Recv: AT &F E0 &C1 &D2 V1 S0=0 \V1<cr> 03-20-2004 09:56:55.711 - Command Echo 03-20-2004 09:56:55.711 - Recv: <cr><lf>OK<cr><lf> 03-20-2004 09:56:55.711 - Interpreted response: OK 03-20-2004 09:56:55.721 - Send: ATS7=60S30=0L0M1\N3%C1 +DCS=1,1&K3B0B15B2X4<cr> 03-20-2004 09:56:55.731 - Recv: <cr><lf>OK<cr><lf> 03-20-2004 09:56:55.731 - Interpreted response: OK 03-20-2004 09:56:55.731 - Waiting for a call. 03-20-2004 09:56:55.741 - Send: ATS0=0<cr> 03-20-2004 09:56:55.751 - Recv: <cr><lf>OK<cr><lf> 03-20-2004 09:56:55.751 - Interpreted response: OK 03-20-2004 09:56:55.751 - 115200,8,N,1, ctsfl=1, rtsctl=2 03-20-2004 09:56:55.751 - Initializing modem. 03-20-2004 09:56:55.761 - Send: AT<cr> 03-20-2004 09:56:55.771 - Recv: <cr><lf>OK<cr><lf> 03-20-2004 09:56:55.771 - Interpreted response: OK 03-20-2004 09:56:55.781 - Send: AT &F E0 &C1 &D2 V1 S0=0 \V1<cr> 03-20-2004 09:56:55.941 - Recv: <cr><lf>OK<cr><lf> 03-20-2004 09:56:55.941 - Interpreted response: OK 03-20-2004 09:56:55.951 - Send: ATS7=60S30=0L0M1\N3%C1 +DCS=1,1&K3B0B15B2X4<cr> 03-20-2004 09:56:55.961 - Recv: <cr><lf>OK<cr><lf> 03-20-2004 09:56:55.961 - Interpreted response: OK 03-20-2004 09:56:55.961 - Dialing. 03-20-2004 09:56:55.961 - TSP Completing Async Operation (0x000102c1) Status 0x00000000 03-20-2004 09:56:55.961 - TSP(0000): LINEEVENT: LINECALLSTATE_DIALING 03-20-2004 09:56:55.961 - TSP(0000): LINEEVENT: LINECALLSTATE_PROCEEDING 03-20-2004 09:56:55.971 - Send: ATDT###########<cr> 03-20-2004 09:57:27.316 - Recv: <cr><lf>CONNECT 48000 V42bis<cr><lf> 03-20-2004 09:57:27.316 - Interpreted response: Connect 03-20-2004 09:57:27.316 - Receive Connect but CD was low, Waiting for signal to go high 03-20-2004 09:57:27.337 - CD has been raised 03-20-2004 09:57:27.337 - Connection established at 48000bps. 03-20-2004 09:57:27.337 - Error-control on. 03-20-2004 09:57:27.337 - Data compression on. 03-20-2004 09:57:27.337 - TSP(0000): LINEEVENT: LINECALLSTATE_CONNECTED 03-20-2004 09:57:27.367 - TSP(0000): Dropping Call 03-20-2004 09:57:27.367 - Hanging up the modem. 03-20-2004 09:57:27.367 - Hardware hangup by lowering DTR. 03-20-2004 09:57:27.807 - Detected CD dropped from lowering DTR 03-20-2004 09:57:27.807 - Recv: <cr><lf>OK<cr><lf> 03-20-2004 09:57:27.807 - Interpreted response: OK 03-20-2004 09:57:27.817 - Send: ATH E1<cr> 03-20-2004 09:57:27.977 - Recv: <cr><lf>OK<cr><lf> 03-20-2004 09:57:27.977 - Interpreted response: OK 03-20-2004 09:57:27.977 - 115200,8,N,1, ctsfl=1, rtsctl=2 03-20-2004 09:57:27.977 - Initializing modem. 03-20-2004 09:57:27.987 - Send: AT<cr> 03-20-2004 09:57:27.997 - Recv: AT<cr> 03-20-2004 09:57:27.997 - Command Echo 03-20-2004 09:57:27.997 - Recv: <cr><lf>OK<cr><lf> 03-20-2004 09:57:27.997 - Interpreted response: OK 03-20-2004 09:57:28.007 - Send: AT &F E0 &C1 &D2 V1 S0=0 \V1<cr> 03-20-2004 09:57:28.168 - Recv: AT &F E0 &C1 &D2 V1 S0=0 \V1<cr> 03-20-2004 09:57:28.168 - Command Echo 03-20-2004 09:57:28.168 - Recv: <cr><lf>OK<cr><lf> 03-20-2004 09:57:28.168 - Interpreted response: OK 03-20-2004 09:57:28.178 - Send: ATS7=60S30=0L0M1\N3%C1 +DCS=1,1&K3B0B15B2X4<cr> 03-20-2004 09:57:28.188 - Recv: <cr><lf>OK<cr><lf> 03-20-2004 09:57:28.188 - Interpreted response: OK 03-20-2004 09:57:28.188 - Waiting for a call. 03-20-2004 09:57:28.198 - Send: ATS0=0<cr> 03-20-2004 09:57:28.208 - Recv: <cr><lf>OK<cr><lf> 03-20-2004 09:57:28.208 - Interpreted response: OK 03-20-2004 09:57:28.208 - TSP(0000): LINEEVENT: LINECALLSTATE_DISCONNECTED(0x1) 03-20-2004 09:57:28.208 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE 03-20-2004 09:57:28.208 - TSP Completing Async Operation (0x0001025a) Status 0x00000000 03-20-2004 09:57:28.208 - TSP(0000): Dropping Call 03-20-2004 09:57:28.208 - TSP Completing Async Operation (0x0001026b) Status 0x00000000 03-20-2004 09:57:28.208 - TSP(0000): Closing Call 03-20-2004 09:57:28.208 - Session Statistics: 03-20-2004 09:57:28.208 - Reads : 55 bytes 03-20-2004 09:57:28.208 - Writes: 82 bytes >-----Original Message----- >Does device manager show any bad adapters under network adapters? Well I don't see anything obvious here. But I'm not an expert in modems either. Maybe someone else will see something. SignatureKen Wickes [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. > Ken, > [quoted text clipped - 131 lines] > > > confers no rights. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.