RE: Re: Windows Mapped Drives - Strange

["Ady Joy" <ukha@xxxxxxxxxxxxxxxxx>]

If you are trying to resolve 'windows computernames' to IP addresses (and
if
you are looking to make up for the fact that you don't have a WINS server
then 'windows computernames' to IP is what you are trying to do) then you
should look at creating a file called LMHOSTS in
C:/windows/system32/drivers/etc. There is an example LMHOSTS file called
LMHOSTS.SAM for you to peruse, but basically adding <ip.address>
<computername> #PRE should do the trick. i.e.

192.168.0.102  mydesktop  #PRE

The HOSTS file is used to resolve DNS names to IP addresses and is subtly
different. By all means add the entry to the HOSTS (without the #PRE) as
well if you aren't sure whether it is using 'windows computernames' or DNS
names, and it will use the one it needs.

Hope this helps someone - finally something I know a bit about!

Ady

PS DNS names are traditionally anything running TCP/IP with a hostname that
isn't running Windows, and the correct term for 'windows computernames' is
NETBIOS names.

> -----Original Message-----
> From: nick@xxxxxxx [mailto:nick@xxxxxxx]
> Sent: 28 September 2004 21:02
> To: ukha_d@xxxxxxx
> Subject: [ukha_d] Re: Windows Mapped Drives - Strange
>
>
>
> > I don't really know :-(  and TBH, the
> > whole "hosts file thing" is still
> > a bit of a mystery to me. Just
> > guessing, but if the WINS handling has
> > changed in XP (as Nick suggests)
> > updating the hosts file may do that
> > name resolution locally for you
> > instead of a dedicated machine having to
> > be the WINS server.
>
> Sounds logical enough.  An entry in Hosts avoids the need for the PC
> to go looking for a DNS (or WINS) server to translate the name to an
> IP address - it gets it from the file instead.
>
> Nick
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>