[wpkg-users] WPKG cannot reach Samba at boot-up (was Re: Where is WPKG client config stored?)

[Tomasz Chmielewski]

> My Samba logging is using 'auth:10' so I see lots of detail relating to
> share access.

It's way too great.
Reduce it to 3, unless you're debugging detailed protocol issues.


> My Samba setup logs to /var/log/samba/clientlog/%m.log -
> where %m is the NetBIOS name of the PC.  So, for machine called pc00123,
> it logs to /var/log/samba/clientlog/pc00123.log and so on.
> Interestingly, for the 'problem' PCs, logging info is logged initially
> to /var/log/samba/clientlog/<IP-address-of-pc00123>.log and then, a few
> seconds later, logging has switched to
> /var/log/samba/clientlog/pc00123.log again.

It is perfectly normal for every new connection to Samba.


> Does this mean that there is a NetBIOS name resolution problem here
> somewhere? 

No.


> Thus causing logging to go to <IP-address-of-pc00123>.log
> initially? 

No.


> If, at the stage WPKG runs during system boot-up it is
> unable to resolve/find the Samba server by name, that would explain why
> WPKG cannot run properly.
> 
> If so, why does it only affect some PCs on the network?  The server is
> running smbd and nmbd in a fairly typical Samba setup and all PCs are
> sysprepped from the same WinXP image.

Again, it's perfectly normal that a new connection appears as <IP>.log, 
and a while later as <machinename>.log.


-- 
Tomasz Chmielewski
http://wpkg.org


wpkg-users mailing list
wpkg-users at lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users