search for: win95upd

Displaying 7 results from an estimated 7 matches for "win95upd".

1998 Nov 24
0
Dial in accounts (1883)
...even win95a (pre-OSR/2). You should probably apply all the currrent updates for OSR/2 networking stuff, and then apply the same reg tweaks (TCP/IP stuff - MaxMTU, RWIN, etc) to all the clients. Then you *may* get the same behavior... For update info, links, etc, see: http://www.walbeehm.com/win95upd.html The OSR/2 FAQ is at: http://www.compuclinic.com/osr2faq/ and some TCP/IP DUN tips can be found at: http://dspace.dial.pipex.com/mreeves/tips.htm There's a nice TCP/IP reg-tweaking tool at: http://www.mjs.u-net.com/ Hope this helps, Steve *******************************************...
1999 Jul 04
1
oplock_break: MS kb articles
I found these articles that talk about the oplock_break problem (specifically they are related to problems with word97): http://support.microsoft.com/support/ntserver/serviceware/nts40/e9msge2bc.asp http://support.microsoft.com/support/kb/articles/q163/5/25.asp Basically they say: either apply sp3 on the winnt client or disable oplock on nt server But they don't say anything about win9x,
1999 Sep 05
0
win 95b, win 95, encrypted passwords
...anything about that? Thanks. I'd suggest updating both machines with the M$ system updates, especially the win95 original version (which will become win95a after you apply the first update). There are updates for networking components, security holes, etc. See: http://www.walbeehm.com/win95upd.html Also, what is your win95 NetBIOS naming convention? Are you using the username map file? What is your samba guest account set to? Did you create the smbpasswd file, and are there valid M$ passwords in it? You should read the browsing.txt, encryption.txt and domain.txt (and others) and...
1999 May 30
1
oplock_break failed
Hi, I am running Samba 2.0.3 on Linux Kernel 2.2.5 (SuSE 6.1) in a test environment with a Win NT server (PDC), the Linux box taking over step by step the file- and printserver tasks, and Win 95 clients. Samba is setup with security=domain at this stage. It just happened again what I have seen only a few times before. When I use Outlook 98 on the Win95 machine and want to access the
2000 Jun 09
1
SAMBA digest 2551
...bly most of the others too). I've found that win95 (up to and including OSR/2.5) works quite a bit better (almost tolerable) with the system updates. At least two of them fix vredir problems, and many TCP stack problems too. Go here to read and get the ones you need: http://www.walbeehm.com/win95upd.html **************************************************************** Stephen L. Arnold with Std.Disclaimer; use Std.Disclaimer; ****************************************************************
1999 Aug 24
2
What to do in Windows 95 after configuring Samba
Hello, I'm new to Samba so sorry for this trivial question. I've configured my smb.conf with all the shares and enabled WINS support. I wanted to know what do I have to configure in my windows 95 machine. My LAN setup is - one Linux Red Hat 6.0 machine Pentium 166 and a windows 95 machine a 486. I've made my Linux m/c the proxy server using Squid. Also whenever I boot my Win m/c it
1999 Jun 25
3
security = server & encrypted passwords
Folks, I've missed the latest encrypted passwords thread, so forgive me if this is old hat for some of you. I'm running 2.0.3 with auth being handled by an NT PDC. It seems that some Win95 clients (namely those with later releases of the OS) have problems authenticating. I've got encrypt passwords = yes but it still seems only the old Win95 clients (clear text passwords) can auth