"Cannot Negotiate" Answer #1!!

Donn F. Lasher (dlasher@owt.com)
Thu, 05 Dec 1996 15:55:09 -0800

I've been following this thread, and we've been experiencing this quite a
bit here as well. (We have 4 - 2E's and 120 SupraFax 33.6). Just wanted to
share a couple things we've discovered with all of you, and you might be
able to find "The Answer" for you.

#1 - "Instant Login" - Windows 95 Uses PAP. I know some of you knew this,
but this came as a suprise to me. It appears that in some cases, Windows 95
will attempt a "configure request" AS-SOON-AS the CD is detected. In most
modems cases, it takes about 1 sec before data starts moving. Therefore
win95 appears to "jump the gun", the data never makes it to the PM, and
win95 time-outs. You can solve this by installing scripting for windows 95.
Use the ISDN accel pack (dun 2.0) for ease of use, and just write a simple
script to go with it. This forces 95 to wait for the login/password. I'll
include our sample script on the end of this message. (BTW, You can have
the client turn on extended logging by going to: Control Panels: Network:
Dial-UP Adapter: Properties: Advanced: Record a Log File: and set it to
YES. This can show a lot about WHY a connection fails.)

#2 - Port Death - It appears that on certain occaisions, a modem may
hang-up/reset (&d3) and lose sync with the portmaster. The modem is still
working, so it will answer the phone. However, with lost/no sync with the
Portmaster, all the end user will get is either garbage or nothing. The
only way to correct this problem seems to be to reset the port. If anyone
has a fix for this one I'd LOOOOVE to know about it, since it's one of the
things we can't directly solve!!

#3 - IPX - Since a good percentage of new windows 95 users have never used
a computer much, there's a lot of misconfiguration. Debugs show that, on
some machines, when you have a loaded protocol request (NetBEUI, IPX,
TCP/IP) and the PM refuses first #1, then #2, by the time it gets around to
accepting #3, Win95 has timed out. Check to ensure TCP/IP is the only
protocol enabled/installed. (Where applicable)

Anyway, these are the things we've done to combat this problem, and other
than #2, we've managed to at least cut down on the volume.

Hope this helps!

Donn

--------------------------------------------------------------
- Donn Lasher - dlasher@oneworld.owt.com - (509) 735-0408 -
- Tech Support - One World Telecommuncations - Tricities, WA -
- Tri-Cities Oldest, Fastest, Most Reliable Internet Provider-
--------------------------------------------------------------