smb & win9x
Jim at Morris.net
Mon Mar 12 21:35:50 GMT 2001
Monday, March 12, 2001, 9:07:16 AM, you wrote:
os level >> 33 is not needed for any Windows systems. So,
RS> os level = 33
RS> is enough. If there is another samba server with an os level > 32, then you
RS> might not want to fight with it.
I don't know what is going on here, as I am in agreement with you
that the "os level" setting should not normally need to be higher than
33 (I sometimes use 65 though). Regardless, Bartlomiej is apparently
onto something, as my problems using DHCP client PC's seems to
disappear if I use "os level = 128" in my smb.conf (Samba 2.0.7 here).
My local LAN at the moment only has one Samba 2.0.7 server (running on
Mandrake 7.1) and two Windows 98 client PC's. I am not sure whether
this logon issue happens with NT4 clients or not, as I don't often try
to log my NT4 systems into the Samba controlled domain. Most of my
NT4 and Win2000 setups are actually VMWare machines that I use for
testing, and as I often carry them around to different LAN's on a
laptop, I don't have them joined to the domain. Maybe I'll work some
more on this issue though....
I also see this on one LAN that is running Samba 2.0.7 on Redhat 6.0 -
while another Redhat 6.0 Samba server never seems to have this issue.
A pretty large installation with Samba 2.0.5a on Redhat 5.2 also never
has this issue - and it has close to 100 DHCP-allocated Windows client
Again, this ONLY seems to happen when you let the Win98 client get its
WINS server settings via DHCP.... If you manually set the WINS server
address, it doesn't happen. Wierd!
Jim Morris mailto:Jim at Morris.net
More information about the samba-ntdom