P
Post Master
Symptoms - dialup works via PABX but not on residential phone line,
seems to fail during/after authentication.
Win-XP(Home)
Microsoft Firewall enabled
Intel Celeron 2.7 GHz
Modem type: Smart Link 56K Voice Modem
If I initiate the dialup via Internet Explorers "Connect" window I get
one of two
failure modes :
Dialing attempt 1.
Dialing...
Unable to establish a connection.
Dialing attempt 1.
Dialing...
Unable to connect because of a configuration error.
This is not an insurmountable problem, as I can init. the dialup from
the network connections on the startup menu, properties -> Dial now
The connection via my work PABX is as expected.
However when I dial from home, same sort of copper phone line (only
difference is send a preceding 0 to get a PABX line, at home I post-fix
a four digit PIN for my home phone), I get the errors below after
authentication.
I wonder if this could be related to the firewall? I have read in other
posts that this has caused problems and disabling it has solved these.
I should be able to disable the firewall during the dialup and then
enable it straight after should I not. But why different behaviour
between the PABX and residential dialup?
I know that the user details below are correct because these work via
the PABX dialup. But I do not get the typical "User Authenicated" type
confirmation immediately after password is read - suggesting that the
problem may be related to incorrect transfer of the password.
The @#}..@#} responses get steadily echoed to the screen for a couple
of minutes then eventually the connection dies.
User Access Verification
username:[email protected]
password:shpxlbh
~~ÿ}#À!}!}.} %}"}&} }*} } }#}$À#}%}&}%"ÿ
}'}"}(}"}1}$}%ô}3})}!isdnx2ÝÃ~~ÿ}#À!}!}/} %}"}&} }*} }
}#}$À#}%}&}%"ÿ }'}"}(}"}1}$}%ô}3})}!isdnx2'o~~ÿ}#À!}!}0}
%}"}&} }*} } }#}$À#}%}&}%"ÿ
}'}"}(}"}1}$}%ô}3})}!isdnx2;ì~~ÿ}#À!}!}1} %}"}&} }*} }
}#}$À#}%}&}%"ÿ }'}"}(}"}1}$}%ô}3})}!isdnx2t@~~ÿ}#À!}!}2} %}"}&}
}*} } }#}$À#}%}&}%"ÿ }'}"}(}"}1}$}%ô}3})}!isdnx2´¼~~ÿ}#À!}!}3}
%}"}&} }*} } }#}$À#}%}&}%"ÿ
}'}"}(}"}1}$}%ô}3})}!isdnx2û}0~~ÿ}#À!}!}4} %}"}&} }*} }
}#}$À#}%}&}%"ÿ }'}"}(}"}1}$}%ô}3})}!isdnx2%M~~ÿ}#À!}!}5} %}"}&}
}*} } }#}$À#}%}&}%"ÿ }'}"}(}"}1}$}%ô}3}
and
username:[email protected]
password:shpxlbh
~~ÿ}#À!}!m} %}"}&} }*} }
}#}$À#}%}&}0lVÜ}'}"}(}"}1}$}%ô}3})}!isdnx2ëe~~ÿ}#À!}!n} %}"}&}
}*} } }#}$À#}%}&}0lVÜ}'}"}(}"}1}$}%ô}3})}!isdnx2+™~~ÿ}#À!}!o}
%}"}&} }*} }
}#}$À#}%}&}0lVÜ}'}"}(}"}1}$}%ô}3})}!isdnx2d5~~ÿ}#À!}!p} %}"}&} }*}
} }#}$À#}%}&}0lVÜ}'}"}(}"}1}$}%ô}3})}!isdnx2Ͷ~~ÿ}#À!}!q} %}"}&}
}*} } }#}$À#}%}&}0lVÜ}'}"}(}"}1}$}%ô}3})}!isdnx2,}:~~ÿ}#À!}!r}
%}"}&} }*} }
}#}$À#}%}&}0lVÜ}'}"}(}"}1}$}%ô}3})}!isdnx2Bæ~~ÿ}#À!}!s} %}"}&}
}*} } }#}$À#}%}&}0lVÜ}'}"}(}"}1}$}%ô}3})}!isdnx2}-J~~ÿ}#À!}!t}
%}"}&} }*} }
}#}$À#}%}&}0lVÜ}'}"}(}"}1}$}%ô}3})}!isdnx2Ó}7~~ÿ}#À!}!u} %}"}&}
}*} } }#}$À#}%}&}0lVÜ}'}"}(}"}1}$}%ô}3})}!isdnx2œ»~~ÿ}#À!}!v}
%}"}&} }*} } }#}$À#}%}&}0lVÜ}'}"}(}"}1}$}%ô}3})}!isdnx2\G~
Here is the modem log (below), the three instances with ====
underlining concern me, why should an abort be initiated when there is
no apparent cause for this? Why so much activity after the abort? Is it
possible that all of the above gumf is actually generated on my side
and has not come from the ISP ?
C:\WINDOWS\ModemLog_Smart Link 56K Voice Modem.txt
22:07:25.046 - File: C:\WINDOWS\system32\tapisrv.dll, Version 5.1.2600
22:07:25.046 - File: C:\WINDOWS\system32\unimdm.tsp, Version 5.1.2600
22:07:25.046 - File: C:\WINDOWS\system32\unimdmat.dll, Version 5.1.2600
22:07:25.046 - File: C:\WINDOWS\system32\uniplat.dll, Version 5.1.2600
22:07:25.046 - File: C:\WINDOWS\system32\drivers\modem.sys, Version
5.1.2600
22:07:25.046 - File: C:\WINDOWS\system32\modemui.dll, Version 5.1.2600
22:07:25.046 - File: C:\WINDOWS\system32\mdminst.dll, Version 5.1.2600
22:07:25.046 - Modem type: Smart Link 56K Voice Modem
22:07:25.046 - Modem inf path: mdmhamrw.inf
22:07:25.046 - Modem inf section: Modem1
22:07:25.046 - Matching hardware ID:
pci\ven_2000&dev_2800&subsys_2800163c
22:07:25.125 - 460800,8,N,1, ctsfl=1, rtsctl=2
22:07:25.125 - Initializing modem.
22:07:25.140 - Send: AT<cr>
22:07:25.140 - Recv: <cr><lf>OK<cr><lf>
22:07:25.140 - Interpreted response: OK
22:07:25.156 - Send: AT &F E0 V1 &A3 &D2 &C1 S0=0<cr>
22:07:25.156 - Recv: <cr><lf>OK<cr><lf>
22:07:25.156 - Interpreted response: OK
22:07:25.171 - Send: ATS7=60S19=0L1M1\N3%C3&H1N1X4<cr>
22:07:25.171 - Recv: <cr><lf>OK<cr><lf>
22:07:25.171 - Interpreted response: OK
22:07:25.171 - Waiting for a call.
22:07:25.187 - Send: at#cid=1<cr>
22:07:25.187 - Recv: <cr><lf>OK<cr><lf>
22:07:25.187 - Interpreted response: OK
22:07:25.203 - Send: ATS0=0<cr>
22:07:25.203 - Recv: <cr><lf>OK<cr><lf>
22:07:25.203 - Interpreted response: OK
22:07:25.203 - 115200,8,N,1, ctsfl=1, rtsctl=2
22:07:25.203 - Initializing modem.
22:07:25.218 - Send: AT<cr>
22:07:25.218 - Recv: <cr><lf>OK<cr><lf>
22:07:25.218 - Interpreted response: OK
22:07:25.234 - Send: AT &F E0 V1 &A3 &D2 &C1 S0=0<cr>
22:07:25.234 - Recv: <cr><lf>OK<cr><lf>
22:07:25.234 - Interpreted response: OK
22:07:25.250 - Send: ATS7=60S19=0L1M1\N3%C3&H1N1X4<cr>
22:07:25.250 - Recv: <cr><lf>OK<cr><lf>
22:07:25.250 - Interpreted response: OK
22:07:25.250 - Dialing.
22:07:25.265 - Send: ATDT*###,,,,,,####,,,,,,#,,,,,,#<cr>
22:07:29.750 - Attempting to abort current command
==================================================
22:07:29.750 - Send: <cr>
22:07:30.062 - Recv: <cr><lf>NO CARRIER<cr><lf>
22:07:30.062 - Interpreted response: No Carrier
==================================================
22:07:30.062 - Hanging up the modem.
==================================================
22:07:30.078 - Send: ATH<cr>
22:07:30.093 - Recv: <cr><lf>OK<cr><lf>
22:07:30.093 - Interpreted response: OK
22:07:30.093 - 460800,8,N,1, ctsfl=1, rtsctl=2
22:07:30.093 - Initializing modem.
22:07:30.109 - Send: AT<cr>
22:07:30.109 - Recv: <cr><lf>OK<cr><lf>
22:07:30.109 - Interpreted response: OK
22:07:30.125 - Send: AT &F E0 V1 &A3 &D2 &C1 S0=0<cr>
22:07:30.125 - Recv: <cr><lf>OK<cr><lf>
22:07:30.125 - Interpreted response: OK
22:07:30.140 - Send: ATS7=60S19=0L1M1\N3%C3&H1N1X4<cr>
22:07:30.140 - Recv: <cr><lf>OK<cr><lf>
22:07:30.140 - Interpreted response: OK
22:07:30.140 - Waiting for a call.
22:07:30.156 - Send: at#cid=1<cr>
22:07:30.156 - Recv: <cr><lf>OK<cr><lf>
22:07:30.156 - Interpreted response: OK
22:07:30.171 - Send: ATS0=0<cr>
22:07:30.171 - Recv: <cr><lf>OK<cr><lf>
22:07:30.171 - Interpreted response: OK
22:07:30.171 - Session Statistics:
22:07:30.171 - Reads : 30 bytes
22:07:30.171 - Writes: 78 bytes
seems to fail during/after authentication.
Win-XP(Home)
Microsoft Firewall enabled
Intel Celeron 2.7 GHz
Modem type: Smart Link 56K Voice Modem
If I initiate the dialup via Internet Explorers "Connect" window I get
one of two
failure modes :
Dialing attempt 1.
Dialing...
Unable to establish a connection.
Dialing attempt 1.
Dialing...
Unable to connect because of a configuration error.
This is not an insurmountable problem, as I can init. the dialup from
the network connections on the startup menu, properties -> Dial now
The connection via my work PABX is as expected.
However when I dial from home, same sort of copper phone line (only
difference is send a preceding 0 to get a PABX line, at home I post-fix
a four digit PIN for my home phone), I get the errors below after
authentication.
I wonder if this could be related to the firewall? I have read in other
posts that this has caused problems and disabling it has solved these.
I should be able to disable the firewall during the dialup and then
enable it straight after should I not. But why different behaviour
between the PABX and residential dialup?
I know that the user details below are correct because these work via
the PABX dialup. But I do not get the typical "User Authenicated" type
confirmation immediately after password is read - suggesting that the
problem may be related to incorrect transfer of the password.
The @#}..@#} responses get steadily echoed to the screen for a couple
of minutes then eventually the connection dies.
User Access Verification
username:[email protected]
password:shpxlbh
~~ÿ}#À!}!}.} %}"}&} }*} } }#}$À#}%}&}%"ÿ
}'}"}(}"}1}$}%ô}3})}!isdnx2ÝÃ~~ÿ}#À!}!}/} %}"}&} }*} }
}#}$À#}%}&}%"ÿ }'}"}(}"}1}$}%ô}3})}!isdnx2'o~~ÿ}#À!}!}0}
%}"}&} }*} } }#}$À#}%}&}%"ÿ
}'}"}(}"}1}$}%ô}3})}!isdnx2;ì~~ÿ}#À!}!}1} %}"}&} }*} }
}#}$À#}%}&}%"ÿ }'}"}(}"}1}$}%ô}3})}!isdnx2t@~~ÿ}#À!}!}2} %}"}&}
}*} } }#}$À#}%}&}%"ÿ }'}"}(}"}1}$}%ô}3})}!isdnx2´¼~~ÿ}#À!}!}3}
%}"}&} }*} } }#}$À#}%}&}%"ÿ
}'}"}(}"}1}$}%ô}3})}!isdnx2û}0~~ÿ}#À!}!}4} %}"}&} }*} }
}#}$À#}%}&}%"ÿ }'}"}(}"}1}$}%ô}3})}!isdnx2%M~~ÿ}#À!}!}5} %}"}&}
}*} } }#}$À#}%}&}%"ÿ }'}"}(}"}1}$}%ô}3}
and
username:[email protected]
password:shpxlbh
~~ÿ}#À!}!m} %}"}&} }*} }
}#}$À#}%}&}0lVÜ}'}"}(}"}1}$}%ô}3})}!isdnx2ëe~~ÿ}#À!}!n} %}"}&}
}*} } }#}$À#}%}&}0lVÜ}'}"}(}"}1}$}%ô}3})}!isdnx2+™~~ÿ}#À!}!o}
%}"}&} }*} }
}#}$À#}%}&}0lVÜ}'}"}(}"}1}$}%ô}3})}!isdnx2d5~~ÿ}#À!}!p} %}"}&} }*}
} }#}$À#}%}&}0lVÜ}'}"}(}"}1}$}%ô}3})}!isdnx2Ͷ~~ÿ}#À!}!q} %}"}&}
}*} } }#}$À#}%}&}0lVÜ}'}"}(}"}1}$}%ô}3})}!isdnx2,}:~~ÿ}#À!}!r}
%}"}&} }*} }
}#}$À#}%}&}0lVÜ}'}"}(}"}1}$}%ô}3})}!isdnx2Bæ~~ÿ}#À!}!s} %}"}&}
}*} } }#}$À#}%}&}0lVÜ}'}"}(}"}1}$}%ô}3})}!isdnx2}-J~~ÿ}#À!}!t}
%}"}&} }*} }
}#}$À#}%}&}0lVÜ}'}"}(}"}1}$}%ô}3})}!isdnx2Ó}7~~ÿ}#À!}!u} %}"}&}
}*} } }#}$À#}%}&}0lVÜ}'}"}(}"}1}$}%ô}3})}!isdnx2œ»~~ÿ}#À!}!v}
%}"}&} }*} } }#}$À#}%}&}0lVÜ}'}"}(}"}1}$}%ô}3})}!isdnx2\G~
Here is the modem log (below), the three instances with ====
underlining concern me, why should an abort be initiated when there is
no apparent cause for this? Why so much activity after the abort? Is it
possible that all of the above gumf is actually generated on my side
and has not come from the ISP ?
C:\WINDOWS\ModemLog_Smart Link 56K Voice Modem.txt
22:07:25.046 - File: C:\WINDOWS\system32\tapisrv.dll, Version 5.1.2600
22:07:25.046 - File: C:\WINDOWS\system32\unimdm.tsp, Version 5.1.2600
22:07:25.046 - File: C:\WINDOWS\system32\unimdmat.dll, Version 5.1.2600
22:07:25.046 - File: C:\WINDOWS\system32\uniplat.dll, Version 5.1.2600
22:07:25.046 - File: C:\WINDOWS\system32\drivers\modem.sys, Version
5.1.2600
22:07:25.046 - File: C:\WINDOWS\system32\modemui.dll, Version 5.1.2600
22:07:25.046 - File: C:\WINDOWS\system32\mdminst.dll, Version 5.1.2600
22:07:25.046 - Modem type: Smart Link 56K Voice Modem
22:07:25.046 - Modem inf path: mdmhamrw.inf
22:07:25.046 - Modem inf section: Modem1
22:07:25.046 - Matching hardware ID:
pci\ven_2000&dev_2800&subsys_2800163c
22:07:25.125 - 460800,8,N,1, ctsfl=1, rtsctl=2
22:07:25.125 - Initializing modem.
22:07:25.140 - Send: AT<cr>
22:07:25.140 - Recv: <cr><lf>OK<cr><lf>
22:07:25.140 - Interpreted response: OK
22:07:25.156 - Send: AT &F E0 V1 &A3 &D2 &C1 S0=0<cr>
22:07:25.156 - Recv: <cr><lf>OK<cr><lf>
22:07:25.156 - Interpreted response: OK
22:07:25.171 - Send: ATS7=60S19=0L1M1\N3%C3&H1N1X4<cr>
22:07:25.171 - Recv: <cr><lf>OK<cr><lf>
22:07:25.171 - Interpreted response: OK
22:07:25.171 - Waiting for a call.
22:07:25.187 - Send: at#cid=1<cr>
22:07:25.187 - Recv: <cr><lf>OK<cr><lf>
22:07:25.187 - Interpreted response: OK
22:07:25.203 - Send: ATS0=0<cr>
22:07:25.203 - Recv: <cr><lf>OK<cr><lf>
22:07:25.203 - Interpreted response: OK
22:07:25.203 - 115200,8,N,1, ctsfl=1, rtsctl=2
22:07:25.203 - Initializing modem.
22:07:25.218 - Send: AT<cr>
22:07:25.218 - Recv: <cr><lf>OK<cr><lf>
22:07:25.218 - Interpreted response: OK
22:07:25.234 - Send: AT &F E0 V1 &A3 &D2 &C1 S0=0<cr>
22:07:25.234 - Recv: <cr><lf>OK<cr><lf>
22:07:25.234 - Interpreted response: OK
22:07:25.250 - Send: ATS7=60S19=0L1M1\N3%C3&H1N1X4<cr>
22:07:25.250 - Recv: <cr><lf>OK<cr><lf>
22:07:25.250 - Interpreted response: OK
22:07:25.250 - Dialing.
22:07:25.265 - Send: ATDT*###,,,,,,####,,,,,,#,,,,,,#<cr>
22:07:29.750 - Attempting to abort current command
==================================================
22:07:29.750 - Send: <cr>
22:07:30.062 - Recv: <cr><lf>NO CARRIER<cr><lf>
22:07:30.062 - Interpreted response: No Carrier
==================================================
22:07:30.062 - Hanging up the modem.
==================================================
22:07:30.078 - Send: ATH<cr>
22:07:30.093 - Recv: <cr><lf>OK<cr><lf>
22:07:30.093 - Interpreted response: OK
22:07:30.093 - 460800,8,N,1, ctsfl=1, rtsctl=2
22:07:30.093 - Initializing modem.
22:07:30.109 - Send: AT<cr>
22:07:30.109 - Recv: <cr><lf>OK<cr><lf>
22:07:30.109 - Interpreted response: OK
22:07:30.125 - Send: AT &F E0 V1 &A3 &D2 &C1 S0=0<cr>
22:07:30.125 - Recv: <cr><lf>OK<cr><lf>
22:07:30.125 - Interpreted response: OK
22:07:30.140 - Send: ATS7=60S19=0L1M1\N3%C3&H1N1X4<cr>
22:07:30.140 - Recv: <cr><lf>OK<cr><lf>
22:07:30.140 - Interpreted response: OK
22:07:30.140 - Waiting for a call.
22:07:30.156 - Send: at#cid=1<cr>
22:07:30.156 - Recv: <cr><lf>OK<cr><lf>
22:07:30.156 - Interpreted response: OK
22:07:30.171 - Send: ATS0=0<cr>
22:07:30.171 - Recv: <cr><lf>OK<cr><lf>
22:07:30.171 - Interpreted response: OK
22:07:30.171 - Session Statistics:
22:07:30.171 - Reads : 30 bytes
22:07:30.171 - Writes: 78 bytes
