On Tue, 2 Jun 1998, John Nowack wrote:
> Sending LCP_CONFIGURE_REJECT to port S3 of 7 bytes containing:
> 04 02 00 07 0d 03 06
> Sent to port S3: 9 bytes LCP Reject-2
> Callback = 0x06
a reject is not necessarily bad, what is that Callback thing? Does that
mean the user is calling back trying to get the same ip #? > > Received
LCP_CONFIGURE_REQUEST on port S3 of 16 bytes containing: > 01 03 00 14 02
06 00 0a 00 00 05 06 00 01 ec c3 > 07 02 08 02 > Fixed #bytes to match
#found... > Recvd from port S3: 22 bytes LCP Request-3 >
Async-Control-Char-Map = 0x000a0000 > Magic-Number = 0x0001ecc3 >
Protocol-Field-Comp > Addr-and-Ctl-Field-Comp
Is that async map supposed to be 000a0000? (sorry, i accidentally
justified that)
> Sending LCP_CONFIGURE_ACK to port S3 of 20 bytes containing:
> 02 03 00 14 02 06 00 0a 00 00 05 06 00 01 ec c3
> 07 02 08 02
> Sent to port S3: 22 bytes LCP Accept-3
> Async-Control-Char-Map = 0x000a0000
> Magic-Number = 0x0001ecc3
> Protocol-Field-Comp
> Addr-and-Ctl-Field-Comp
> Skipping: S3: LCP Open
It acknowledged that async map (whether its right or not I dont think
matters to the connection, unless that map is causing some data to be
filtered wrong.
> Received PAP_AUTH_REQ on port S3 of 22 bytes containing:
> Fixed #bytes to match #found...
> Recvd from port S3: 2 bytes PAP <badlen=0,4> unknown<0x0>
> Skipping: xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx
> Skipping: xx xx xx xx xx xx
This is the authentication request
> Sending PAP_AUTH_ACK to port S3 of 20 bytes containing:
> 02 01 00 14 0f 4c 6f 67 69 6e 20 53 75 63 63 65
> 65 64 65 64
> Sent to port S3: 22 bytes PAP Accept-1
> <Login Succeeded>
Oh hi, its you...
> Sending IPCP_CONFIGURE_REQUEST to port S3 of 16 bytes containing:
> 01 01 00 10 02 06 00 2d 0f 00 03 06 cd f2 5a 64
> Sent to port S3: 18 bytes IPCP Request-1
> IP Comp Proto = Van Jacobson 15 0
> IP Address = 205.242.90.100
Server is saying, okay here is MY ip address and Im using vj comp to
send you this info.
> Skipping:
>
> Received IPCP_CONFIGURE_REQUEST on port S3 of 36 bytes containing:
> 01 01 00 28 02 06 00 2d 0f 01 03 06 00 00 00 00
> 81 06 cd f2 5a 02 82 06 00 00 00 00 83 06 00 00
> 00 00 84 06 00 00 00 00
> Fixed #bytes to match #found...
> Recvd from port S3: 42 bytes IPCP Request-1
> IP Comp Proto = Van Jacobson 15 1
> IP Address = 0.0.0.0
> Pri DNS = 205.242.90.2
> Pri Netbios NS = 0.0.0.0
> Sec DNS = 0.0.0.0
> Secy Netbios NS = 0.0.0.0
remote guy is saying okay I WANT an address, cuz i dont have one(0.0.0.0),
prim and 2ndary nb ns's , and I have prim dns but need secy dns. BTW, do
YOU offer netbios NS data? It seems he has some netbios stuff turned on
for this connection.
> Sending IPCP_CONFIGURE_REJECT to port S3 of 10 bytes containing:
> 04 01 00 0a 84 06 00 00 00 00
> Sent to port S3: 12 bytes IPCP Reject-1
> Secy Netbios NS = 0.0.0.0
Host is saying no to secy netbios ns, i dont have that info
> Sending LCP_PROTOCOL_REJECT to port S3 of 21 bytes containing:
> 08 02 00 15 80 fd 01 01 00 0f 12 06 00 00 00 01
> 11 05 00 01 04
> Sent to port S3: 23 bytes LCP Protocol-Reject-2 CCP 80 fd 01 01 00 0f
host rejecting a protocol. What protocol?
> Received IPCP_CONFIGURE_ACK on port S3 of 12 bytes containing:
> 02 01 00 10 02 06 00 2d 0f 00 03 06 cd f2 5a 64
> Fixed #bytes to match #found...
> Recvd from port S3: 18 bytes IPCP Accept-1
> IP Comp Proto = Van Jacobson 15 0
> IP Address = 205.242.90.100
remote says, Oh okay I see you at 100.
> Skipping:
>
> Received IPCP_CONFIGURE_REQUEST on port S3 of 30 bytes containing:
> 01 02 00 22 02 06 00 2d 0f 01 03 06 00 00 00 00
> 81 06 cd f2 5a 02 82 06 00 00 00 00 83 06 00 00
> 00 00
> Fixed #bytes to match #found...
> Recvd from port S3: 36 bytes IPCP Request-2
> IP Comp Proto = Van Jacobson 15 1
> IP Address = 0.0.0.0
> Pri DNS = 205.242.90.2
> Pri Netbios NS = 0.0.0.0
> Sec DNS = 0.0.0.0
remote says, I STILL need an address? and more nbns info...
>
> Sending IPCP_CONFIGURE_NAK to port S3 of 16 bytes containing:
> 03 02 00 10 82 06 00 00 00 00 83 06 cd f3 ad 44
> Sent to port S3: 18 bytes IPCP Refuse-2
> Pri Netbios NS = 0.0.0.0
> Sec DNS = 205.243.173.68
Host again says, no to that request. But here is your Sec DNS info...
> Skipping:
>
> Received IPCP_CONFIGURE_REQUEST on port S3 of 30 bytes containing:
> 01 03 00 22 02 06 00 2d 0f 01 03 06 00 00 00 00
> 81 06 cd f2 5a 02 82 06 00 00 00 00 83 06 cd f3
> ad 44
> Fixed #bytes to match #found...
> Recvd from port S3: 36 bytes IPCP Request-3
> IP Comp Proto = Van Jacobson 15 1
> IP Address = 0.0.0.0
> Pri DNS = 205.242.90.2
> Pri Netbios NS = 0.0.0.0
> Sec DNS = 205.243.173.68
remote says I STILL NEED an address, and netbios stuff, thans for the dns
info.
>
> Sending IPCP_CONFIGURE_REJECT to port S3 of 10 bytes containing:
> 04 03 00 0a 82 06 00 00 00 00
> Sent to port S3: 12 bytes IPCP Reject-3
> Pri Netbios NS = 0.0.0.0
Host says NO to this pri Netbios NS. (why is the remote asking for this?
Do they have some netbios stuff checked on the remote end?)
> Received IPCP_CONFIGURE_REQUEST on port S3 of 24 bytes containing:
> 01 04 00 1c 02 06 00 2d 0f 01 03 06 00 00 00 00
> 81 06 cd f2 5a 02 83 06 cd f3 ad 44
> Fixed #bytes to match #found...
> Recvd from port S3: 30 bytes IPCP Request-4
> IP Comp Proto = Van Jacobson 15 1
> IP Address = 0.0.0.0
> Pri DNS = 205.242.90.2
> Sec DNS = 205.243.173.68
Remote says, LOOK MAN! This is the 4th time ive asked for an address. This
is becuase it was asking for that netbios ns stuff before and getting
turned down so its gonna stop asking...
>
> Sending IPCP_CONFIGURE_NAK to port S3 of 10 bytes containing:
> 03 04 00 0a 03 06 cd f2 5a 70
> Sent to port S3: 12 bytes IPCP Refuse-4
> IP Address = 205.242.90.112
Host says NO, Here is an addres for you, 112
> Received IPCP_CONFIGURE_REQUEST on port S3 of 24 bytes containing:
> 01 05 00 1c 02 06 00 2d 0f 01 03 06 cd f2 5a 70
> 81 06 cd f2 5a 02 83 06 cd f3 ad 44
> Fixed #bytes to match #found...
> Recvd from port S3: 30 bytes IPCP Request-5
> IP Comp Proto = Van Jacobson 15 1
> IP Address = 205.242.90.112
> Pri DNS = 205.242.90.2
> Sec DNS = 205.243.173.68
>
Remote asks, can I have this info? is it right?
> Sending IPCP_CONFIGURE_ACK to port S3 of 28 bytes containing:
> 02 05 00 1c 02 06 00 2d 0f 01 03 06 cd f2 5a 70
> 81 06 cd f2 5a 02 83 06 cd f3 ad 44
> Sent to port S3: 30 bytes IPCP Accept-5
> IP Comp Proto = Van Jacobson 15 1
> IP Address = 205.242.90.112
> Pri DNS = 205.242.90.2
> Sec DNS = 205.243.173.68
Host says, yes, here we are on the same page now!!!
> Skipping: S3: IPCP Open
> Skipping: LCP IPCP Open
> Skipping: Connection Succeeded
>
> At that point sho mx shows the modem "Active", and show sx shows the status
> "Connecting." No more packets are sent, but the line will stay up until
> the user drops it from his end (I had him sit for minutes like this).
It seems that something with netbios NS is making the lcp negotiation go
not so smoothly. Or maybe that async map thing...I just watched a couple,
and I didnt see any netbios ns stuff, but I did get:
S3: IPCP Open
LCP IPCP Open
Connection Succeeded
Just like you had My s3 has ESTABLISHED. So I assumed that when you got
Connection Succeeded, that it should say ESTABLISHED, and all negotiation
is done at this point, so I dont know why the pm 3 is still saying
CONNECTING. Are you SURE the port in questions still says CONNECTING?
Have you compared THIS debug output to others when they call in?
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
Jake Messinger ph:713-772-6690 Lucent Dealer
AMS, Inc. fx:713-774-3498 Medical Billing
8300 Bissonnet #400 jake@ams.com Internet Services
Houston, Texas 77074 www.ams.com/~jake Business Management
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>