714snoopy wrote:From my experience, Nautilus uses the Samba service to do its sharing. I think when you share something via Nautilus, it writes a separate configuration file somewhere else and not necessarily in the system's samba.conf file. Can anyone confirm that?
My networking issues were resolved by changing out the brand of router I was using. For some reason, with my Linksys router (WRT54G), NetBios names do not seem to work. I have to use IP addresses to find any shares on other computers. I borrowed a Netgear VPN/Firewall router from my work and now I can just use computer names to find them on the network! I'll have to fiddle with the Linksys setting some more and see if I can get it to work. But for now, I'm good!
; name resolve order = lmhosts host wins bcast
name resolve order = bcast host lmhosts wins
Winbind provides three separate functions:
Authentication of user credentials (via PAM). This makes it possible to log onto a UNIX/Linux system using user and group accounts from a Windows NT4 (including a Samba domain) or an Active Directory domain.
Identity resolution (via NSS). This is the default when winbind is not used.
Winbind maintains a database called winbind_idmap.tdb in which it stores mappings between UNIX UIDs, GIDs, and NT SIDs. This mapping is used only for users and groups that do not have a local UID/GID. It stores the UID/GID allocated from the idmap uid/gid range that it has mapped to the NT SID. If idmap backend has been specified as ldap:ldap://hostname[:389], then instead of using a local mapping, Winbind will obtain this information from the LDAP database.
Users browsing this forum: Bing [Bot] and 5 guests