Re: How to connect the NT4 PCD from windows 2003 server
From: Steven L Umbach (sumbach_at_N0spam.ameritech.net)
Date: 05/11/04
- Next message: jhahn: "set up security violation reports"
- Previous message: LaVerne Davis: "Sasser Worm Virus & WINDOWS 2000 file"
- In reply to: Lillian: "Re: 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 12:36:03 -0500
I see you have two IP addresses on your server - 128.97.213.11 and
192.168.1.100. Usually the 192.168.xxx.xxx range is used for internal
networking. If that is the case you may need to modify your lmhosts files to
reflect those addresses. Are the 128.97.213.xxx range used for internet
access or ipsec tunnel?? The network adapters used for internal networking
should also be at the top of the priority list such as shown in network
connections/advanced/advanced settings for Windows 2003. I am not sure about
your question with Exchange, but you probably could find an answer in one of
the Exchange newsgroups. The link below may also be helpful in
troubleshooting the RPC server is unavailable message. --- Steve
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224370
"Lillian" <anonymous@discussions.microsoft.com> wrote in message
news:b3f501c43778$801130f0$a401280a@phx.gbl...
> Steve:
>
> Here is what I change according yours:
>
> Digitally sign communications (always)....Disable
> Digitally sign communications (if server agrees)...Enable
> Digitally sign communications (always)....Disable
> Digitally sign communications (if client agrees)...Enable
> From NT2003 server, I did nbtstat -R, then nbtstat -c, it
> show as following...
>
> External:
> Node IPAddress: [128.97.213.11] Scope ID: []
> Netbios Remote Cache Name Table
> Name Type Node Address Life
> --------------------------------------------
> GLCDOM <03> UNIQUE 128.97.213.11 -1
> GLCDOM <00> UNIQUE 128.97.213.11 -1
> GLCDOM <20> UNIQUE 128.97.213.11 -1
>
> Internal:
> Node IP address: [192.168.1.100] Scope ID: []
> no Name in cache.
>
> From NT4 server, I type nbtstat -c
> NetBios Remote Cache Name Table
> ---------------------------------------------
> Name Type Node Address Life
> TRAINING1 <1C> Group 128.97.213.10 -1
> GLCTEST1 <03> UNIQUE 128.97.213.10 -1
> GLCTEST1 <00> UNIQUE 128.97.213.10 -1
> GLCTEST1 <20> UNIQUE 128.97.213.10 -1
>
> Then I go to active directory users and computers, right
> click on traing1.gov, select connect to domain controller,
> on the enter the name of another domain controller, I
> type in the box say" Any writable domain controller" I
> type glcdom, which is my NT4 domain controller name, it
> say " The following domain controller could not be
> contacted: glcdom. the RPC server is unavailable"
>
> The purpose of this NT2003 server and NT4 server, because
> NT4 server is exchange 5.5 server, the username "glc17"
> is on exchange server has mail box, now I login on the
> workstation connect to Training1 server, if I double
> click the outlook, I want the domain point to "Training1"
> server instead of "GLCDOM" server, is that possible, is
> windows 2003 server can work on exchange 5.5 server?
>
> Thanks for all the help.
>
> Lillian
> Thanks for all the help.
>
> Lillian
>
> >-----Original Message-----
> >It still sounds like the W2003 domain controller can not
> find the NT4.0
> >domain controller per your error message. Did you try
> the lmhosts file on
> >the W2003 domain controller and double check that the it
> is in the netbios
> >name cache via nbtstat -c ??Are there any pertinent
> messages in the Event
> >Viewer of either domain controller that may provide a
> clue? Did you try
> >disabling digitally sign communications "always"?? ---
> Steve
> >
> >
> >"Lillian" <anonymous@discussions.microsoft.com> wrote in
> message
> >news:b59b01c43764$3f819250$a001280a@phx.gbl...
> >> Steve:
> >>
> >> The two way trust is working now as I explain early
> >> that NT4 server I can see the Training1(NT2003server)
> and
> >> GLCDOM (NT4PDC) both domain, but how did you make the
> >> connection from NT2003 server to see the GLCDOM?
> >>
> >>
> >> Lillian
> >>
> >>
> >>
> >> >-----Original Message-----
> >> >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: jhahn: "set up security violation reports"
- Previous message: LaVerne Davis: "Sasser Worm Virus & WINDOWS 2000 file"
- In reply to: Lillian: "Re: 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
|
|
