[Samba] can connect to 2 samba servers by name but to one by IPonly
gaiseric.vandal at gmail.com
Thu Jan 13 12:14:08 MST 2011
nslookup on windows machines does require the FQDN name- i.e.
ping does not (windows will appropriately add the domain name.)
I have not tried "net use \\pdc1.mydomain.com" from a VPN connection.
I know that "nslookup" and "ping" in Windows have separate name
resolution routines, and handle domain suffixes a little
differently. Again, that should have affected all machines.
Machines on VPN connection get the "mydomain.com" appended to the VPN
virtual NIC, but it is not the default domain for the machine.
I looked at my DNS server- I can't see any differences in the entry for
"pdc1" vs any other machine- even though DNS is the only thing that
would make sense. But VPN clients use the 2ndary DNS servers for name
lookup, not the primary. I may try configuring VPN clients to use
the primary DNS server. None of the server names are 16 characters or
On 01/13/2011 12:38 PM, TAKAHASHI Motonobu wrote:
> 2011/1/13 Gaiseric Vandal<gaiseric.vandal at gmail.com>:
>> Adding pdc1 to the hosts file (c:\windows\system32\drivers\etc\hosts) did
>> not make a difference. After adding pdc1 to lmhosts, "net use \\pdc1" did
>> work. So in the case of pdc1 one, the name is being resolved as a netbios
>> name (i.e. via lmhosts) not a tcp/ip type name (i.e. via dns or hosts)
>> But then why does "net use" work with all the other windows or samba
>> servers? As far as I can tell, DNS is the only method by which the names
>> are being resolved.
> What does "nslookup PDC1" and "ping PDC1" show?
> If you have a host named "PDC1.example.com" then nslookup PDC1 may
> return the IP address of "PDC1.example.com", not the IP address of
> expected "PDC1".
> Anyway, you had better debug at the view of DNS name resolution, not Samba.
> TAKAHASHI Motonobu<monyo at samba.gr.jp>
More information about the samba