Networking Forums

Networking Forums > Computer Networking > Windows Networking > dir \\domainname.com fails

Reply
Thread Tools Display Modes

dir \\domainname.com fails

 
 
Will
Guest
Posts: n/a

 
      07-18-2007, 02:32 AM
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


 
Reply With Quote
 
 
 
 
Daniele Catanesi
Guest
Posts: n/a

 
      07-18-2007, 11:29 AM
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)
 
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
is .local in the domainname neccessary? Domé Windows Networking 7 09-14-2008 02:35 PM
domainname = none ToddAndMargo@gbis.com Linux Networking 1 09-05-2006 10:13 PM
Registered a domainname - will i be sued now? zucker Wireless Internet 8 04-11-2005 05:27 AM
Configuring hostname, domainname, and IP address linuxquestion@yahoo.com Linux Networking 38 01-10-2004 12:54 AM
Getting RH9 to remember NIS domainname after reboot Linux Networking 6 09-30-2003 08:33 AM



1 2 3 4 5 6 7 8 9 10 11