On Tue, Mar 09, 2010 at 10:45:39PM -0500, Chris Smith wrote: > Just upgraded a Samba PDC from 3.0.32 to 3.5.1. The good news - it is > running - the bad news - probably on life support. > > All seemed well until I started getting messages on some Windows > clients that the domain was not available - if your credentials were > not cached you could not log in - if they were everything seemed to > work. > > The test: > nmblookup -B BIGSERVER __SAMBA__ > > failed (yes, I replaced BIGSERVER with the proper PDC name) > > The test: > nmblookup -M testgroup > > also failed. > > But if your credentials were cached, you could login, the netlogon > scripts would run, the shared directories and printers were > available,etc. > > A restart makes everything right (the tests above will produce correct > info and the domain will be available) - for anywhere from a few > minutes to an hour or so but at some point samba will lose its head > and the domain will be unavailable. > > Assistance is greatly appreciated.
There were some changes that went into nmbd in 3.5.x to allow it to run correctly on a box with "bind interfaces only" set. Can you post your smb.conf ? Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
