Help with DHCP basics

I have been needing to gain exposure to win2003 server and AD and so I'm
attempting to config it for my SOHO network. I've run the AD wizard and
followed the settings outlined in a book (Mastering by Minasi). After a
day or two of that I decided to simplify and I have the win2003 server
connected to a single work station via a hub, and not linked at all to
the internet or sw or any other part of the lan. So there is no chance
of there being two dhcp servers in play.

The DHCP service is running and authorized; so are the scopes (I now
have two scopes set up, 192.168.0.10-254 and 10.0.0.10-200 only because
the first scope didn't seem to 'work').

The problem is that Win2003 standard does not seem to be acting as a
DHCP server. Workstation come up with 169.xxx.xxx.xxx ip addresses. None
can therefore even ping the win2003 server (192.168.0.10).

I've tried every ipconfig command to see if I could get the workstation
to pay heed to the server. But nothing. It's such a basic failure,
according to my notion, the workstation should 'wake up', look around
for a dhcp server, and finding one, get an ip address from it.

Workstation is WinXP sp2; set to auto obtain IP address etc. Both are
connected to a simple hub. As an experiment I assigned a static ip to
the workstation and then the server and the ws could see each other. So
there is no physical problem with the network.

When I run ipconfig /release, ip is set to 0.0.0.0. If I run ipconfig
/renew on the ws, it pauses for at least a minute and then says
connection timed out, no dhcp server was found.

On the server side, it's configured per the AD wizard, dealing with
range 192.168.0.10 - .254, exclusion for 192.186.0.10 (the server).

What other information would be useful? Why doesn't this server act as a
dhcp server?

Hi,

Have you checked the eventlogs on both machines?

Have you tried the steps listed here
http://technet2.microsoft.com/Window...5893f1033.mspx

This might also be helpful
http://www.microsoft.com/windowsserv...fault.mspx#EPC

Cheers

Gareth Brown | Consultant | 1E Ltd

http://www.1e.com


"network_out" <none.none.none> wrote in message
news:(E-Mail Removed) m...
>I have been needing to gain exposure to win2003 server and AD and so I'm
> attempting to config it for my SOHO network. I've run the AD wizard and
> followed the settings outlined in a book (Mastering by Minasi). After a
> day or two of that I decided to simplify and I have the win2003 server
> connected to a single work station via a hub, and not linked at all to
> the internet or sw or any other part of the lan. So there is no chance
> of there being two dhcp servers in play.
>
> The DHCP service is running and authorized; so are the scopes (I now
> have two scopes set up, 192.168.0.10-254 and 10.0.0.10-200 only because
> the first scope didn't seem to 'work').
>
> The problem is that Win2003 standard does not seem to be acting as a
> DHCP server. Workstation come up with 169.xxx.xxx.xxx ip addresses. None
> can therefore even ping the win2003 server (192.168.0.10).
>
> I've tried every ipconfig command to see if I could get the workstation
> to pay heed to the server. But nothing. It's such a basic failure,
> according to my notion, the workstation should 'wake up', look around
> for a dhcp server, and finding one, get an ip address from it.
>
> Workstation is WinXP sp2; set to auto obtain IP address etc. Both are
> connected to a simple hub. As an experiment I assigned a static ip to
> the workstation and then the server and the ws could see each other. So
> there is no physical problem with the network.
>
> When I run ipconfig /release, ip is set to 0.0.0.0. If I run ipconfig
> /renew on the ws, it pauses for at least a minute and then says
> connection timed out, no dhcp server was found.
>
> On the server side, it's configured per the AD wizard, dealing with
> range 192.168.0.10 - .254, exclusion for 192.186.0.10 (the server).
>
> What other information would be useful? Why doesn't this server act as a
> dhcp server?