Windows 98 + domain logons

Svein Roar Nilsen svein-roar.nilsen at statkart.no
Thu Nov 30 10:41:06 GMT 2000


[This message is a reply to 3 different other messages.]

> > When our PC's are configured via DHCP to use our caching
> > only DNS, will they start looking up machines on our
> > local network using DNS and forget everything about
> > WINS and broadcast?

> depends entirely on how you configure your PC's.  Are
> you assigning the IP address of your WINS server via DHCP
> as well?

Yes, all our PC's are configured using DHCP. We use a config file that closely
resembles that of DHCP-Server-Configuration.txt:

subnet 192.168.1.0 netmask 255.255.255.0 {
        range 192.168.1.10 192.168.1.200;
        default-lease-time 86400;
        max-lease-time 604800;
        option subnet-mask 255.255.255.0;
        option broadcast-address 192.168.1.255;
        option routers 192.168.1.2;
        option domain-name-servers 192.168.1.1, 195.70.161.40, 195.70.164.130;
        option domain-name "fjelltun";
        option ip-forwarding off;
        option netbios-name-servers 192.168.1.1;
        option netbios-dd-server 192.168.1.1;
        option netbios-node-type 8;
}

OK, the domain-name is not good as it is now, but that is because I have tried
different things here to see if it makes any difference. To be honest, it is not
all of those entries I know the meaning of. I have just used the suggestions
from the Samba documentation. 

> > became really anoying at about the same time as we
> > got our internet connection and the PC's were configured
> > to use a DNS...

> At that time, did you change /etc/resolv.conf on the
> Samba server?

Yes, I did. Before we got the internet connection, there were absolutely no DNS
server available. Now, it simply looks like this:

nameserver 192.168.1.1
nameserver 195.70.161.40
nameserver 195.70.164.130

>The name resolve order only has relavance when Samba is attempting
>to lookup a name for itself.

I know. What I tried to suggest, was that maybe Samba did a DNS lookup anyway,
even if it should not. If this happened only under very special circumstances,
one could get a bug like this? Earlier, I was administrator for a windows
network were we were using WINS but did not have our own DNS, and thus no
forward or reverse mappings. And there was never any problems logging on to our
NT domain from Win98 machines. (There were, however, lots of other problems. :)
So if many people have had the same problem and solved it by adding reverse
names, I think that should indicate a bug in Samba. 

>Are all of the Win98 clients using you Samba as 
>the WINS server?  You appear to only be using one subnet
>(from you hosts allow line).  Do you really think you 
>need WINS?  

No, I don't think I need it. But it should work anyway. And it also did for
nearly a year. But, if you think that dropping wins will solve our problems, I
have no problems trying. 

>The process logon packet opcode of 0x0 is confusing.  I don't
>see it in the namserv.h head file.

Most of the failed logins have 0x0. Some of them has 0x7. Is it Samba or Windows
98 that generates this number? 

>What version of Samba is this?  We you have problems.  
>What is the contents of wins.dat?

2.0.7. But the problem appeared earlier than that, and has been there, to
different degrees, over 2 or 3 Samba versions and at least 2 RedHat versions. 

wins.dat:

VERSION 1 159502
"__MSBROWSE__#01" 976090116 255.255.255.255 84R
"ADMINISTRATOR#03" 976086229 192.168.1.46 64R
"ANDRE#00" 976002042 255.255.255.255 84R
"ANNELISE#00" 976085151 192.168.1.45 64R
"ANNELISE#03" 976085153 192.168.1.45 64R
"ANNELISE#20" 976085155 192.168.1.45 64R
"ARBEIDSGRUPPE#00" 976086229 255.255.255.255 e4R
"ARBEIDSGRUPPE#1e" 976086229 255.255.255.255 e4R
"AVID#00" 976095125 192.168.1.14 64R
"AVID#03" 976095125 192.168.1.14 64R
"AVID#20" 976095125 192.168.1.14 64R
"BD#00" 976089423 192.168.1.17  4R
"BD#03" 976089423 192.168.1.17  4R
"BD#20" 976089423 192.168.1.17  4R
[...]
"ESTER#00" 976094526 192.168.1.1 46R
"ESTER#03" 976094526 192.168.1.1 46R
"ESTER#20" 976094526 192.168.1.1 46R
"FJELLTUN#00" 976094526 255.255.255.255 c4R
"FJELLTUN#1b" 976094526 192.168.1.1 44R
"FJELLTUN#1c" 976094526 192.168.1.1 c4R
"FJELLTUN#1e" 976094526 255.255.255.255 c4R
"GAT#00" 976028825 192.168.1.38  4R
"GAT#03" 976028825 192.168.1.38  4R
"HEIDI#00" 976088030 192.168.1.23  4R
"HEIDI#03" 976088028 192.168.1.23  4R
"HEIDI#20" 976088032 192.168.1.23  4R
"HK#03" 976088149 192.168.1.23  4R
"HKG#00" 976002042 192.168.1.33  4R
"HS#03" 976083274 192.168.1.32  4R
"IK#03" 976085465 192.168.1.26  4R
"INET~SERVICES#1c" 976085162 192.168.1.45 e4R
"INGE#00" 976085433 192.168.1.26  4R
"INGE#03" 976085431 192.168.1.26  4R
"INGE#20" 976085434 192.168.1.26  4R
"IS~ANNELISE#00" 976094872 192.168.1.45 64R
"JANOVE#03" 976088320 192.168.1.11  4R
[...]

(ESTER is our samba server. FJELLTUN is the workgroup and domain she belongs
to.)


Svein Roar Nilsen




More information about the samba mailing list