From owner-freebsd-questions Sun Dec 29 13:04:00 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA12048 for questions-outgoing; Sun, 29 Dec 1996 13:04:00 -0800 (PST) Received: from value.net (root@value.net [204.188.125.4]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA12037 for ; Sun, 29 Dec 1996 13:03:58 -0800 (PST) Received: from value.net (nickliu@value.net [204.188.125.4]) by value.net (8.8.4/8.7.3) with SMTP id NAA03782 for ; Sun, 29 Dec 1996 13:03:56 -0800 (PST) Date: Sun, 29 Dec 1996 13:03:55 -0800 (PST) From: Nick Liu To: questions@freebsd.org Subject: Win95 to FreeBSD Direct Null Modem Connection Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dear hackers, I know this is strictly a Win95 issue, but I believe someone had already tried it and be willing to help. I was able to establish a null modem connection between a Win95 PC and my FreeBSD 2.1.5 server. All problems had been ironed out with these. But I still cannot make my Win95 machine connect to the Internet. I mean, the dial-up program just won't recognize Slirp (and it's not Slirp's problem). I tried everything possible. I even added a direct connection null modem device using an .inf file from Well's site (http://www.vt.edu:10021/K/kewells/net/index.html). When I commanded the DUN tools to connect, I saw the login screen, I entered the user name and password and everything (including slirp), but the damn DUN scrren stayed as if the connection was not established. It could be an adventure but I just ran out my patience. Can anyone help? Please cc me.