Now we are having this problem:
Win95 dial-up getting 'Could not negotiate a compatible set of network
protocols...' this is dialing into a PM2e (ver 3.3.2c1) and does not happen
all the time. Seems to only happen after multiple successful dial-ins and
disconnects.
No other protocols are selected for the Dial-up adapter other than TCP.
There is however a network adapter in the machine that I have used to
reproduce the problem.
Having the terminal window come up after dialing and entering login and pwd
seems to have no effect.
Any help on this would be greatly appreciated. It's funny I just read
someone asking if they should go to NT's RAS as a valid dial-in solution
and Livingston came back and said how wonderful the PM's were. Well we are
switching from RAS and we never had this problem with it. I'm sure it can
be fixed, it's just frustrating to have to go through this!
Here is the debug info from the PM:
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
Sending LCP_CONFIGURE_REJECT to port S7 of 7 bytes containing:
04 01 00 07 0d 03 06
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
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
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
S7: LCP Open
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
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
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