Hi all, I set up a Samba server (version 3.0.24) names "Lamp" on a Debian Etch distribution. It provides a "guest" (guest ok = yes, guest only = yes, security = SHARE) access to a "share" directory, which works fine. Indeed, I can access \\lamp\share from a Windows machine (named "Ginger") without issuing a password. I can also ping the Linux machine from the Windows one using "ping Lamp", and get the Windows machine IP from its NetBIOS name: # nmblookup Ginger querying Ginger on 192.168.1.255 192.168.1.22 Ginger<00> But I cannot ping (or, more generally, resolve the name of) the Windows machine from the Linux one: # ping Ginger ping: unknown host Ginger I hence followed the guidelines from those links: http://ubuntuforums.org/archive/index.php/t-182824.html http://www.linuxquestions.org/questions/linux-networking-3/linuxsamba-pdc-cant-resolve-windows-names-622797/ Which means I installed winbind and modified /etc/nsswitch.conf by adding "wins" to the "hosts" entry. As I understand it, winbind provides a bridge between nmbd and gethostbyname() by using the "Name Service Switch". Please note that I am not interested in the "active directory" part of winbind, nor in joining a domain, etc. Anyway, after I performed those modifications, "ping Ginger" actually worked. But then, \\lamp\share could not be accessed anymore (the error message was "The specified group does not exist"). Now, as soon as I remove the winbind package, I can access \\lamp\share again, but "ping Ginger" does not work anymore. I've been suggested on #samba to drop winbind and simply add "wins support = yes" to smb.conf; but then "ping Ginger" does not work any better. So, can I keep my simple "share" configuration, *and* integrate NetBIOS name resolution to my Linux system using Name Service Switch? FWIW, I posted my smb.conf here: http://pastebin.ca/1019614 <http://pastebin.ca/1019614> and nsswitch.conf here: http://pastebin.ca/1019612 <http://pastebin.ca/1019612>. Any hint would be greatly approciated. Wht should I look for? Regards.
Hi, you can resolve this by following this howto. http://www.debian-administration.org/articles/343 Configuring Dynamic DNS & DHCP set your resolve.conf to resolve on localhost first and set the search order. example of the resolve.conf search yourlocaldomain.internal.local otherdomain.com nameserver 127.0.0.1 nameserver ipofprovider Louis>-----Oorspronkelijk bericht----- >Van: samba-bounces+belle=bazuin.nl@lists.samba.org >[mailto:samba-bounces+belle=bazuin.nl@lists.samba.org] Namens >Olivier Parisy >Verzonden: vrijdag 16 mei 2008 2:05 >Aan: samba@lists.samba.org >Onderwerp: [Samba] NetBIOS name resolution from Linux > >Hi all, > >I set up a Samba server (version 3.0.24) names "Lamp" on a Debian Etch >distribution. It provides a "guest" (guest ok = yes, guest only = yes, >security = SHARE) access to a "share" directory, which works fine. >Indeed, I can access \\lamp\share from a Windows machine (named >"Ginger") without issuing a password. > >I can also ping the Linux machine from the Windows one using "ping >Lamp", and get the Windows machine IP from its NetBIOS name: ># nmblookup Ginger >querying Ginger on 192.168.1.255 >192.168.1.22 Ginger<00> > > >But I cannot ping (or, more generally, resolve the name of) >the Windows >machine from the Linux one: ># ping Ginger >ping: unknown host Ginger > > >I hence followed the guidelines from those links: >http://ubuntuforums.org/archive/index.php/t-182824.html >http://www.linuxquestions.org/questions/linux-networking-3/linu >xsamba-pdc-cant-resolve-windows-names-622797/ > >Which means I installed winbind and modified /etc/nsswitch.conf by >adding "wins" to the "hosts" entry. As I understand it, >winbind provides >a bridge between nmbd and gethostbyname() by using the "Name Service >Switch". Please note that I am not interested in the "active >directory" >part of winbind, nor in joining a domain, etc. > >Anyway, after I performed those modifications, "ping Ginger" actually >worked. But then, \\lamp\share could not be accessed anymore >(the error >message was "The specified group does not exist"). > >Now, as soon as I remove the winbind package, I can access >\\lamp\share >again, but "ping Ginger" does not work anymore. > > >I've been suggested on #samba to drop winbind and simply add "wins >support = yes" to smb.conf; but then "ping Ginger" does not >work any better. > > >So, can I keep my simple "share" configuration, *and* >integrate NetBIOS >name resolution to my Linux system using Name Service Switch? > >FWIW, I posted my smb.conf here: http://pastebin.ca/1019614 ><http://pastebin.ca/1019614> and nsswitch.conf here: >http://pastebin.ca/1019612 <http://pastebin.ca/1019612>. > >Any hint would be greatly approciated. Wht should I look for? > >Regards. > >-- >To unsubscribe from this list go to the following URL and read the >instructions: https://lists.samba.org/mailman/listinfo/samba >
On 5/16/2008, L.P.H. van Belle (belle@bazuin.nl) wrote:> set your resolve.conf to resolve on localhost first and set the > search order. > > example of the resolve.conf > search yourlocaldomain.internal.local otherdomain.com > nameserver 127.0.0.1 > nameserver ipofproviderMuch better to use the opendns servers than any randon ISP DNS... -- Best regards, Charles
A few thoughts, take from them what you will (and remember, free advice is worth what you pay for it). It's really good to have proper IP name resolution. Requires DNS or (ugh) hosts files. It can also be good to have NetBIOS name resolution, if you have the need (Windows type browsing and sharing in non-native AD environments). Implies WINS or (ugh) lmhosts files for resolution (or you're left only with broadcasts). It's good to avoid security=share, especially if you want to run WINS. And yes, a proper setup using security=user can provide guest shares. Winbind is normally used to authenticate against Windows servers that are running WINS or AD, so that you don't need to duplicate the Windows user/groups. You don't mention how big your network is, but if you're dealing with 5 or more systems I highly suggest both DNS and WINS over their static equivalents, hosts and lmhosts, respectively. Even with fewer systems, it can be a good idea to bother with the setup if you intend to grow or want flexibility. If you run a WINS server, you need to tell your clients to register with it (this is easily done with DHCP - then you don't have to manually configure them), or it wont contain their information. -- Chris
On Friday 16 May 2008, L.P.H. van Belle wrote:> so yes sure opendns is useable but if you really want it ...Actually it's horrible for mail servers. Although fine if you value its ability to block sites for desktop use. At sites that I use it, I've needed 2 DNS caches, one that forwards to OpenDNS for non-local systems that desktops connects to, and one that resolves via the root servers for the mail server. For my own use I prefer to resolve via the root servers. -- Chris
On Thu, May 15, 2008 at 7:05 PM, Olivier Parisy <ml.olivier.parisy@free.fr> wrote:> Hi all, > > I set up a Samba server (version 3.0.24) names "Lamp" on a Debian Etch > distribution. It provides a "guest" (guest ok = yes, guest only = yes, > security = SHARE) access to a "share" directory, which works fine. Indeed, I > can access \\lamp\share from a Windows machine (named "Ginger") without > issuing a password. > > I can also ping the Linux machine from the Windows one using "ping Lamp", > and get the Windows machine IP from its NetBIOS name: > # nmblookup Ginger > querying Ginger on 192.168.1.255 > 192.168.1.22 Ginger<00> > > > But I cannot ping (or, more generally, resolve the name of) the Windows > machine from the Linux one: > # ping Ginger > ping: unknown host Ginger > > > I hence followed the guidelines from those links: > http://ubuntuforums.org/archive/index.php/t-182824.html > http://www.linuxquestions.org/questions/linux-networking-3/linuxsamba-pdc-cant-resolve-windows-names-622797/ > > Which means I installed winbind and modified /etc/nsswitch.conf by adding > "wins" to the "hosts" entry. As I understand it, winbind provides a bridge > between nmbd and gethostbyname() by using the "Name Service Switch". Please > note that I am not interested in the "active directory" part of winbind, nor > in joining a domain, etc. > > Anyway, after I performed those modifications, "ping Ginger" actually > worked. But then, \\lamp\share could not be accessed anymore (the error > message was "The specified group does not exist"). > > Now, as soon as I remove the winbind package, I can access \\lamp\share > again, but "ping Ginger" does not work anymore. > > > I've been suggested on #samba to drop winbind and simply add "wins support > yes" to smb.conf; but then "ping Ginger" does not work any better. > > > So, can I keep my simple "share" configuration, *and* integrate NetBIOS name > resolution to my Linux system using Name Service Switch? > > FWIW, I posted my smb.conf here: http://pastebin.ca/1019614 > <http://pastebin.ca/1019614> and nsswitch.conf here: > http://pastebin.ca/1019612 <http://pastebin.ca/1019612>. > > Any hint would be greatly approciated. Wht should I look for?You just need to do this: http://lucasmanual.com/mywiki/SambaDomainController#head-8ae23b786749b4d46ef0e9ed22148e63eeab95e7 Lucas
Hi, i used Bind9 ( with dhcp3), with caching dns with forwarders. i have 4 local zones. these are in the resolve.conf as search domains. ( 4 different subnets ) If you want a copy of my config its possible. Louis>-----Oorspronkelijk bericht----- >Van: samba-bounces+belle=bazuin.nl@lists.samba.org >[mailto:samba-bounces+belle=bazuin.nl@lists.samba.org] Namens >Charles Marcus >Verzonden: maandag 19 mei 2008 12:56 >Aan: samba@lists.samba.org >Onderwerp: Re: [Samba] NetBIOS name resolution from Linux > >On 5/19/2008, L.P.H. van Belle (belle@bazuin.nl) wrote: >> 1c) setup DHCP3 + DDNS >> this is done so every pc which is connected to the network >> and gets dhcp ip also gets recorded in the dns server. > >What did you use for DNS? Bind? How is it configured (caching only with >forwarders?) > >-- > >Best regards, > >Charles >-- >To unsubscribe from this list go to the following URL and read the >instructions: https://lists.samba.org/mailman/listinfo/samba >