RayT
Guest
|
 Posted:
Wed Oct 19, 2005 8:51 pm Post subject:
Existing NT 4 BDC not communicating with new 2003 AD DC |
|
|
We have upgraded our existing NT 4 Domain to active directory domain and it
appears we are having some authentication/replication issues between the
existing BDC's and the new 2003 DC. We upgraded the NT PDC to Win 2003 and
created a clean Win 2003 DC, joined the domain and then migrated all the FSMO
roles to the new clean box, then demoted the old upgrated NT box. Post
upgrade on the existing NT BDC's we added the new DNS server to the TCP/IP
properties of the NIC and added the new suffix as well, aside from that we
did nothing else to the existing NT boxes.
Info:
One Domain nothing special
All BDC's are running NT 4.0 with SP6
The new DC is running Win 2003 w/ SP1
2 Event Errors on the Existing NT 4.0 machines
Event ID 5719 Source: NETLOGON
No Windows NT Domain Controller is available for domain newdomain. (This
event is expected and can be ignored when booting with the 'No Net' Hardware
Profile.) The following error occurred:
The RPC server is unavailable.
Event ID 3013 Source: rdr
The redirector has timed out a request to Win2003PDC-01
Problem:
It appears that we are having some Replication issues, newly created users
in the Win2003 AD cannot access recources on the NT 4.0 File Servers.
Questions
Where do you see/configure the replication of the AD to SAM?
All the existing Domain Controllers are in the AD in the Domain Controllers
Container, i see them no where else in AD should they be somewhere else like
in the AD Sites/Services in the Servers container?
Thanks... |
|
Vincent Xu [MSFT]
Guest
|
| Posted:
Thu Oct 20, 2005 8:51 am Post subject:
RE: Existing NT 4 BDC not communicating with new 2003 AD DC |
|
|
Hi,
This error can be a result of the TCP/IP Netbios Helper service being
disabled on the server or Netbios over TCP/IP being disabled on one of the
NIC's used to access the Terminal server. You should also verify that the
Client for Microsoft networks is bound to the adapter used to access the
server.
Please run Netdiag/v on the problematic box
B. The error can also be a result of a T server with multiple clients
already connected failing under load. You can edit the following registry
values
on the server from which the clients are requesting resources:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
Value name: MaxCmds
Data type: REG_DWORD
Radix: Decimal
Value data: 500
Value name: MaxWorkItems
Data type: REG_DWORD
Radix: Decimal
Value data: 8192
Value name: MaxMpxCt
Data type: REG_DWORD
Radix: Decimal
Value data: 500
Note: You may have to increase these values if the registry key does not
work.
More information about these values are available in 232476 - "Terminal
Server
Client Connections and Logon Limited by MaxWorkItem and" at
<http://support.microsoft.com/?id=232476>
Best regards,
Vincent Xu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
--------------------
| Quote: | Thread-Topic: Existing NT 4 BDC not communicating with new 2003 AD DC
thread-index: AcXU2rQrVgzJYZdMRJekgzKCCqA3aA==
X-WBNR-Posting-Host: 67.96.95.194
From: "=?Utf-8?B?UmF5VA==?=" <RayT@discussions.microsoft.com
Subject: Existing NT 4 BDC not communicating with new 2003 AD DC
Date: Wed, 19 Oct 2005 11:27:04 -0700
Lines: 36
Message-ID: <0CA63D53-9926-40E3-B57E-63C3A0542298@microsoft.com
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.0
Newsgroups: microsoft.public.windows.server.migration
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:12392
X-Tomcat-NG: microsoft.public.windows.server.migration
We have upgraded our existing NT 4 Domain to active directory domain and
it
appears we are having some authentication/replication issues between the
existing BDC's and the new 2003 DC. We upgraded the NT PDC to Win 2003
and
created a clean Win 2003 DC, joined the domain and then migrated all the
FSMO
roles to the new clean box, then demoted the old upgrated NT box. Post
upgrade on the existing NT BDC's we added the new DNS server to the
TCP/IP
properties of the NIC and added the new suffix as well, aside from that
we
did nothing else to the existing NT boxes.
Info:
One Domain nothing special
All BDC's are running NT 4.0 with SP6
The new DC is running Win 2003 w/ SP1
2 Event Errors on the Existing NT 4.0 machines
Event ID 5719 Source: NETLOGON
No Windows NT Domain Controller is available for domain newdomain. (This
event is expected and can be ignored when booting with the 'No Net'
Hardware
Profile.) The following error occurred:
The RPC server is unavailable.
Event ID 3013 Source: rdr
The redirector has timed out a request to Win2003PDC-01
Problem:
It appears that we are having some Replication issues, newly created
users
in the Win2003 AD cannot access recources on the NT 4.0 File Servers.
Questions
Where do you see/configure the replication of the AD to SAM?
All the existing Domain Controllers are in the AD in the Domain
Controllers
Container, i see them no where else in AD should they be somewhere else
like
in the AD Sites/Services in the Servers container?
Thanks...
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in