Re: Unable to join my new XP pro wkstation to the Win 2K pro server domain.

From: Herb Martin (news_at_LearnQuick.com)
Date: 03/24/04 

Date: Wed, 24 Mar 2004 15:17:38 -0600

"Sydney Lotterby" <sydney@infosearch.com> wrote in message
news:OTKEQedEEHA.3064@tk2msftngp13.phx.gbl...
> 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

This is not usually relevant unless you use the same Domain/Zone name
internally.

What is your AD Win2000+ Domain name?

> 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?

You must have an internal DNS zone for each AD domain that is
maintained separately from the Internet versions of these zone (if
you were to use the same name both publicly and privately.)

You need an INTERNAL DNS server (set) for the zones.

> 2) How can I correct the situation now (step by step please or point me
to
> an article)?

I don't yet know what precisely you have done so it would be
silly to ask you to read hundreds of pages when you might have
a simple problem or when we might be able to point you to a short
refernce.

Do you have a DNS server internally? What is you AD domain name?
Do you have a corresponding Zone in that INTERNAL DNS that uses
this same name? IS it dynamic?

Are all of your internal machines configured on their NIC\IP properties
to use STRICTLY the internal dynamic DNS server set?

DCs and DNS servers are "DNS clients" too!!!

> 3) What can I read to get smart on AD?

The built-in help. Really. There are even "checklists" which can be
searched in Help. Search [ CHECKLIST DNS ] or [CHECKLIST active directory ]
etc. 

-- 
Herb Martin
> 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
> > >
> > >
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: Non-domain connection problem
    ... "Gregg Hill" wrote: ... You said that you "hard coded the DNS server to a known DNS on the ... Connect to Internet from external network ...
    (microsoft.public.windows.server.sbs)
  • Re: Added router, lost web site
    ... Did your ISP create a DNS record for your FQDN? ... > really have a direct connection. ... > Internet connection information: ... > Preferred DNS server: someisp DNS server address ...
    (microsoft.public.windows.server.sbs)
  • Re: Unix Bind and Windows DNS with Dynamic update issues!!!
    ... >suggest but it does NOT service internal clients directly. ... still have UNIX BIND to do the rest for host name and internet resolution. ... Windows 2003 DNS will acting as another internal DNS server like UNIX BIND? ...
    (microsoft.public.win2000.dns)
  • Re: Unix Bind and Windows DNS with Dynamic update issues!!!
    ... >> 2) All internal DNS clients NIC\IP properties must specify SOLELY ... >> we are running UNIX BIND as internal and external DNS server. ... > expose your sensitive internal information on the Internet. ... >> internal clients like Windows, Mac etc are pointing to UNIX BIND server to ...
    (microsoft.public.win2000.dns)
  • Re: DNS Deployment
    ... NS records map a zone to a DNS server name, ... > After the installation, I can see the subfolders, msdcs, sites, tcp, udp ... Herb Martin> ...
    (microsoft.public.windows.server.migration)