-
From: Gaiseric Vandal [mailto:gaiseric.van...@gmail.com]
Sent: Wednesday, February 02, 2011 7:39 AM
To: 'Samba'
Subject: RE: [Samba] can connect to 2 samba servers by name but to one by
IPonly
This is where things stand so far:
Pdc1 is samba 3.4.x
Bdc1 is samba 3.0.x (also the WINS se
Thursday, January 13, 2011 2:14 PM
To: TAKAHASHI Motonobu
Cc: Samba
Subject: Re: [Samba] can connect to 2 samba servers by name but to one by
IPonly
nslookup on windows machines does require the FQDN name- i.e.
"pdc1.mydomain.com."
ping does not (windows will appropriately add the domain
nslookup on windows machines does require the FQDN name- i.e.
"pdc1.mydomain.com."
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
2011/1/13 Gaiseric Vandal :
> 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 t
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