Need a little networking help

[office boy]

My SetiQue at work has about 6 computers that it serves, but the problem is that the names don't show up in setiQ, I have found that since each computer here has it's own Internet IP (206.63.103.**) that setiQ gets DNS names (some crap with a "W" and then last 2#s of IP) before local (netbios) computer names. Now last night the router bombed, and so I came in this morning, and ever so pretty names showed up in the Que dialog box.
Anyway is there a way to get my computer to NOT resolve the external names of these IP's and to get it to use proper names?
I'm using Win2K.
Anyone? I know we got some MSCE network types here

 

[Fardringle]

Are the individual IP addresses assigned by a DHCP server, or are they static (permanent) addresses? If they are DHCP addresses, then in your Network Properties for TCP/IP, you can set it to use DHCP for WINS resolution in order to resolve the names of the computers. Or, if they are permanent addresses, or you don't want to use WINS/DHCP, you can edit the HOSTS.SAM file in your Windows directory and add entries for each of the clients. That way, the SetiQ computer will never ask the DNS server for the names and will instead get them directly from its own Hosts file...

 

[office boy]

All static.
and what's the "HOSTS.SAM" I have a lmhosts.sam, is that the same thing?

 

[office boy]

So i can just stick
the ip and then the computer name in there and my computer will use that?

the format is like

"0.0.0.0 computer1" right?

 

[Poof]

Office boy - Lmhosts.sam is the sample lmhosts file (for NetBIOS name resolution). Hosts.sam is similar but is the sample file for TCP/IP hostnames (fully qualified domains). They're both in /%systemroot%/system32/drivers/etc for NT/2K or in c:\windows for 9x.

If there's a hosts file on your Setiqueue machine that has a list of the hostnames of your static IP machines, then it uses that file to resolve the names of those machines in the Setiqueue log...

[EDIT: To put the correct path....]

 

[JonB]

No, LMHOSTS isn't the same as HOSTS

The *.SAM files are just sample files. A HOSTS file has NO extension (or it won't work).

Here is a HOSTS.SAM file I use. Just put your own information at the bottom, save it in the same folder as your LMHOSTS file but be sure it has NO extension.


# Copyright (c) 1993-1995 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows NT.
#
# 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

 

[Poof]

<< &quot;0.0.0.0 computer1&quot; right? >>



That's the format for &quot;lmhosts&quot;. The &quot;hosts&quot; file would be different. I don't think Setiqueue uses lmhosts to resolve names, it uses hosts.

 

[office boy]

Reboot required?

 

[Poof]

Technically no but with windud, it's a good idea...

 

[office boy]

Wow, thanks guy's, I'm not sure if it's working yet (next result isn't for another 18min), but I can ping computernames now, so that seems good.

BTW this seems like a good practical joke tool to. You could have any URL resolve to another IP right? (like www.msn.com to some pr0n page?)

 

[office boy]

WOOHOO it works

BTW is it case sensitive?

 

[Poof]

LOL Office boy!

I think by default, most of the OS's will check the hosts file first before it checks DNS...

[EDIT: You're typing too fast for me to respond!!!! With windud, nothing is case sensitive except maybe passwords... with *nix, stuff usually is...]

 

[Viztech]

Yup. Winblows checks the hosts file first before using DNS, so hijacking is very possible.
I spent hours trying to solve a DNS issue, which I was able to solve with a Host file....just as long as they don't change the IP of that server.

viz