Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 804
  • Last Modified:

Domain Controller Not Listed When Adding Users Under the Location Button

Hi Experts,

This issue occurs rarely, however I am trying to find out the cause of it...


We have a Windows 2000 AD Server at Site A.  Site B is connected to site A through a VPN.  When adding users, groups or even a new workstation to the domain, the workstation or the OS does not see the remote AD Server.

My work around has been to try repeatedly or force the workstation by connecting to that server running \\ip address of that server.

Any ideas on why this is being cased and how to fix it permanently?

Thanks for all your help!
0
byd2k
Asked:
byd2k
  • 2
1 Solution
 
mkdonohueCommented:
You could preload the cache via the lmhosts file:

Locate the file %systemRoot%\System32\Drivers\Etc\lmhosts on the affected machine.

If this file does not exist, please create it. There is likely a file called lmhosts.sam  (The .sam extension indicates "Sample") that you can rename to lmhosts <- no file extension.

Add the following entries to this file:
10.x.x.x <SERVERNAME>  #PRE #DOM:<DOMAIN NAME>
10.x.x.x "<DOMAIN NAME> \0x1b"   #PRE

Where 10.x.x.x is the IP of your windows server, <SERVERNAME> is the name of the server and <DOMAIN NAME> is the name of your domain. Make the entries without the < & > characters.

Note 1: In the first entry, the domain name is case sensitive. Make sure that you use uppercase characters for the domain name. If you use lower-case characters for the domain name, NetBT does not recognize the name.

Note 2: In the second entry, there must be a total of 20 characters within the quotations (the domain name plus the appropriate number of spaces to pad up to 15 characters, plus the backslash, plus the NetBIOS hex representation of the service type).

After you add the entries, save the file.

At a command prompt, type nbtstat -R       < --Note The -R is case sensitive and must be uppercase.
After you type this command, you should receive the following message:

Successful purge and preload of the NBT Remote Cache Name Table.


At a command prompt, type nbtstat -c      <---Note The -c is case sensitive and must be lower-case
After you type this command, you should receive a display that is similar to the following:  

                              
                              
                        Node IpAddress: [10.x.x.x] Scope Id: []
                        
                        NetBIOS Remote Cache Name Table      
         Name        Type        Host Address      Life [sec]      
                        ---------------------------------------------------------------------------------------      
      SERVERNAME      <03>  UNIQUE      10.x.x.x      -1      
      SERVERNAME      <00>  UNIQUE      10.x.x.x      -1      
      SERVERNAME      <20>  UNIQUE      10.x.x.x      -1      
      DOMAINNAME      <1B> UNIQUE      10.x.x.x      -1      
                              

Once you have that result, name resolution should not be an issue.

The one caveat is your are hardcoding IP addresess. You will need to update these files if your servers IP ever changes.

Let me know if that works for you.
0
 
byd2kAuthor Commented:
Hi mkdonohue,

I hope to have some time later this week to perform the solution.  I just wanted to let you know that I am still in progress with this issue.

Thanks,
byd2k
0
 
mkdonohueCommented:
I *think* the solution I posted should have resolved his issue, I had been hoping to hear back from him if that was the case. :(
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now