IT Employment

Ask something
Discussion Locked

Problem in accessing Trusted domain

0 helpful
2 replies

by inbarasank

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

Hi All,
We have one of client client trusting our forest.Client domain is NT domain.Our Forest is w2k forest. Client is having one way trust to our forest.We are having problem accessing few servers in our client domain.when i try to access the server it throws a error msg that there is no logon servers available to logon to this server. Can anyone helpme pls.I really don't know where exactly is the problem.
It will be really helpful if someone throw some light on this to fix this issue.
Thanks
Inba

2 replies

by pcnetworktech

I would add an entry to the lmhost file on both AC/DC and NTserver.

Location: C:\winnt\system32\drivers\etc

Example:
000.00.00.00 servername #PRE #DOM:domainname
000.00.00.00 "Domainame \0x1b" #PRE

Note: Zero are the ipaddress of the server

After entering the lmhost file. Go to DOS prompt and type
ipconfig/flushdns

Ipconfig/registerdns

It will take 3 hours for the changes to take effect. This is due to the default replacation is 3 hours

by rabbit_runner

From each domain can you ping the NetBios domain name? This may be the reason for the inability to connect with a trust. We had a similar situation a few months ago. There wree two NT4 domains, and one was upgraded to Windows 2000 domain with Active Directory. Once the upgrade had been completed, the 2 way trust quit working. We could ping the domain controllers, both by IP and by name. But the trust would not work. Each time, we received an error that stated it could not find the other domain. To check this, we attempted to ping the NetBios domain name from each domain controller. Failed.
Therefore, we added two lines to our HOSTS file. Below are examples for both Domain Controllsers. Substitute your own names and IP addresses.

This included....
---------------
192.168.1.2 NT4_PDC.DOMAIN1.COM NT4_PDC
192.168.1.2 DOMAIN1
---------------
10.10.10.2 W2K_DC.DOMAIN2.COM W2K_DC
10.10.10.2 DOMAIN2
---------------
NOTE: on the Win2k server, the AD domain name may be different from the NetBios domain name. You must use the NetBios domain name in the second line.

This was done to each domain controller and the information would point to the Other domain controller in the other domain. The first line locates the domain controller name and its IP address. The second line set the IP address to the NetBios Domain Name.

Once this was done, the trust was re-established.

Best of Luck.

This discussion is closed to new replies.