I've tried to annotate the (portion?) of the log you sent
based on my (limited?) understanding of what is happing.
Is this the full transcript?
It looks as if at least some LCP stuff is missing (but probably not =
important).
Is the client using a login script instead of PAP?
Did you just choose not to broadcast the users name & password?
It looks like the PAP exchange is missing (but probably not important).
=46inally, it seems that the client (Win95) seems to just give up when
the PM rejects it's request for NBNSs and SecDNS. It usually
just sends another IPCP Request leaving them out.
Could there have been more output that didn't make it
into your posting?
Puzzled,
Bill
=20
>Received LCP_CONFIGURE_REQUEST on port S7 of 19 bytes containing:
>01 01 00 17 02 06 00 0a 00 00 05 06 0f f5 e9 ca
>07 02 08 02 0d 03 06
=46ixed #bytes to match #found...
Recvd from port S7: 25 bytes LCP Request-1=20
Async-Control-Char-Map =3D 0x000a0000
Magic-Number =3D 0x0ff5e9ca
Protocol-Field-Comp
Addr-and-Ctl-Field-Comp
Callback =3D 0x06=20
Win95 asks PM to talk to it using these LCP opts.
>Sending LCP_CONFIGURE_REJECT to port S7 of 7 bytes containing:
>04 01 00 07 0d 03 06
Sent to port S7: 9 bytes LCP Reject-1=20
Callback =3D 0x06=20
PM says: I won't do callback.
>Sending LCP_CONFIGURE_ACK to port S7 of 20 bytes containing:
>02 02 00 14 02 06 00 0a 00 00 05 06 0f f5 e9 ca
>07 02 08 02
Sent to port S7: 22 bytes LCP Accept-2=20
Async-Control-Char-Map =3D 0x000a0000
Magic-Number =3D 0x0ff5e9ca
Protocol-Field-Comp
Addr-and-Ctl-Field-Comp=20
PM says: These opts are ok.
Usually this comes in response to another conf req from Win95.
Notice this a reply to req #2. Where is req #2?
>Sending LCP_CONFIGURE_REQUEST to port S7 of 20 bytes containing:
>01 04 00 14 02 06 00 00 00 00 05 06 f6 35 92 68
>07 02 08 02
Sent to port S7: 22 bytes LCP Request-4=20
Async-Control-Char-Map =3D 0x00000000
Magic-Number =3D 0xf6359268
Protocol-Field-Comp
Addr-and-Ctl-Field-Comp=20
PM asks Win95 to talk to it using these LCP opts.
>Received LCP_CONFIGURE_ACK on port S7 of 16 bytes containing:
>02 04 00 14 02 06 00 00 00 00 05 06 f6 35 92 68
>07 02 08 02
=46ixed #bytes to match #found...
Recvd from port S7: 22 bytes LCP Accept-4=20
Async-Control-Char-Map =3D 0x00000000
Magic-Number =3D 0xf6359268
Protocol-Field-Comp
Addr-and-Ctl-Field-Comp=20
Win95 says: OK
>Skipping: S7: LCP Open
The firmware on the PM recognizes that the LCP negotiation
has converged.
Normally PAP takes place now.
Is this client set up to use some login script instead of PAP?
>Sending IPCP_CONFIGURE_REQUEST to port S7 of 16 bytes containing:
>01 01 00 10 02 06 00 2d 0f 00 03 06 ce 64 54 07
Sent to port S7: 18 bytes IPCP Request-1=20
IP Comp Proto =3D Van Jacobson 15 0
IP Address =3D 206.100.84.7=20
PM says: Please use VJC and *my* IP addr is 206...7 (if you care).
>Received IPCP_CONFIGURE_REQUEST on port S7 of 36 bytes containing:
>01 01 00 28 02 06 00 2d 0f 01 03 06 00 00 00 00
>81 06 00 00 00 00 82 06 00 00 00 00 83 06 00 00
>00 00 84 06 00 00 00 00
=46ixed #bytes to match #found...
Recvd from port S7: 42 bytes IPCP Request-1=20
IP Comp Proto =3D Van Jacobson 15 1
IP Address =3D 0.0.0.0
Pri DNS =3D 0.0.0.0
Pri Netbios NS =3D 0.0.0.0
Sec DNS =3D 0.0.0.0
Secy Netbios NS =3D 0.0.0.0=20
Win95 says: Please use VJC and tell me addresses for these
other 5 things. Win95 seems to ask for the Netbio NSs even
if WINS is disabled; although puzzling, it is normal.
>Sending IPCP_CONFIGURE_REJECT to port S7 of 22 bytes containing:
>04 01 00 16 82 06 00 00 00 00 83 06 00 00 00 00
>84 06 00 00 00 00
Sent to port S7: 24 bytes IPCP Reject-1=20
Pri Netbios NS =3D 0.0.0.0
Sec DNS =3D 0.0.0.0
Secy Netbios NS =3D 0.0.0.0=20
PM says: I can't tell you the addresses for these.
At this point Win95 normally responds with another IPCP Req
containing only VJC, IP adr, and Pri DNS addr.
Don't know why it wouldn't.