On Tue, May 5, 2009 at 9:26 AM, David Lum <[email protected]> wrote: > Wouldn't \\machinename\c$ have to be \\FQDN\c$ to work if there is no > NetBIOS?
Nope. In most places, when you give Windows a name of any kind, it does several things to try and resolve that name into an IP address: 1. hosts file 2. DNS resolver 3. lmhosts file 4. NetBIOS name resolution The DNS resolver will stick DNS suffixes on to the end of an unqualified name. Depending on Windows release, Service Pack, and/or configuration tweaks, it may also try the bare name, and it may also append DNS suffixes to names with some number of dots. (IIRC) By default NetBIOS name resolution tries broadcast first, then WINS (if configured). That can be changed by setting the NetBIOS node type. I recommend setting the type to either P (peer, WINS only) or H (hybrid, WINS first, then broadcast) -- that way you'll cut down on broadcast traffic, and prefer WINS, which is generally more reliable anyway. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
