LMHOSTS

r00k

r00k

2[H]4U
Joined
Aug 24, 2004
Messages
2,696
Hey everyone, i have a specific situation that i need to resolve, and i can't seem to get it to work despite my attempts. Many sites describe vaguely how to amend the LMHOSTS file accordingly, but i need to see it as it would actually be written.


I have one main office, and one remote location. I have set up a VPN using SonicWALL routers. There is a windows 2003 domain set up at the office, and i need to connect two machines at the remote location to the domain. I am certain this can be done with the LMHOSTS file. The names are changed but have the exact same number of characters.



Office:
::::::::::::::::::::::
Network: 192.168.1.0 / 24
Server IP: 192.168.1.254
Server FQDN: ableoneserver.ableone.local
domain: ableone.local


Remote Location
::::::::::::::::::::::::::
Network: 192.168.0.0 / 24
Computers: Windows XP Pro

Somebody please show me exactly what i need to add to my lmhosts file to allow my two remote pc's to be able to join the domain.
 
SpaceHonkey said:
First of all LMHOSTS is for NetBIOS resolution, not DNS. HOSTS is the file you are looking for.
Click to expand...
Not for what he's trying to do. :)

I've had to do this before due to a variety of issues - nevertheless, it's been a long while since I've had to do it.

Here are some supporting documents:

http://support.microsoft.com/kb/314108
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/cnet/cnfd_lmh_tgvz.mspx?mfr=true
http://support.microsoft.com/kb/150800
http://en.wikipedia.org/wiki/LMHOSTS

From the first link...

10.0.0.1 PDCNAME #PRE #DOM: DOMAIN_NAME
10.0.0.1 "DOMAIN_NAME \0x1b" #PRE

Note: There's no space between the DOM: and the DOMAIN_NAME, I just put one there to prevent the forum from making it into a smiley.

Before putting the time and effort into this though -- ensure that "Enable NETBIOS over TCP/IP" is checked in your TCP/IP-WINS properties. The default value does not enable it unless your DHCP server has that value set. You could also try using WINS.

Ultimately though -- you'll need to find out what's going on between your remote sites that's preventing name resolution and proper domain function as nothing is going to work 100% until you do.

Hope that helps...
 
You must log in or register to reply here.
Back
Top