|
||||||||
|
|
#1
|
|
I have a newly promoted Windows 2003 domain controller that lives in a
single domain forest along with two older Windows 2000 DCs. Call the two Windows 2000 DCs Server1 and Server2. Call the newly promoted Windows 2003 Server Server3. Server3 cannot locate the domain using either of these command lines: dir \\mydomain.com\sysvol net view mydomain.com The identical two commands work perfectly both from Server1 and Server2, as well as from other Windows 2003 member servers in the domain. It looks like something in the DNS client for Server3 is broken. I know I have seen the problem and fixed it previously, but unfortunately I did not document the fix. I would appreciate any guidance on how to get the DNS client functionality working correctly on the newly promoted Server3. Note that DNS client settings for all three machines are currently pointing to Server1 and Server2. Note also that Server1 and Server2 can replicate Active Directory with Server3, but only when they initiate the conversation. It is the initiation from Server3 that seems to be failing. -- Will Will |
|
#2
|
|||
|
|||
|
Will ha scritto:
> I have a newly promoted Windows 2003 domain controller that lives in a > single domain forest along with two older Windows 2000 DCs. Call the two > Windows 2000 DCs Server1 and Server2. Call the newly promoted Windows 2003 > Server Server3. > > Server3 cannot locate the domain using either of these command lines: > > dir \\mydomain.com\sysvol > net view mydomain.com > > The identical two commands work perfectly both from Server1 and Server2, as > well as from other Windows 2003 member servers in the domain. It looks > like something in the DNS client for Server3 is broken. > > I know I have seen the problem and fixed it previously, but unfortunately I > did not document the fix. I would appreciate any guidance on how to get > the DNS client functionality working correctly on the newly promoted > Server3. > > Note that DNS client settings for all three machines are currently pointing > to Server1 and Server2. Note also that Server1 and Server2 can replicate > Active Directory with Server3, but only when they initiate the conversation. > It is the initiation from Server3 that seems to be failing. > Hi Will, what events/errors are registered in the server03 EW? A look at the events would really help. Cheer, Daniele -- ---------------- Daniele Catanesi MCT, MCSE, MCSA Please reply to the newsgroup so that all may benefit MSN : (E-Mail Removed) Blog : ehlomate.blogspot.com Blog : msexchangehell.blogspot.com (Italian) |
![]() |
| Tags |
| dir, fails, or domainnamecom |
| Thread Tools | |
| Display Modes | |
|
|