Problem With Joining XP Computer to Windows 2003 Domain

[Guest]

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)

 

[Richard G. Harper]

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] (e-mail address removed)
* 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

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)

 

[Guest]

Hi Richard,

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

Happy Holidays,
Vinh Le

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] (e-mail address removed)
* 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

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)

 

[Richard G. Harper]

Excellent, we'll be waiting to hear what happens.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* 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

Hi Richard,

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

Happy Holidays,
Vinh Le

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] (e-mail address removed)
* 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

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)

 

[Guest]

Hello Richard, Everyone!!!

Hope you all had a great XMAS and New Year celebrations.

Update on my problem joining the 2003 Active Directory Domain from my
Windows XP Pro laptop.

1.
Following Richard Harper suggestions, I verified that DNS services is
enabled. I then follow step-by-step instructions in my Windows 2000 Server
book to create a Forwared and Reversed lookup zones. I also create a Local
Host for the Linksys Router address.

2.
On the laptop side, I inputted the DNS Server IP address into the laptop's
LAN TCP/IP properties.

3.
I also performed command IPCONFIG /FLUSHDNS

After doing the above three steps, I was able to login to the domain ok and
TCP/IP assignments are normal as expected.

Thanks again for all your help Richard!!!
Vinh Le

Excellent, we'll be waiting to hear what happens.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* 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

Hi Richard,

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

Happy Holidays,
Vinh Le

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] (e-mail address removed)
* 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


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)

 

[Richard G. Harper]

I'm glad to hear that it all worked out well.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* 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

Hello Richard, Everyone!!!

Hope you all had a great XMAS and New Year celebrations.

Update on my problem joining the 2003 Active Directory Domain from my
Windows XP Pro laptop.

1.
Following Richard Harper suggestions, I verified that DNS services is
enabled. I then follow step-by-step instructions in my Windows 2000
Server
book to create a Forwared and Reversed lookup zones. I also create a
Local
Host for the Linksys Router address.

2.
On the laptop side, I inputted the DNS Server IP address into the laptop's
LAN TCP/IP properties.

3.
I also performed command IPCONFIG /FLUSHDNS

After doing the above three steps, I was able to login to the domain ok
and
TCP/IP assignments are normal as expected.

Thanks again for all your help Richard!!!
Vinh Le

Excellent, we'll be waiting to hear what happens.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* 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

Hi Richard,

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

Happy Holidays,
Vinh Le

:

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] (e-mail address removed)
* 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


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)