RE: trust between windows nt 4.0 and windows 2003 domain

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi,

I think you need to modify the LMHost file manually.

To create a correctly formatted Lmhosts file, follow these steps: 1. Use
any text editor, such as Notepad.exe or Edit.com, to create a file named
Lmhosts, and save it in the following folder: Microsoft Windows NT
----------

%SystemRoot%\System32\Drivers\Etc

Microsoft Windows 95
----------

C:\Windows (the folder where Windows is installed)

Microsoft Windows NT and Windows 2000
---------------------------

%SystemRoot%\System32\Drivers\Etc

Note The file name is Lmhosts, without an extension. If you use
Notepad.exe, it may automatically append the .txt extension. In this case,
at a command prompt, you must rename the file using no extension.
2. Add the following entries to the Lmhosts file: 10.0.0.1 PDCNAME
#PRE #DOM:DOMAIN-NAME
10.0.0.1 "DOMAIN-NAME \0x1b" #PRE

Note The domain name in this entry is case sensitive. Make sure that you
use uppercase characters for the domain name. If you use lowercase
characters for the domain name, NetBT does not recognize the name.

How to write an Lmhosts file for domain validation and other name
resolution issues
http://support.microsoft.com/?id=180094


Best regards,

Vincent Xu
Microsoft Online Partner Support

======================================================
Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================



--------------------
Thread-Topic: trust between windows nt 4.0 and windows 2003 domain
thread-index: AcZeTab/YRluGS4SSeazr0GTBSNAwg==
X-WBNR-Posting-Host: 195.62.26.120
From: =?Utf-8?B?SmFybyBTdGVyYmlrLUxhbWluYQ==?=
<JaroSterbikLamina@xxxxxxxxxxxxxxxxxxxxxxxxx>
References: <7E038624-58B5-4692-B1D9-CE677D7BED7A@xxxxxxxxxxxxx>
<crBKQ4QXGHA.4620@xxxxxxxxxxxxxxxxxxxxx>
Subject: RE: trust between windows nt 4.0 and windows 2003 domain
Date: Wed, 12 Apr 2006 09:25:03 -0700
Lines: 119
Message-ID: <207B21F1-9721-4578-97C4-D6B5A10FB2CF@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.windows.server.migration
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:23290
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windows.server.migration

Thx Vince for the two links. I configured everything like described
there,
but it's still not working from the 2003-side (with the same message).
The NT-PDC didn't come up with any more error messages (the lmhosts file
+
lookup solved this one).

The only point where i'm not sure are the registry settings for NT in the
KB-article. It's recommended to check certain parameter values, but they
are
not set on my NT-PDC. Should I set them to a certain value (if yes,
which?),
or should it work already like this?

Is there anything else I could try?
Thx, Jaro


--
___________
Please reply to the group.
=========

Of all the things I've lost, I miss my mind the most. (Ozzy Osbourne)


"Vincent Xu [MSFT]" schrieb:

Hi Jaro,

Regarding troubshooting the problem in building trust between NT4 and
Windows Server 2003, I'd like to suggest you refer to following
articles:

Trust between a Windows NT domain and an Active Directory domain cannot
be
established or it does not work as expected
http://support.microsoft.com/default.aspx?scid=kb;EN-US;889030

http://71.214.150.200:443/windows/articles/firewall_trust.html

Hope helps

Best regards,

Vincent Xu
Microsoft Online Partner Support

======================================================
Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your newsreader
so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no
rights.
======================================================



--------------------
Thread-Topic: trust between windows nt 4.0 and windows 2003 domain
thread-index: AcZcszcYbJhDG36OSYO/1QeMp0xMBQ==
X-WBNR-Posting-Host: 195.62.26.120
From: =?Utf-8?B?SmFybyBTdGVyYmlrLUxhbWluYQ==?=
<JaroSterbikLamina@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: trust between windows nt 4.0 and windows 2003 domain
Date: Mon, 10 Apr 2006 08:27:02 -0700
Lines: 30
Message-ID: <7E038624-58B5-4692-B1D9-CE677D7BED7A@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.windows.server.migration
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:23256
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windows.server.migration

Hi all,

I'm trying to establish a trust relationship between our old Windows
NT
domain and our new Windows 2003 domain.
The theory is clear to me, the two servers (NT PDC and W2k3
PDC-emulator)
can ping each other, the netbios names can be resolved...

But when I try to setup the trust in Windows AD Domains and Trusts it
always
ends with the following error message:
"The Local Security Authority is unable to obtain an RPC connection
to
the
domain controller [SERVER-A]. Please check that the name is resolved
an
the
server is available."
Where [SERVER-A] is the correct name of the NT-PDC. So I guess it
can't
be a
problem with resolving the names. Both servers are up and running,
and
can be
accessed via the network; no firewalls between them (W2k3 firewall
also
inactive).

Any ideas what I might have missed/forgotten, or where the problem
could
be?
Thx in advance!

Rgds, Jaro



--
___________
Please reply to the group.
=========

Of all the things I''ve lost, I miss my mind the most. (Ozzy Osbourne)





.

Relevant Pages

  • RE: trust between windows nt 4.0 and windows 2003 domain
    ... we can try to create a one way trust via netdom trust, ... Microsoft Online Partner Support ... To create a correctly formatted Lmhosts file, ... C:\Windows ...
    (microsoft.public.windows.server.migration)
  • RE: Win2003 server cant browse NT Domain
    ... What is the relationship between your win2k3 machine and NT? ... DC and you are building trust to NT or win2k3 is a member server? ... How to Write an LMHOSTS File for Domain Validation and Other Name ... How To Establish Trusts with a Windows NT-Based Domain in Windows Server ...
    (microsoft.public.windows.server.migration)
  • Re: How to connect the NT4 PCD from windows 2003 server
    ... the NT domain and in the properties of the trust for incoming and outgoing ... I would also go into Domain Controller Security ... When you create lmhosts file make sure ... You can also use nbtstat -c on the Windows ...
    (microsoft.public.win2000.security)
  • Windows Update Help Needed.
    ... I have windows xp home. ... # This is a sample LMHOSTS file used by the Microsoft TCP/IP for Windows. ... Each entry should be kept on an individual line. ... # \0xnn notation to specify a hex value for a non-printing character. ...
    (microsoft.public.windowsupdate)
  • RE: trust between windows nt 4.0 and windows 2003 domain
    ... I think the domain controller for the NT domain is recognized by the Windows ... To create a correctly formatted Lmhosts file, ... and save it in the following folder: Microsoft Windows NT ... Trust between a Windows NT domain and an Active Directory domain cannot ...
    (microsoft.public.windows.server.migration)