Discussion Locked

Domain Membership

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,
Here is information on our network..
1. NT 4.0 Domain controller
2. 3 BDC's (NT 4.0)
3. Two locations and on different subnets
192.168.2.xxx and 10.0.39.xxx
255.255.255.0 255.255.255.192
4. PDC is at main location, and one BDC is at the remote location
5. Have a VPN tunnel established and the needed route statements are 'in place'
6. All computers are on the same domain.
7. Problem is at the remote location.
8. We are able to ping ANY computer by IP address, andby name.
9. Win98 workstations are connected fine and have no problems.
10. Problem: Setting up two Win2000 Pro workstations. They are on the same workgroup.
11. They can browse the network, see all computers, and ping any computer by IP or by Name
12. These two computers are NOT able to join the domain.
13. When attempting to join, this message appears...
The following error occurred attempting to join the domain "domain": The specified domain either does not exist or could not be contacted.
14. I have tried different HOSTS and LMHOSTS files, but nothing will work.

Any suggestions.

Thanks

4 replies

by tony.colgrove

It seems you are having some communication problems across the VPN. The Win2k machines MUST talk to the PDC to join the domain.
Does you BDC, communicate fine with the PDC? Are you getting any errors in the event viewer on the BDC.
You might want to add an entry in the the LMHOSTS file a #PRE #DOM:domain to the domain controllers IP (not to the PDC computer name, but to the domain name)
ie:
192.168.2. "domainname \0x1c" #PRE #DOM:domainname
There should be exactly 20 characters inside the quotes. The \ should be the 16th character.

by rabbit_runner

I have tried the LMHOSTS file with the ..

192.168.2. "domainname \0x1c" #PRE #DOM:domainname

Using both the PDC and the BDC (at different times) In both cases, I came up with the same error.

NOTE: one time the error was different. It was indicating that the username and password for the Administrator were not correct. Re-typed, several times, would not recognize the username.

NOTE 2: There is another NT 4.0 server at the remote location. It is able to be a member of the domain (was added before the BDC was placed there). Problem seems to only be with the Win2K systems.

This discussion is closed to new replies.