From owner-freebsd-bugs Wed Jan 17 20:36:14 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA09716 for bugs-outgoing; Wed, 17 Jan 1996 20:36:14 -0800 (PST) Received: from underdog.maxie.com (maxie.com [199.250.231.28]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA09621 for ; Wed, 17 Jan 1996 20:36:06 -0800 (PST) Received: (from max@localhost) by underdog.maxie.com (8.6.12/8.6.12) id XAA19106; Wed, 17 Jan 1996 23:34:58 -0500 Date: Wed, 17 Jan 1996 23:34:57 -0500 (EST) From: James Robertson To: Asif Bakar cc: bugs@freebsd.org Subject: Re: Windows95 connection In-Reply-To: <199601180340.VAA06651@emu.arinet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@freebsd.org Precedence: bulk On Wed, 17 Jan 1996, Asif Bakar wrote: > I am not sure if it is Windows 95 problem or FreeBSD > problem. But here it is! > > I use Free BSD to allow users to connect to my machine. > I dont have any problems with any of the users connecting > to my machine using any windows TCP/IP software. but > all my customers with WINDOWS95 are having problems. > do you have any suggestions in terms of setting up some > flag or option somewhere which will allow me to let > the window95 users get into my server. Windows95 has a known problem talking to BSDI, since FreeBSD is similar it might be the same. At any rate, the same fix lets Win95 users dial into the FreeBSD server here. Disable VJ compression in Win95 and it should successfully connect, if you don't you'll get a message something like "No compatible protocol"..I don't remember exactly now, it's been a while since I messed with Win95, the 95 test machine here is now a FreeBSD one. :-) If that doesn't do it, let me know, I have some notes around here somewhere on getting it to work. It's Win95 with the bug, not BSD, by the way... James Robertson