DIAL-UP PROBLEMS: Need some suggestions/recommendations for
DComTalk.com Forum Index DComTalk.com
Discussion of VoIP, VPN, Video Conferencen, DSL and other data commucations.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web dcomtalk.com
DIAL-UP PROBLEMS: Need some suggestions/recommendations for

 
Post new topic   Reply to topic    DComTalk.com Forum Index -> Modems
Author Message
CURIOUS ANGEL
Guest
Posted: Sun Jul 31, 2005 12:20 am    Post subject: DIAL-UP PROBLEMS: Need some suggestions/recommendations for Reply with quote
Hi folks,

Every now and then my ISP will not _complete_ my Dial-Up connection due
to inordinate heavy useage (such as recently, having just built a new
Windows 2000 Pro computer). What happens is the call is placed and it
just keeps showing "Dialing" on the little Windows 2000 Dial-Up screen.

At times like this when I am inside my chassis and fooling around with
drives & other hardware during a build, I can't DISTINGUISH when the
failure to complete my Dial-Up connection is mine (because I'm
jumpering this and disconnecting that) . . . or just my ISP giving me
grief for being online so much (to learn how to jumper this and
disconnect that lol).

What I'm trying to access is intelligence on the source of the failure
to complete my Dial-Up, so I can at a minimum isolate the problem as
not being on MY end.

I know that, somewhere, a log is being kept. Could any of you Modem
Gurus ;) give me some guidance here as to (hopefully simple) actions I
can take to understand why I am not connecting? In other words, I
trust the modem would report some kind of data in a log somewhere that
says something like "The carrier isn't authorizing you to proceed with
the connection, even though your call is obviously placed and the phone
line is in use"? Some kind of TRACE string? A PING of some sort?

I remember years ago there was a trick to this and I can't remember it.
It's all a fog since I started this build lol.

Thanks if anyone can help! Then at least I'll know the problem isn't
on my end. ;)

Angel
Back to top
Gary A. Edelstein
Guest
Posted: Sun Jul 31, 2005 9:35 pm    Post subject: Re: DIAL-UP PROBLEMS: Need some suggestions/recommendations Reply with quote
On 30 Jul 2005 15:25:21 -0700, "CURIOUS ANGEL" <byte.this@usa.net>
wrote:

Quote:
Hi folks,

Every now and then my ISP will not _complete_ my Dial-Up connection due
to inordinate heavy useage (such as recently, having just built a new
Windows 2000 Pro computer). What happens is the call is placed and it
just keeps showing "Dialing" on the little Windows 2000 Dial-Up screen.

This is strange. Normally, if they think your time is up, then the

remote modem would likely just hang up. What you are saying is
happing is the connection, and their remote modem are being tied up,
but you aren't getting a completed connection and an IP. I don't know
why your ISP would allow a modem to be tied up in that situation.

Quote:
At times like this when I am inside my chassis and fooling around with
drives & other hardware during a build, I can't DISTINGUISH when the
failure to complete my Dial-Up connection is mine (because I'm
jumpering this and disconnecting that) . . . or just my ISP giving me
grief for being online so much (to learn how to jumper this and
disconnect that lol).

What I'm trying to access is intelligence on the source of the failure
to complete my Dial-Up, so I can at a minimum isolate the problem as
not being on MY end.

I know that, somewhere, a log is being kept. Could any of you Modem
Gurus ;) give me some guidance here as to (hopefully simple) actions I
can take to understand why I am not connecting? In other words, I
trust the modem would report some kind of data in a log somewhere that
says something like "The carrier isn't authorizing you to proceed with
the connection, even though your call is obviously placed and the phone
line is in use"? Some kind of TRACE string? A PING of some sort?

I remember years ago there was a trick to this and I can't remember it.
It's all a fog since I started this build lol.

Thanks if anyone can help! Then at least I'll know the problem isn't
on my end. ;)

Here's how to view the log. Post the complete log back here and we

can take a look.

http://www.modemsite.com/56k/modemlog2k.asp

Gary E
--
|Gary A. Edelstein
|edelsgNO@SPAMyahoo.com.invalid (remove NO SPAM and .invalid to reply)
|"We have met the enemy and he is us." - Walt Kelly's Pogo
Back to top
CURIOUS ANGEL
Guest
Posted: Sun Jul 31, 2005 11:15 pm    Post subject: Re: DIAL-UP PROBLEMS: Need some suggestions/recommendations Reply with quote
Gary A. Edelstein wrote:
Quote:
On 30 Jul 2005 15:25:21 -0700, "CURIOUS ANGEL" <byte.this@usa.net
wrote:

This is strange. Normally, if they think your time is up, then the
remote modem would likely just hang up. What you are saying is
happing is the connection, and their remote modem are being tied up,
but you aren't getting a completed connection and an IP. I don't know
why your ISP would allow a modem to be tied up in that situation.

Here's how to view the log. Post the complete log back here and we
can take a look.

http://www.modemsite.com/56k/modemlog2k.asp

Gary E

Hey Gary! Will do. Yeah, it's strange I can tell you. Luckily I
connect on an External (V.90 56k) modem, and have become somewhat
"attuned" to listening to the drone sound that indicates that --
although my phone line is being used, and I've clearly completed the
dialing portion of the routine -- I've hit the wall, and might as well
disconnect unless I want to sit there for hours grinding away.

Angel
Back to top
CURIOUS ANGEL
Guest
Posted: Mon Aug 01, 2005 9:28 pm    Post subject: Re: DIAL-UP PROBLEMS: Need some suggestions/recommendations Reply with quote
Almost forgot: When I couldn't get the modem to connect on my regular
connection, I created a **NEW** connection, and thus connected.

I was just glancing at this log. Hmm. I could have sworn the
problem-connect occurred later in the day but . . . it's all a blur lol.

If we can't see it here for some reason I'll see if I can't trigger it
again and repost. Thanks Gary.

Angel
Back to top
CURIOUS ANGEL
Guest
Posted: Tue Aug 02, 2005 12:20 am    Post subject: Re: DIAL-UP PROBLEMS: Okay! Here's a RECENT CRASH log . . . Reply with quote
This _just_ happened Gary. I had to connect using one of my older
(previously-failed) connections. Don't ask me why it worked this time.
Picked up as of Line 721:

721___08-01-2005 12:41:39.093 - File: C:\WINNT\system32\unimdm.tsp,
Version 5.0.2195 - Retail
722___08-01-2005 12:41:39.109 - File: C:\WINNT\system32\unimdmat.dll,
Version 5.0.2195 - Retail
723___08-01-2005 12:41:39.125 - File: C:\WINNT\system32\uniplat.dll,
Version 5.0.2195 - Retail
724___08-01-2005 12:41:39.171 - File:
C:\WINNT\system32\drivers\modem.sys, Version 5.0.2195 - Retail
725___08-01-2005 12:41:39.171 - File: C:\WINNT\system32\modemui.dll,
Version 5.0.2195 - Retail
726___08-01-2005 12:41:39.171 - Modem type: Rockwell 56K ACF II
Fax+Data+Voice Modem
727___08-01-2005 12:41:39.171 - Modem inf path: oem1.inf
728___08-01-2005 12:41:39.171 - Modem inf section: Install_ext
729___08-01-2005 12:41:42.171 - Opening Modem
730___08-01-2005 12:41:42.171 - 115200,8,N,1, ctsfl=1, rtsctl=2
731___08-01-2005 12:41:42.171 - Initializing modem.
732___08-01-2005 12:41:42.187 - Send: AT<cr>
733___08-01-2005 12:41:42.187 - Recv: <cr><lf>OK<cr><lf>
734___08-01-2005 12:41:42.187 - Interpreted response: OK
735___08-01-2005 12:41:42.203 - Send: AT&FE0V1&C1&D2S95=0S0=0<cr>
736___08-01-2005 12:41:42.203 - Recv: <cr><lf>OK<cr><lf>
737___08-01-2005 12:41:42.203 - Interpreted response: OK
738___08-01-2005 12:41:42.218 - Send: ATS7=60S30=0L1M1\N3%C3&K3BN1X4<cr>
739___08-01-2005 12:41:42.218 - TSP(0000): Making call
740___08-01-2005 12:41:42.218 - Recv: <cr><lf>OK<cr><lf>
741___08-01-2005 12:41:42.218 - Interpreted response: OK
742___08-01-2005 12:41:42.218 - Waiting for a call.
743___08-01-2005 12:41:42.234 - Send: at#cid=1<cr>
744___08-01-2005 12:41:42.234 - Recv: <cr><lf>OK<cr><lf>
745___08-01-2005 12:41:42.234 - Interpreted response: OK
746___08-01-2005 12:41:42.250 - Send: ATS0=0<cr>
747___08-01-2005 12:41:42.250 - Recv: <cr><lf>OK<cr><lf>
748___08-01-2005 12:41:42.250 - Interpreted response: OK
749___08-01-2005 12:41:42.250 - 115200,8,N,1, ctsfl=1, rtsctl=2
750___08-01-2005 12:41:42.250 - Initializing modem.
751___08-01-2005 12:41:42.265 - Send: AT<cr>
752___08-01-2005 12:41:42.265 - Recv: <cr><lf>OK<cr><lf>
753___08-01-2005 12:41:42.265 - Interpreted response: OK
754___08-01-2005 12:41:42.281 - Send: AT&FE0V1&C1&D2S95=0S0=0<cr>
755___08-01-2005 12:41:42.281 - Recv: <cr><lf>OK<cr><lf>
756___08-01-2005 12:41:42.281 - Interpreted response: OK
757___08-01-2005 12:41:42.296 - Send: ATS7=60S30=0L1M1\N3%C3&K3BN1X4<cr>
758___08-01-2005 12:41:42.296 - Recv: <cr><lf>OK<cr><lf>
759___08-01-2005 12:41:42.296 - Interpreted response: OK
760___08-01-2005 12:41:42.296 - Dialing.
761___08-01-2005 12:41:42.296 - TSP(0000): LINEEVENT: LINECALLSTATE_DIALING
762___08-01-2005 12:41:42.296 - TSP(0000): LINEEVENT:
LINECALLSTATE_PROCEEDING
763___08-01-2005 12:41:42.312 - Send: ATDT###-####<cr>
764___08-01-2005 12:42:08.890 - TSP(0000): Dropping call
765___08-01-2005 12:42:08.890 - Attempting to abort current command
766___08-01-2005 12:42:08.890 - Send: <cr>
767___08-01-2005 12:42:10.625 - Recv: <cr>
768___08-01-2005 12:42:10.625 - Interpreted response: Informative
769___08-01-2005 12:42:10.625 - Recv: <lf>
770___08-01-2005 12:42:10.625 - Interpreted response: Informative
771___08-01-2005 12:42:10.625 - Recv: NO CARRIER
772___08-01-2005 12:42:10.625 - Interpreted response: No Carrier
773___08-01-2005 12:42:10.625 - Hanging up the modem.
774___08-01-2005 12:42:10.640 - Send: ATH<cr>
775___08-01-2005 12:42:10.640 - Recv: <cr>
776___08-01-2005 12:42:10.640 - Interpreted response: Informative
777___08-01-2005 12:42:10.640 - Recv: <lf>
778___08-01-2005 12:42:10.640 - Interpreted response: Informative
779___08-01-2005 12:42:10.640 - Recv: <cr><lf>OK<cr><lf>
780___08-01-2005 12:42:10.640 - Interpreted response: OK
781___08-01-2005 12:42:10.640 - 115200,8,N,1, ctsfl=1, rtsctl=2
782___08-01-2005 12:42:10.640 - Initializing modem.
783___08-01-2005 12:42:10.656 - Send: AT<cr>
784___08-01-2005 12:42:10.656 - Recv: <cr><lf>OK<cr><lf>
785___08-01-2005 12:42:10.656 - Interpreted response: OK
786___08-01-2005 12:42:10.671 - Send: AT&FE0V1&C1&D2S95=0S0=0<cr>
787___08-01-2005 12:42:10.671 - Recv: <cr><lf>OK<cr><lf>
788___08-01-2005 12:42:10.671 - Interpreted response: OK
789___08-01-2005 12:42:10.687 - Send: ATS7=60S30=0L1M1\N3%C3&K3BN1X4<cr>
790___08-01-2005 12:42:10.687 - Recv: <cr><lf>OK<cr><lf>
791___08-01-2005 12:42:10.687 - Interpreted response: OK
792___08-01-2005 12:42:10.687 - Waiting for a call.
793___08-01-2005 12:42:10.703 - Send: at#cid=1<cr>
794___08-01-2005 12:42:10.703 - Recv: <cr><lf>OK<cr><lf>
795___08-01-2005 12:42:10.703 - Interpreted response: OK
796___08-01-2005 12:42:10.718 - Send: ATS0=0<cr>
797___08-01-2005 12:42:10.718 - Recv: <cr><lf>OK<cr><lf>
798___08-01-2005 12:42:10.718 - Interpreted response: OK
799___08-01-2005 12:42:10.718 - TSP(0000): LINEEVENT:
LINECALLSTATE_DISCONNECTED(0x1)
800___08-01-2005 12:42:10.718 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE
801___08-01-2005 12:42:10.718 - TSP(0000): Dropping call
802___08-01-2005 12:42:10.718 - TSP(0000): Closing Call
803___08-01-2005 12:42:10.718 - Session Statistics:
804___08-01-2005 12:42:10.718 - Reads : 30 bytes
805___08-01-2005 12:42:10.718 - Writes: 74 bytes
Back to top
Gary A. Edelstein
Guest
Posted: Wed Aug 03, 2005 4:20 pm    Post subject: Re: DIAL-UP PROBLEMS: Need some suggestions/recommendations Reply with quote
On Mon, 01 Aug 2005 09:28:44 -0700, CURIOUS ANGEL <byte.this@usa.net>
wrote:

Quote:
Almost forgot: When I couldn't get the modem to connect on my regular
connection, I created a **NEW** connection, and thus connected.

I was just glancing at this log. Hmm. I could have sworn the
problem-connect occurred later in the day but . . . it's all a blur lol.

If we can't see it here for some reason I'll see if I can't trigger it
again and repost. Thanks Gary.

I see a couple problems at your end reading the logs:


- It appears you are using the wrong driver and inf file for the
modem. The correct one would give the modem to modem connect rate and
error correction status rather than just the the port rate with
unknown error correction. If you are using the wrong driver and/or
inf, then the modem may be in the wrong state to correctly communicate
with the remote modem, which may be why you are having communication
problems.

583___08-01-2005 07:37:39.671 - Recv: CONNECT 115200
584___08-01-2005 07:37:39.671 - Interpreted response: Connect
585___08-01-2005 07:37:39.671 - Connection established at 115200bps.
586___08-01-2005 07:37:39.671 - Error-control off or unknown.
587___08-01-2005 07:37:39.671 - Data compression off or unknown.

- For some reason, either due to line conditions, wrong driver and/or
inf or a problem at the isp end, the modem isn't always communicating
correctly, as seen by continual communication attempts without proper
resolution - seen by data reads and writes and a subsequent drop of
the connection by the remote modem. I think that's what's happening
when you think the isp is dropping you due to traffic.

<snipped repeated read and write messages>
490___07-31-2005 19:48:08.421 - Read: Total: 64315700, Per/Sec: 650,
Written: Total: 3030015, Per/Sec: 82
491___07-31-2005 19:50:08.421 - Read: Total: 64349155, Per/Sec: 278,
Written: Total: 3034748, Per/Sec: 39
492___07-31-2005 19:52:08.421 - Read: Total: 64380619, Per/Sec: 262,
Written: Total: 3041624, Per/Sec: 57
493___07-31-2005 19:54:08.437 - Read: Total: 64409936, Per/Sec: 244,
Written: Total: 3045093, Per/Sec: 28
494___07-31-2005 19:54:43.000 - CD dropped--Remote modem hung up.
ModemStatus=00000030

Gary E
--
|Gary A. Edelstein
|edelsgNO@SPAMyahoo.com.invalid (remove NO SPAM and .invalid to reply)
|"We have met the enemy and he is us." - Walt Kelly's Pogo
Back to top
Franc Zabkar
Guest
Posted: Thu Aug 04, 2005 12:20 am    Post subject: Re: DIAL-UP PROBLEMS: Need some suggestions/recommendations Reply with quote
On Wed, 03 Aug 2005 11:11:20 -0500, Gary A. Edelstein
<edelsgNO@SPAMyahoo.com.invalid> put finger to keyboard and composed:

Quote:
On Mon, 01 Aug 2005 09:28:44 -0700, CURIOUS ANGEL <byte.this@usa.net
wrote:

Almost forgot: When I couldn't get the modem to connect on my regular
connection, I created a **NEW** connection, and thus connected.

I was just glancing at this log. Hmm. I could have sworn the
problem-connect occurred later in the day but . . . it's all a blur lol.

If we can't see it here for some reason I'll see if I can't trigger it
again and repost. Thanks Gary.

I see a couple problems at your end reading the logs:

- It appears you are using the wrong driver and inf file for the
modem. The correct one would give the modem to modem connect rate and
error correction status rather than just the the port rate with
unknown error correction. If you are using the wrong driver and/or
inf, then the modem may be in the wrong state to correctly communicate
with the remote modem, which may be why you are having communication
problems.

583___08-01-2005 07:37:39.671 - Recv: CONNECT 115200
584___08-01-2005 07:37:39.671 - Interpreted response: Connect
585___08-01-2005 07:37:39.671 - Connection established at 115200bps.
586___08-01-2005 07:37:39.671 - Error-control off or unknown.
587___08-01-2005 07:37:39.671 - Data compression off or unknown.

The problem appears to be the "S95=0" in one of the init strings. I
suggest that the OP add S95=45 to his/her Extra Settings.


- Franc Zabkar
--
Please remove one 's' from my address when replying by email.
Back to top
 
Post new topic   Reply to topic    DComTalk.com Forum Index -> Modems All times are GMT
Page 1 of 1

 
 You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




VoIP Solutions: Telephone Systems Electronics Satellite TV Tech & Gadgets
Powered by phpBB