>>Hi John,
>>
>>>Note this is straight forward when using NT workstation or W2k as a workstation accessing another like platform or server. With '98 you have to setup a host file, which is a major pain in the podex! I have some info on this if this is what you are after.
>>
>>Where does the host file go, how is it named, and will it work on Win95?
>
>Ok, here is what I found from my old machine at the office:
>The layout is critical. It must have the proper number of spaces between the ipaddress and the domain name.
>
>c:\windows\hosts.sam
># Copyright (c) 1998 Microsoft Corp.
>#
># This is a sample HOSTS file used by Microsoft TCP/IP stack for Windows98
>#
># This file contains the mappings of IP addresses to host names. Each
># entry should be kept on an individual line. The IP address should
># be placed in the first column followed by the corresponding host name.
># The IP address and the host name should be separated by at least one
># space.
>#
># Additionally, comments (such as these) may be inserted on individual
># lines or following the machine name denoted by a '#' symbol.
>#
># For example:
>#
># 102.54.94.97 rhino.acme.com # source server
># 38.25.63.10 x.acme.com # x client host
>
>#127.0.0.1 localhost

David,

The file on your drive, hosts.sam is a sample file meant to show you the syntax. To activate a real file, you have to name it lmhosts (no extension), and place it in C:\WINNT\system32\drivers\etc\

after you modify your lmhosts file, you have to tell Windows to read it, and use the entry when resolving names. To do this, use the commands:

nbtstat -R

to release and reload the names from the file. To see if your remote name is listed:

nbtstat -c

After doing this, you should be able to NET USE using the computer name, or locate the machine in the Find Computer dialog.

Note- this whole discussion is completely irrelevant to Mark's original question-