Problem Creating Trusts Between Domains.

[dreynolds20]

Hi,

I am trying to create a trust between my new Windows 2003 Domain and my old Windows NT Domain.

I have created the trust on my NT Domain but everytime I try and set it up on the new Domain I get teh error message below:

The verification of the incoming trust failed with the following error(s):
The target system FPSERVER does not support NetLogon trust password verification.
A secure channel reset will be attempted.
The secure channel reset failed with error 1355: The specified domain either does not exist or could not be contacted.

The verification of the outgoing trust failed with the following error(s):
The trust password verification test was inconclusive.
A secure channel reset will be attempted.
The secure channel reset failed with error 1311: There are currently no logon servers available to service the logon request.

My setup:

Old Domain:

172.35.1.*
WINS Enabled.

New Domain:

192.168.0.*
DNS Enabled.

Any help would be appreciated.

Cheers

Dave

 

[aftertaf]

i think first off they need to speak the same protocols...

you are trying to set up a trust where one side only speaks chinese and the other only japanese..

but im sure theres another reason, not convinced myself....
but anyway, if it can help

Aftertaf

"Resolve is never stronger than the night before it was never weaker

 

[bofhrevenge2]

dreynolds20 is this still not working?

Did this link not help?

http://support.microsoft.com/default.aspx?scid=kb;en-us;325874

I don't mean to sound bitter, cold, or cruel, but I am, so that's how it comes out - Bill Hicks

 

[dreynolds20]

No it didnt mate.

I do appreciate your help on this.

The Windows NT domain can kind of see the new domain but the new Windows 2003 domain can not see the old one at all.

The I.P. Address scheme is different and they are both running parralell on the smae site.

 

[bofhrevenge2]

I assume there a router in between?

I don't mean to sound bitter, cold, or cruel, but I am, so that's how it comes out - Bill Hicks

 

[dreynolds20]

No.

They are sitting next to each other joined by a Cisco Switch.

 

[bofhrevenge2]

Have you entered the IP address of your old server into the new domains DNS?

I don't mean to sound bitter, cold, or cruel, but I am, so that's how it comes out - Bill Hicks

 

[bofhrevenge2]

Also is there just the one server left in the old domain, could you bring it into the same IP range?

I don't mean to sound bitter, cold, or cruel, but I am, so that's how it comes out - Bill Hicks

 

[dreynolds20]

I added a new zone with the 172.35.0.* address's.

Because of the way everything is setup it is not possible to change the old system.

 

[bofhrevenge2]

Any luck?

I don't mean to sound bitter, cold, or cruel, but I am, so that's how it comes out - Bill Hicks

 

[tdong]

simple solution would be go here on the Server 2003 C:\WINDOWS\system32\drivers\etc open host using notepad then enter this

172.35.0.* dnsoftheNT
172.35.0.* computernameofNT

that would let you enable trust

 

[bofhrevenge2]

tdong could be right try that instead of the LMHOSTS file as ecunupe suggested.

I don't mean to sound bitter, cold, or cruel, but I am, so that's how it comes out - Bill Hicks

 

[dreynolds20]

Already done that, its a very strange problem.

I have done everything that has been recomended and I have everything I can think of and it still wont work but I have nothing strange here.

 

[aftertaf]

googling suggests that it is a name resolution problem somewhere...

http://support.microsoft.com/default.aspx?scid=kb;EN-US;180094

both servers need to resolve each other's names via TCP/IP & WINS... is this the case?

Aftertaf

"Resolve is never stronger than the night before it was never weaker

 

[bofhrevenge2]

dreynolds20 after you added the LMHOSTS record can you ping the PDCe in the 2003 domain and vice versa by 'NetBIOS' name.

As aftertaf suggests it lookslike it's down to name resolution, I have a 2003 AD that trusts an NT4 Domain and vice versa with no problems. All i did was follow the instructions in the link and also add a Host (A) record into my Forward lookup zone pointing to the NT4 PDC and it's worked fine for five monthes now.


I don't mean to sound bitter, cold, or cruel, but I am, so that's how it comes out - Bill Hicks

 

[dreynolds20]

I can ping the servers by I.P. Address and by name.

I have the lmhosts files set-up, I have it created forward and reverse lookups in DNS, they are on the same site and plugged into the same switch.

The old domain can see me but I still cant see the old domain, I have disabled any firewalls or things that sit in the middle and it still does not work.

 

[aftertaf]

have you enabled netbios on your 2003 server?

Aftertaf

"Resolve is never stronger than the night before it was never weaker

 

[bofhrevenge2]

Also did you say that you created a new zone in DNS, you should only need to add an (A) record to your current forward lookup zone.

I don't mean to sound bitter, cold, or cruel, but I am, so that's how it comes out - Bill Hicks

 

[dreynolds20]

Netbios is enabled on the servers.

Host Record has been created for the Windows NT DC.

 

[dreynolds20]

The trust has been created on both the servers but when I try and validate the trust on the new server I get the message below.

Verification of the trust between the domain X and the domain X was unsuccessful because: There are currently no logon servers available to service the logon request.