3 -10 56k modem cards
Channelized T1:
Command> sh line0
---------------------- line0 - T1 Inband DS0 ---------------
Status: UP Framing: D4 Encoding: AMI PCM: u-law
Signaling: Trunk E&M wink start
Receive Level: -7.5dB to -15dB
Alarms Violations
----------------------------- -----------------------------
Blue 0 Bipolar 0
Yellow 0 CRC Errors 0
Receive Carrier Loss 0 Multiframe Sync 0
Loss of Sync 0
Customers are having problems authenticating at times. I was at a customers
home tonight when it happened to me using Windows95 dialup networking. I
tried to login and it stopped at the verifying password and disconnected.
I tried again with Hyper terminal and got the following results
login: aaatatat
Password:
Invalid Login
login: !root
Password:
The first login time the aaatat appeared when I connected. The second time
I was able to log in.
I tried again a little later and got similiar result. Both the Hypeterminal
attempts are logged below in my syslog but the Windows95 Dialup Networking
attempts weren't logged.
messages:Jan 13 21:16:40 garcia radius[22510]: auth: access-request from
ginsberg.ballcom.com (208.4.243.3) denied for unknown user aaatatat
messages:Jan 13 21:23:49 garcia radius[22616]: auth: access-request from
ginsberg.ballcom.com (208.4.243.3) denied for unknown user aatat
There are also several entries where the denied user is just a bunch of
garbage such as these couple:
Jan 13 16:25:46 garcia radius[20132]: auth: access-request from
ginsberg.ballcom.com (208.4.243.3) denied for unknown user @Xa]I.hby{u#"uL4z
Jan 13 16:25:46 garcia radius[20133]: auth: access-request from
ginsberg.ballcom.com (208.4.243.3) denied for unknown user |9wwd%%+V~]2 gj9
Ne('JueBAc2e@h`f>A(
Both calls that I connected using Hyperterminal were handled by m3
Command> sh m3
State: ACTIVE
Active Port: S3
Transmit Rate: 28800
Receive Rate: 31200
Connection Type: LAPM/V42BIS
Chars Sent: 135349431
Chars Received: 19363637
Retrains: 0
Renegotiations: 1
Total Calls: 138
Modem Detects: 126
Good Connects: 126
Connection Failures
No Modulation: 0
No Protocol: 0
Not Operational: 0
Total Failed: 0
Session Terminations
Lost Carrier: 0
Normal Disconnect: 125
Any Idea what could be causing this to happen? Is there anyway that the client can work around this problem?
Bill Ball
Ball Communications
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.