Re: Problem With Joining XP Computer to Windows 2003 Domain

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Vinh Le (VinhLe_at_discussions.microsoft.com)
Date: 12/27/04 

Date: Sun, 26 Dec 2004 16:25:02 -0800

Hi Richard,

Thank you for your suggestions! I will give it and reply with the results.

Happy Holidays,
Vinh Le

"Richard G. Harper" wrote:

> I think you can solve most of your problems by doing two things:
>
> One, if the DC is connected directly to the Internet, DISCONNECT IT by
> placing a router or NAT firewall between you and the Internet. A DC should
> never ever be connected directly to the Internet.
>
> Two, if DNS is not running on the DC, you need to install and configure it,
> then have all clients looking ONLY at the DC DNS for name resolution. The
> DC should be using DNS forwarders to resolve all names outside your network.
>
> --
> Richard G. Harper [MVP Shell/User] rgharper@gmail.com
> * PLEASE post all messages and replies in the newsgroups
> * for the benefit of all. Private mail is usually not replied to.
> * My website, such as it is ... http://rgharper.mvps.org/
> * HELP us help YOU ... http://www.dts-l.org/goodpost.htm
>
>
> "Vinh Le" <VinhLe@discussions.microsoft.com> wrote in message
> news:306B7912-F95C-4BEB-BED0-AFF507B085F1@microsoft.com...
> > Hello Again! Happy Holidays Everyone,
> >
> > I am sure if this is the correct section to post this question in...if not
> > please point me the right way and I will repost. :-)
> >
> > I am working to build a home network for myself, and just got Windows 2003
> > Standard server loaded. I have assigned the server to Domain Controller
> > roll
> > and has Active Directory setup. I statically assigned the server to
> > static
> > IP address 192.168.1.165, which is outside of the Linksys Router DHCP
> > address
> > assignment range between 192.168.1.100 to 192.168.1.150
> >
> > I have also created my user name account in Active Directory Users and
> > Computers so that I can aunthenticate my login. So far I have only join
> > my
> > laptop to this domain and is testing out networking functionallity and ran
> > into this problem.
> >
> > The problem is that after joining my XP Pro SP2 laptop to the
> > home.thehood.com domain, I can not successfully complete the logon to the
> > new
> > domain. Further investigation, I notice a few errors and information that
> > seem to be pointing to DHCP scope possibly on the server's configuration
> > end.
> > The logon attempt just sit at the windows "configuring computer
> > environment". On the laptop I notice the following error in the Event
> > Logs
> >
> > The DHCP allocator has disabled itself on IP address 192.168.1.101, since
> > the IP address is outside the 192.168.0.0/255.255.255.0 scope from which
> > addresses are being allocated to DHCP clients. To enable the DHCP
> > allocator
> > on this IP address, please change the scope to include the IP address, or
> > change the IP address to fall within the scope.
> >
> > From the server when I try pinging the laptop computer name "MONKEY" I get
> > the following IP address replies: 216.138.240.196
> >
> >
> > I am clueless to which approach to start tourbleshooting the problem at
> > this
> > point. Hope that someone can point me the right direction. The technical
> > details are provided below.
> >
> > [Home Network]
> > SBC DSL
> > Linksys Router = BEFW11S4
> > Linksys Router = BEFSR41 (Daisy chain to the above router w/DCHP disabled)
> > (1) Compaq Deskpro EN = Windows 2003 Standard Server (DC)
> > (1) ThinkPad T20 Laptop = XP Pro SP2
> > (1) eMonster 600 PIII = XP Pro SP2
> > (1) PC P4 = XP Pro SP2
> > (1) Dell PIII = Linux RedHat 9
> >
> > [Active Directory]
> > Domain = home.thehood.com
> > Server TCP/IP = 192.168.1.165
> > Subnet Mask = 255.255.255.0
> > Default Gateway = 192.168.1.1 (Router's address)
> >
> >
> >
>
>
>

Relevant Pages

  • Re: Application Hang
    ... Do not run 2 DHCP servers together, that will create conflicts for the client. ... Under DNS management console is the server listed under Forward lookup zone, if yes with how many entries and which ones? ... I hope this is what you were looking for by way of scope options: ...
    (microsoft.public.windows.server.networking)
  • Re: SBS Reinstall
    ... In DHCP when I select the server it shows 192.168.16.2 and when I expand it ... "The wizard cannot set the DHCP scope options" error message when you run ... Ethernet adapter local area connection: ...
    (microsoft.public.windows.server.sbs)
  • Re: ...OS is Win 2003 Std...
    ... Microsoft Small Business Server Support ... >> The scope I have defined is identical to what you have listed, except for>> the range of the scope; ... but the message in the system error log>> indicates that it is not servicing clients because there is no NIC with a>> static IP assigned. ... >> The messages can be produced at will currently by simply restarting the> DHCP>> server service. ...
    (microsoft.public.windows.server.sbs)
  • Re: No DHCP Leases Available - SBS2K3
    ... delete scope 192.168.1.240 dhcpfullforce (command ... scope with two suggested options; stopped DHCP service; ran CEICW again - ... same message as above; started DHCP service; opened Change Server IP Address ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem With Joining XP Computer to Windows 2003 Domain
    ... One, if the DC is connected directly to the Internet, DISCONNECT IT by ... I have assigned the server to Domain Controller ... > seem to be pointing to DHCP scope possibly on the server's configuration ...
    (microsoft.public.windowsxp.network_web)