Windows 2003 Domain Problem.

[dreynolds20]

Hi,

I have a Windows 2003 domain that I need to talk to a Windows NT domain.

I have some software on a PDC that my user base needs to use but they are all running on a new Windows 2003 domain with Windows XP clients, I do not need any replication between the domains but I do need them to access the old PDC just to access the software that is not available in a newer version.

Any help would be appreciated.

Cheers

Dave

 

[bofhrevenge2]

If you create a trust relationship between the domains the users will be able to access resources in the NT4 domain.

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

 

[dreynolds20]

Do you know of any good articles for doing this.

 

[bofhrevenge2]

This is for an NT4 to 2000 trust but i'm pretty sure it's the same.

http://support.microsoft.com/?kbid=306733

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

 

[bofhrevenge2]

http://support.microsoft.com/?kbid=308195

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

 

[dreynolds20]

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.

 

[bofhrevenge2]

Have a look at this

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

 

[ecunupe]

Hey one thing you also want to look at is dropping an lmhost file in the PDC and PDCE for the other domain and Domain contollers on these machines. Usually when we see a problem with trusts it is with restrictanonymous, Smb signing, or with netbios communiciations, because we are using a trust between Win2k3 and Winnt we still use ntlm authentication. Therefore i would put the 1B and 1C records on the PDCs respectively.

 

[dreynolds20]

Sorry my NT knowledge is very distant.

How do I create an lmhost file and where would I put it on both servers.

 

[dreynolds20]

Oh and I dont surely need a WINS Server on my new domain.

 

[bofhrevenge2]

You don't need a WINS server and i don't think you require an LMHOSTS entry either (It's worth trying tho) I have an NT4 to 2003 trust and it works fine and we don't use WINS.

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

 

[bofhrevenge2]

Actually thinking about it ecunupe is probably right as you are crossing a router.

LMHOSTS is in

C:\WINDOWS\system32\drivers\etc

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