Re: PM3 and Win 3.1

Nick Johnson (nick@gulf.net)
Wed, 2 Apr 1997 08:14:19 -0600 (CST)

We were able to correct this problem by upgrading the OS version to
3.5.1b8. It appears that there was either something amok in 3.5 on the
PM3 or with the installation of 3.5 on that particular PM3. At any rate,
the problem appears OS related, and not related to dial up procedure,
which has remained constant for at least a year or more.

---
Nick Johnson, writer of code, fixer of modems
Gulf Coast Internet Systems Engineering Team
Check the web: http://www.gulf.net/support/network_status/

On Wed, 2 Apr 1997, Mark Essers wrote:

> > > On Tue, 1 Apr 1997, Nick Johnson wrote: > > > We are having considerable trouble getting Windows 3.1 users connected to > > our PM3 boxen. Users can connect, authenticate, and get an IP address > > assigned, but are then unable to connect to any remote sites. I have a > > hunch that this is a gateway assignment problem, but the Windows dialers > > that most of our users use (Netscape Personal Edition 3.0) don't provide > > much debugging information. > > > > Unix and Windows95 have no problems. > > > > Many of our customers are using WIN3.1. But they still use Trumpet > Winsock. > It's no problem to make a connection with it ! > > For the beginning, use the Terminal-Windows of e.g. Trumpet Winsock. You > can see the loggin-procedure. After that, you can easy change the > loggin-script. > > For easy loggin, you only have to login by Username/Password. After that, > the PPP is startet...(than you can start yout Netscape.....in The > Terminal-Windows of Winsock..you have to press "ESC" if you see the > "garbage" PPP-chars.) > > If you want to control something, you only look (by telnetting your PM3) > with "show sessions". If someone is loggin in, you can see something like > "IN CONECTION". If a User has logged in, you see "NETWORK ESTABLISHED". > > If the first message appears, and the connection gets lost, there a > mistake in the login-procedure. > > Mark Essers > >