Samba PDC Version 3.6.12-162.1-2943-SUSE-SL12.1-x86_64. Changed clients (3 notebooks, 2 desktops) from WinXP Pro to Win7 Pro (2 notebooks) and Win8 Pro (1 notebook, 2 desktops). domain logon: working executing logon script: working manual connection of PDC shares: working automatic connection of PDC shares by logon script: working roaming profiles: working browsing network: FAIL None of the clients sees the PDC in network though the clients see each other. Same with a LG NAS running with samba v3.2.7. Samba client tools work as expected. So I guess this is a problem in client-server communication. Strange is that the clients could see the PDC as well as the NAS after having joined the domain. Later on PDC and NAS did not appear any longer. I followed the samba.org guide concerning the registry tweaks and switched off PW change after 30 days in registry. I checked one notebook in another samba network (v3.5.5) with local login. From there I can browse the complete network environment. I attached my smb.conf as well as a client logfile and a nmbd logfile.
Created attachment 8574 [details] smb.conf, client log, nmbd.log
Created attachment 8575 [details] winbind loglevel 10 Maybe this one helps finding the problem. Looks like winbind does not receive/find a domain name.
unreliable network browsing is something that samba can not really fix. The mechanism of network browsing is a matter of luck and never reliable, depends on whether or not you are in the same broadcast net and many other unpredictable things. I think there is not much we can do for you, this is most probably not a samba problem. Als winbind is not required for that as you are running security=user. The important things that need to work are working as you mentioned.
Does that mean even if the PDC can browse the network (smbtree -N works and shows all available computers and nas) it has not to work the other way round? The only machine that cannot be found by the clients is the PDC. The clients see each other. If it was a general browsing problem they could not see each other, right? Even my TV, WLAN Router and some other devices appear in "network". As all computers reside in the same subnet there is no obvious reason why the PDC should not be seen being the master browser for the domain. There are some error messages appearing in the client logs regularyly: smbd_smb2_request_incoming: client read error NT_STATUS_CONNECTION_RESET Can this message be regarding as information only? I also wonder why executing "nbtstat" on client works except for "nbtstat -[s|S|R|RR]". The latter result in an error message. nbtstat -[s|S]: no connections nbtstat -R: NBT-Remotecachetabelle konnte nicht gelöscht werden (NBT remote cache table could not be deleted) nbtstat -RR: Freigeben und erneuern registrierter Namen ist fehlgeschlagen. Der Zugriff wurde verweigert (Release and renew of registered names failed. Access denied) The output of the first two commands show the IP of PDC as node address. I still think this is some kind of authentication problem.
Something I forgot to mention: The NAS does not appear in "network" either. Logging on to the client computer as local user makes the NAS appear. As the NAS runs an older samba version it seems to be some kind of bug in 3.6.x.
>The NAS does not appear in "network" either. Logging on to the client computer >as local user makes the NAS appear. as mentioned, unreliable, dependening on many unpredictable things. Please do not reopen this bug, it's not a samba bug. You may want to exchange experiences on the mailing list or search in the archive for people having discussed browsing in the past.