Re: Unable to join my new XP pro wkstation to the Win 2K pro server domain.
From: Sydney Lotterby (sydney_at_infosearch.com)
Date: 03/24/04
- Next message: Marcus K.: "W2K Native domain with NT4 domain"
- Previous message: Jens-Peter Vraa Jensen: "Re: Recommended NIC for Windows 2003"
- In reply to: Herb Martin: "Re: Unable to join my new XP pro wkstation to the Win 2K pro server domain."
- Next in thread: Herb Martin: "Re: Unable to join my new XP pro wkstation to the Win 2K pro server domain."
- Reply: Herb Martin: "Re: Unable to join my new XP pro wkstation to the Win 2K pro server domain."
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 24 Mar 2004 13:37:58 -0600
Herb,
Thanks for the tips.
I am a AD neophyte so have some further questions.
1) Where and how do I setup Dynamic DNS? My server domain is TCAdomain and
internet is www.infosearch.com
I am offsite presently but I believe I setup the server with TCAdomain
and infosearch.com and didn't have a choice.
What should I have done?
2) How can I correct the situation now (step by step please or point me to
an article)?
3) What can I read to get smart on AD?
tia
"Herb Martin" <news@LearnQuick.com> wrote in message
news:eIOTm0cEEHA.684@tk2msftngp13.phx.gbl...
> "Sydney Lotterby" <sydney@infosearch.com> wrote in message
> news:udziOocEEHA.240@tk2msftngp13.phx.gbl...
> > I am unable to join my new XP pro wkstation to the Win 2K pro server
> domain.
> > I get this message:
>
> Almost always a DNS issue IF the network is functional.
> (IP, cable, NIC which you say are fine.)
>
> > Help - spent way too much time on this already.
> > NIC and cable are OK b/c I can get to the internet.
>
> This is quite common if you configure the workstation to use
> a DNS server on the Internet -- any DNS other than the INTERNAL
> DYNAMIC DNS used to support AD.
>
> AD requires Dynamic DNS for the zone which corresponds to your domain.
>
> All clients -- which includes DCs, DNS servers etc - must be configured
> to use ONLY the internal DNS server (set).
>
> If the real clients are configured otherwise, you will not find the
domain.
> If the "servers" are configured otherwise, they will NOT register and no
> one can find them.
> If you try to use both internal and external, it may work sporadically but
> you will not have a reliable and consistent solution.
>
> > Also, after logging in as local machine account, I can connect to the
> server
> > via My Network places then use server admin pwd to get access to server
> > drives.
>
> Probably resolving via NetBIOS -- browsing is a NetBIOS
> application.
>
> > I have tried creating the computer name and user names manually on the
> > server via Active Users and Computers, set admin rights to all of them.
> > Tried deleting them and letting the wizard create them. I get the same
> > result no matter what.
>
> Stop that. Do it once correctly and then don't flail about.
>
>
> --
> Herb Martin
> >
> >
> >
> >
>
>
- Next message: Marcus K.: "W2K Native domain with NT4 domain"
- Previous message: Jens-Peter Vraa Jensen: "Re: Recommended NIC for Windows 2003"
- In reply to: Herb Martin: "Re: Unable to join my new XP pro wkstation to the Win 2K pro server domain."
- Next in thread: Herb Martin: "Re: Unable to join my new XP pro wkstation to the Win 2K pro server domain."
- Reply: Herb Martin: "Re: Unable to join my new XP pro wkstation to the Win 2K pro server domain."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|