192.168.2.20
192.168.2.21
192.168.0.1
Are all 3 of these Domain Controllers?
Main Topics
Browse All TopicsOn occassion, it becomes impossible to map drives or see resources on the 2 domain controllers (only servers) unless the FQDN is entered.
We don't have WINS running. This is a remote office (192.168.0.x) connected to main office (192.168.2.x) via VPN. It's been operational for > 3 years. Only recent changes have been the reboots after install Windows Updates on Server / Workstation. Yeah. I know....
mydomain = NetBIOS Domain Name
mydomain.com = FQDN
dc1 = W2K3 Domain Controller
My workstation, ws1, has [X] Enable LMHOSTS and (X) Enable NetBIOS over TCP/IP enabled.
C:\>IPCONFIG /REGISTERDNS
Windows IP Configuration
Registration of the DNS resource records for all adapters of this computer has been initiated. Any errors will be reported in the Event Viewer in 15 minutes..
C:\>IPCONFIG /ALL
Windows IP Configuration
Host Name . . . . . . . . . . . . : ws1
Primary Dns Suffix . . . . . . . : mydomain.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mydomain.com
mydomain.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : mydomain.com
Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network Connection
Physical Address. . . . . . . . . : 00-13-72-13-7A-FC
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.195
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.2.20
192.168.2.21
192.168.0.1
Lease Obtained. . . . . . . . . . : Wednesday, May 16, 2007 10:27:13 AM
Lease Expires . . . . . . . . . . : Thursday, May 17, 2007 10:27:13 AM
~~~~~~~~~~~~~~~~~~~~~~~~~~
C:\>NET USE H: /HOME
The user's home directory could not be determined.
More help is available by typing NET HELPMSG 3915.
C:\>NET HELPMSG 3915
The user's home directory could not be determined.
~~~~~~~~~~~~~~~~~~~~~~~~~~
C:\>NET VIEW \\dc1
System error 53 has occurred.
The network path was not found.
C:\>PING dc1
Pinging dc1.mydomain.com [192.168.2.20] with 32 bytes of data:
Reply from 192.168.2.20: bytes=32 time=73ms TTL=126
Reply from 192.168.2.20: bytes=32 time=71ms TTL=126
Ping statistics for 192.168.2.20:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 71ms, Maximum = 73ms, Average = 72ms
Control-C
^C
~~~~~~~~~~~~~~~~~~~~~~~~~~
C:\>NET USE H: \\dc1\jeff$
Enter the user name for 'dc1': jeff
Enter the password for dc1:
System error 5 has occurred.
Access is denied.
C:\>NET USE H: \\dc1\jeff$
Enter the user name for 'dc1': mydomain\jeff
Enter the password for dc1:
System error 5 has occurred.
Access is denied.
C:\>NET USE H: \\dc1.mydomain.com\jeff$
The command completed successfully.
Thoughts?
Bob
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
If you don't have WINS running on your network and you're trying to resolve a machine name that is on a different network segment through NetBIOS, then you'll have to have an LMHOSTS file as adam mentions above. One of the ways that a Windows box can perform name resolution is via broadcast traffic, but since host "dc1" is on a different network segment, that method won't work. So you'll either need a functioning WINS server or a properly configured LMHOSTS file to do what you're wanting to do.
It sounds like you're implying that this has been working for a while and has suddenly stopped. Is this the case?
Everything batry boy said is true. But I would imagine that you want to use DNS for name resolution. If this is the same domain, then the "DNS Suffix Search List" should transform computernames into FQDNs. The only problems I could think of are:
1. It is trying to use NetBIOS Name resolution, which it definititely is if LMHOSTS is enabled.
2. that 192.168.0.1 address is not a domain controller but actually a router of some kind. This can lead to intermitten problems everywhere because all the DNS servers in an Active Directory domain need to be Domain Controllers.
192.168.2.20 and 192.168.2.21 are the DC's visible only through the VPN.
192.168.0.1 is the local router which provides DNS proxy when the VPN is down.
The VPN has [X] NETBIOS Enabled on the VPN configuration.
I'm not at the remote site right now -- will be shortly. I'll try removing the 0.1 and see what happens.
Bob
OK, it seems that "net use" and "net view" try and use NetBIOS name resolution only. This is something i probably knew at one point but then forgot.
You can enable DNS name resolution for NetBIOS names by following the instructions here:
http://support.microsoft.c
OR
You can setup NetBIOS Name resolution. Since you are on different networks, broadcasting will not work. You will need to either use LMOHSTS or WINS. If you use LMHOSTS, you will have to make a static entry in the LMHOSTS file with the computername and IP Address.
Adam,
You got me looking in the right direction. The KB article above doesn't appear applicable for XP but further searches lead me to a registry DWORD = DhcpNodeType at HKEY_LOCAL_MACHINE\SYSTEM\
I set the value to 8 which now shows up as Hybrid in IPCONFIG /ALL.
Did NET USE H: /HOME and it worked! Then did NET VIEW \\DC1 and it worked too.
Not sure what value it should be. I'll investigate later. Thanks much!!
Business Accounts
Answer for Membership
by: SysExpertPosted on 2007-05-16 at 09:48:34ID: 19102259
CHeck the DNS using the windows resource kit tools.
I hope this helps !