DHCP Frustration

Hello ALL.

I am having a hell of a time getting a DHCP server (win2k3 server std.)
to assign IP addresses to clients. Here's the situation. We are
bringing up a new warehouse location that will need a server that can
assign IP to wireless devices. The network is a 192.168.x.x
255.255.255.0 subnet. I configured an additional Domain Controller at
our exising offices and then took it to the new warehouse and put it on
the network. I added a DNS server role with a new zone for this new
physical location. The problem is that no devices seem to be able to
get an ip address assignment from this server. I tried pc's, laptops
and handheld devices.

I have one DHCP server at our existing location and it works perfect.
It is 16 bit network 128.222.x.x 255.255.0.0. It was pretty easy to
setup from what i remember.

With the new DHCP server there are no errors in the event viewer for
the DHCPserver. The only thing is says is '..is now servicing
clients'.


Please help

are you running any other vlans?
--
dave love
Director of IT


"jblaze" wrote:

> Hello ALL.
>
> I am having a hell of a time getting a DHCP server (win2k3 server std.)
> to assign IP addresses to clients. Here's the situation. We are
> bringing up a new warehouse location that will need a server that can
> assign IP to wireless devices. The network is a 192.168.x.x
> 255.255.255.0 subnet. I configured an additional Domain Controller at
> our exising offices and then took it to the new warehouse and put it on
> the network. I added a DNS server role with a new zone for this new
> physical location. The problem is that no devices seem to be able to
> get an ip address assignment from this server. I tried pc's, laptops
> and handheld devices.
>
> I have one DHCP server at our existing location and it works perfect.
> It is 16 bit network 128.222.x.x 255.255.0.0. It was pretty easy to
> setup from what i remember.
>
> With the new DHCP server there are no errors in the event viewer for
> the DHCPserver. The only thing is says is '..is now servicing
> clients'.
>
>
> Please help
>
>

I know this is simple and I am sure you already did it...has it been
authorized?



"jblaze" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> Hello ALL.
>
> I am having a hell of a time getting a DHCP server (win2k3 server std.)
> to assign IP addresses to clients. Here's the situation. We are
> bringing up a new warehouse location that will need a server that can
> assign IP to wireless devices. The network is a 192.168.x.x
> 255.255.255.0 subnet. I configured an additional Domain Controller at
> our exising offices and then took it to the new warehouse and put it on
> the network. I added a DNS server role with a new zone for this new
> physical location. The problem is that no devices seem to be able to
> get an ip address assignment from this server. I tried pc's, laptops
> and handheld devices.
>
> I have one DHCP server at our existing location and it works perfect.
> It is 16 bit network 128.222.x.x 255.255.0.0. It was pretty easy to
> setup from what i remember.
>
> With the new DHCP server there are no errors in the event viewer for
> the DHCPserver. The only thing is says is '..is now servicing
> clients'.
>
>
> Please help
>

No i'm not running any vlans. I have the dhcp server on the network
linked by fibre to other fibre drop locations throughout the warehouse.
The server is connected to a dell powerconnect 5324 switch that i have
plugged a laptop into and attempted to acquire an address. This did not
work.

I have configured a firewall to act as a dhcp server,(and this works)
but would eventually like to use the windows server to handle these
requests.

I'm at a loss. Help....please

Not sure we are on the same page.
If this DHCP server is a Windows 2000/2003 Server, participating in an
Active Directory domain, the DHCP server needs to be "authorized" to handout
addresses. This is to prevent rogue DHCP servers.
A memeber of Enterprise Admins has to do this. Here is a link to follow.
http://www.microsoft.com/technet/pro...eaa37a1e9.mspx

Hope this helps

Ryan



"JBLaze" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> No i'm not running any vlans. I have the dhcp server on the network
> linked by fibre to other fibre drop locations throughout the warehouse.
> The server is connected to a dell powerconnect 5324 switch that i have
> plugged a laptop into and attempted to acquire an address. This did not
> work.
>
> I have configured a firewall to act as a dhcp server,(and this works)
> but would eventually like to use the windows server to handle these
> requests.
>
> I'm at a loss. Help....please
>

> Active Directory domain, the DHCP server needs to be "authorized" to handout
> addresses. This is to prevent rogue DHCP servers.

The server in question is authorized and activated yet none of the
clients can get addresses.

I don't know what else to do....

Well, if this is all one subnet,...with no LAN Routers between the Clients
and the DHCP then:
1. It should work
2. Your DC is meaningless and not even related to this at all. Clients
don't get addresses from DNS Servers. It wouldn't have made any difference
if you built a new DC with DNS or not,...it is just not relevant.

So,....since it should work, but it doesn't,..there must be a lot more to
this that you aren't telling us.

What "firewall" is configured to give DHCP? Where is it? You can't enable it
to do DHCP because it becomes a "rouge" DHCP Server on the LAN that will
clash with the exisitng DHCP,....unless you have more than one subnet and
the problem clients are all on one subnet (along with the firewall) and the
real DHCP is on a different subnet,...in which case you should have made
that clear because DHCP is broadcast based and will not cross subnets by
itself.

There just has got to be more to this than you have described.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"JBLaze" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
>
> > Active Directory domain, the DHCP server needs to be "authorized" to
handout
> > addresses. This is to prevent rogue DHCP servers.
>
> The server in question is authorized and activated yet none of the
> clients can get addresses.
>
> I don't know what else to do....
>