Re: How to connect the NT4 PCD from windows 2003 server
From: Steven L Umbach (n9rou_at_nscomcast.net)
Date: 05/11/04
- Next message: Max: "Certificate Web Enrollment"
- Previous message: Ben: "Both MS Outlook and Outlook Express cannot communicate with email server"
- In reply to: Lillian: "How to connect the NT4 PCD from windows 2003 server"
- Next in thread: Lillian: "Re: How to connect the NT4 PCD from windows 2003 server"
- Reply: Lillian: "Re: How to connect the NT4 PCD from windows 2003 server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 11 May 2004 00:51:18 GMT
Hi again Lilian. I know you replied to me in an earlier post and I lost
track of it - sorry.
I would first use Windows 2003 AD Domain and Trusts to go to the trust with
the NT domain and in the properties of the trust for incoming and outgoing
try to validate the trusts to see if they still are enabled.
Microsoft recommends that you use SP6A on any NT4.0 computers involed in a
trust with a W2003 domain. I would also go into Domain Controller Security
Policy on the W2003 domain and in security settings/local policies/security
options disable the two options for digitally sign communications "always"
and make sure the two options for digitally sign communications if
client/server agrees are enabled at least until the problem is resolved.
Trusts between NT domain use netbios name resolution and therefore you need
to use lmhosts or wins for the domain controllers to find each other. If you
use wins, they need to be replication partners between domains and both
domain controllers need to be wins clients. However in you may want to try
an lmhosts file using the #PRE tag. When you create lmhosts file make sure
it is saved with no extension. You can also use nbtstat -c on the Windows
2003 domain controller where you create the lmhost file and you will see an
entry for the NT domain controller if you did it correctly. See the link
below on lmhosts file and note that the entries are case sensitive.
Nbtstat -R will clear and reload the netbios name cache after you create
your lmhosts file. --- Steve
http://support.microsoft.com/default.aspx?scid=kb;en-us;314108
Below is what you should see via nbtstat -c as an example if your lmhosts
file is done correctly with this entry " 10.0.0.1 PDCNAME #PRE
#DOM:MYDOMAIN1 "
:
Node IpAddress: [192.168.1.105] Scope Id: []
NetBIOS Remote Cache Name Table
Name Type Host Address Life [sec]
------------------------------------------------------------
PDCNAME <03> UNIQUE 10.0.0.1 -1
PDCNAME <00> UNIQUE 10.0.0.1 -1
PDCNAME <20> UNIQUE 10.0.0.1 -1
MYDOMAIN1 <1C> GROUP 10.0.0.1 -1
"Lillian" <anonymous@discussions.microsoft.com> wrote in message
news:b15d01c436e5$4455f070$a001280a@phx.gbl...
> I have NT4.0(PCD) is called glcdom, and NT2003server is
> call Training1, they are both trust each other, from the
> NT4 server User Manager for domain, select domain, I can
> see both glcdom and training1 domain, I can user account
> from training1\glc17, no problem, but from NT2003 server
> try to connect to glcdom ,it say " The following domain
> controller could not be contacted: glcdom. The RPC server
> is unavailable". any idea? I try to connect to domain
> controller from Active Directory Users and Computer,
> right click connect to Domain Controller. did I missing
> something?
>
> Lillian
- Next message: Max: "Certificate Web Enrollment"
- Previous message: Ben: "Both MS Outlook and Outlook Express cannot communicate with email server"
- In reply to: Lillian: "How to connect the NT4 PCD from windows 2003 server"
- Next in thread: Lillian: "Re: How to connect the NT4 PCD from windows 2003 server"
- Reply: Lillian: "Re: How to connect the NT4 PCD from windows 2003 server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
