On Thu, Jul 16, 2009 at 9:39 AM, David Lum<david....@nwea.org> wrote:
> Does \\SERVERNAME (not FQDN) work if there is no NetBIOS in use?
"SERVERNAME" is submitted by SMB to the rest of the OS for name
resolution. The OS will do whatever it is configured to do. If DNS
is configured and can resolve "SERVERNAME", it will. Ditto NetBIOS
broadcast, WINS, ...\ETC\LMHOSTS, ...\ETC\HOSTS, etc.
DNS will generally not attempt to resolve a bare label
("SERVERNAME"), but will append whatever suffix(es) are configured on
the system, and try them one at a time. So if you've got
"corp.example.com" and "example.com" in your DNS search list (in that
order), first "SERVERNAME.corp.example.com" will get used, then
"SERVERNAME.example.com". The system will use the first answer that
isn't NXDOMAIN (non-existent domain).
If you're using the basic all-Microsoft configuration (Active
Directory, AD-integrated DNS, dynamic DNS updates, all nodes
configured to use AD-integrated DNS servers for resolution, no other
resolving nameserver configured, etc.), that all happens pretty much
automatically.
I don't remember how Windows determines the order in which
mechanisms are tried, or if you can change it. Occasionally this
matters if multiple mechanisms are nominally configured but only one
is doing what you want. Stuff may wait ("hang") until one mechanism
times out before trying the next, or one mechanism may return an
answer that is "wrong" as far as you're concerned.
-- Ben
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
