[Samba] Re: Client login delays - especially after reboot

[Nigel Home]

Hi

>Have you posted any of your findings and/or configs? If not, start
>there. If you have, please reference them in another post.
my original post of the problem

http://lists.samba.org/archive/samba/2006-March/119173.html

>What exactly have you done to troubleshoot this so far?
>e.g.:
>* have you reproduced the problem consistently?
yes. the problem is ongoing since the new server was installed. (previously no delays)

>* do any hosts NOT have problems? What is different between them?
all hosts affected

>* have you sniffed the wire and looked at the traffic?
No..can't get ethreal working so far and not sure what i'd be looking for.

>* have you set debug level looked in the logs for any clues?
I've now upped the log level to 4 and found somthing strange with wins. see log below.

>* have you ruled out name resolution issues? (WINS and/or dns)
name resolution works, don't have problems with nmblookup or smbclient queries but not sure about wins, see log below.

master:~ # nmblookup -B cad2 '*'
added interface ip=192.168.0.1 bcast=192.168.0.255 nmask=255.255.255.0
not adding duplicate interface 192.168.0.1
Socket opened.
querying * on 192.168.0.3
nmb packet from 192.168.0.3(137) header: id=19215 opcode=Query(0) response=Yes
    header: flags: bcast=No rec_avail=No rec_des=Yes trunc=No auth=Yes
    header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0
    answers: nmb_name=*<00> rr_type=32 rr_class=1 ttl=300000
    answers   0 char ......   hex 8000C0A80003
Got a positive name query response from 192.168.0.3 ( 192.168.0.3 )
192.168.0.3 *<00>


master:~ # smbclient //master/TMP
added interface ip=192.168.0.1 bcast=192.168.0.255 nmask=255.255.255.0
not adding duplicate interface 192.168.0.1
Client started (version 3.0.12-5-SUSE).
resolve_wins: Attempting wins lookup for name master<0x20>
wins_srv_is_dead: 192.168.0.1 is alive
wins_srv_is_dead: 192.168.0.1 is alive
resolve_wins: using WINS server 192.168.0.1 and tag '*'
wins_srv_is_dead: 192.168.0.1 is alive
Marking wins server 192.168.0.1 dead for 600 seconds from source 192.168.0.1
resolve_lmhosts: Attempting lmhosts lookup for name master<0x20>
getlmhostsent: lmhost entry: 127.0.0.1 localhost
getlmhostsent: lmhost entry: 192.168.0.1 master.xxxxx.com master
getlmhostsent: lmhost entry: 192.168.0.2 cad1.xxxxx.com cad1
getlmhostsent: lmhost entry: 192.168.0.3 cad2.xxxxx.com cad2
getlmhostsent: lmhost entry: 192.168.0.4 director.xxxxx.com director
getlmhostsent: lmhost entry: 192.168.0.7 accounts.xxxxx.com accounts
getlmhostsent: lmhost entry: 192.168.0.8 office.xxxxx.com office
resolve_hosts: Attempting host lookup for name master<0x20>
Connecting to 192.168.0.1 at port 445
 session request ok
Serverzone is 0

note! there is a short delay (5 sec) between wins query and resolution of lmhosts

If I repeat the query after a few seconds i get:-

added interface ip=192.168.0.1 bcast=192.168.0.255 nmask=255.255.255.0
not adding duplicate interface 192.168.0.1
Client started (version 3.0.12-5-SUSE).
Connecting to 192.168.0.1 at port 445
 session request ok
Serverzone is 0

If I wait 10mins I get the first one again.

does this mean wins is going to sleep or something? does Bind provide wins or something else?
where do I go from here?.

Regards

Nigel