Networking Forums

Networking Forums > Computer Networking > Windows Networking > Server 2003 DHCP not serving addresses

Reply
Thread Tools Display Modes

Server 2003 DHCP not serving addresses

 
 
Rich M
Guest
Posts: n/a

 
      09-05-2006, 09:34 PM
My issue is that I have a 2003 server that has DHCP server on it and and is
supposed to be serving a 192.168.10.X addresses but it does not.
The server has been set up in its own domain on an existing network with a
192.168.1.X network and different domain.
I cannot get the clients to accept addresses from the new server at all. I
have also done the following.

Rebuilt server
Re-installed DHCP
De Authorized and Re-Authorized server
De Authorized Server in other domain on network
Tried different hardware altogether

The current DHCP server setup has issues that were existing previous to
my being here. The clients sometimes have to reboot the workstations if they
dont know how to do a relase/renew or repair on their NIC. I am attemping to
build a parallel network and mgrate all users to it but I cant do that
without getting dhcp working on the new server.

Any help would be greatly appreciated!

Regards,

Rich

(E-Mail Removed)

 
Reply With Quote
 
 
 
 
TimeTraveller
Guest
Posts: n/a

 
      09-06-2006, 12:57 AM
See my post and the answer to it on Sept 02 in this newsgroup, about 2
screens down titled
"DHCP won't handout addresses on new scope"..Might the same problem I was
having.

TimeTraveller


"Rich M" <Rich (E-Mail Removed)> wrote in message
news:B38E116A-51DC-432E-8F76-(E-Mail Removed)...
> My issue is that I have a 2003 server that has DHCP server on it and and
> is
> supposed to be serving a 192.168.10.X addresses but it does not.
> The server has been set up in its own domain on an existing network with a
> 192.168.1.X network and different domain.
> I cannot get the clients to accept addresses from the new server at all. I
> have also done the following.
>
> Rebuilt server
> Re-installed DHCP
> De Authorized and Re-Authorized server
> De Authorized Server in other domain on network
> Tried different hardware altogether
>
> The current DHCP server setup has issues that were existing previous to
> my being here. The clients sometimes have to reboot the workstations if
> they
> dont know how to do a relase/renew or repair on their NIC. I am attemping
> to
> build a parallel network and mgrate all users to it but I cant do that
> without getting dhcp working on the new server.
>
> Any help would be greatly appreciated!
>
> Regards,
>
> Rich
>
> (E-Mail Removed)
>



 
Reply With Quote
 
Rich M
Guest
Posts: n/a

 
      09-06-2006, 03:21 PM
I dont think that is it because I have my cisco 5500 as well as the router
setup with the correct DFG.

The internal networks consist of some of which are offsite locations
192.168.1.X
192.168.2.X offsite
192.168.3.X offsite
192.168.4.X offsite
192.168.5.X offsite
192.168.10.X
192.168.11.X
192.168.12.X offsite other side of wifi bridge
192.168.13.X offsite other side of wifi bridge
192.168.14.X offsite other side of wifi bridge

The remote sites work fine, the site on the opposite side of the bridge
will also not serve addresses. It is supported by the main buildings DHCP
server. I can turn on DHCP via the Cisco router but would like to keep it on
the server so I have dynamic dns entries being made. I am beginning to think
it has some to do with AD thinking that the server is a rogue DHCP server on
the network. Not sure though. I will ethereal the interface and see if
requests are being replied to. ?????

Rich

"TimeTraveller" wrote:

> See my post and the answer to it on Sept 02 in this newsgroup, about 2
> screens down titled
> "DHCP won't handout addresses on new scope"..Might the same problem I was
> having.
>
> TimeTraveller
>
>
> "Rich M" <Rich (E-Mail Removed)> wrote in message
> news:B38E116A-51DC-432E-8F76-(E-Mail Removed)...
> > My issue is that I have a 2003 server that has DHCP server on it and and
> > is
> > supposed to be serving a 192.168.10.X addresses but it does not.
> > The server has been set up in its own domain on an existing network with a
> > 192.168.1.X network and different domain.
> > I cannot get the clients to accept addresses from the new server at all. I
> > have also done the following.
> >
> > Rebuilt server
> > Re-installed DHCP
> > De Authorized and Re-Authorized server
> > De Authorized Server in other domain on network
> > Tried different hardware altogether
> >
> > The current DHCP server setup has issues that were existing previous to
> > my being here. The clients sometimes have to reboot the workstations if
> > they
> > dont know how to do a relase/renew or repair on their NIC. I am attemping
> > to
> > build a parallel network and mgrate all users to it but I cant do that
> > without getting dhcp working on the new server.
> >
> > Any help would be greatly appreciated!
> >
> > Regards,
> >
> > Rich
> >
> > (E-Mail Removed)
> >

>
>
>

 
Reply With Quote
 
Phillip Windell
Guest
Posts: n/a

 
      09-06-2006, 05:12 PM
These are all the same subnet. The Router has nothing to do with any of
this. A wired Bridge (a Layer2 device) would also have nothing to do with
it,...but since this is a wireless Bridge that uses additional security due
to the fact that it is wireless, that secureity stuff may be getting in the
way.

DHCP is totally passive,...it does not contact the clients. It is the
Clients that always contact it,...and they do so via broadcasting which
should work unrestricted since this is all a single IP Segment (geography
means nothing). So you may have to run NetMonitor or other sniffer on the
DHCP box and see if it is actually receiving the DHCP Query broadcasts from
the "troublesome" clients.

Also keep in mind that just because you use DHCP doesn't mean that
everything has to use it. Typically hosts that are over a WAN Link may run
static addresses (IP# range listed in "Exclutions" in the Scope) so that the
machines will continue to "stay alive" even if the WAN Link goes down for a
period of time.

For similar reasons there is usually a DC at each physical location as well.
The AD Sites object is used to control AD Replication over the slow WAN
Link. The Sites Object requires that each physical Site have a unique
Subnet with Layer3 Routers between the Sites instead of using Bridges. But
the idea is that the local DC keeps things running at the Site even if the
WAN Link goes down. The DC typically also runs DHCP for that particular
Site & IP Segment, so the Hosts get their IP Config locally at their Site.

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



"Rich M" <(E-Mail Removed)> wrote in message
news:1BEE15B4-2A58-450E-9871-(E-Mail Removed)...
>I dont think that is it because I have my cisco 5500 as well as the router
> setup with the correct DFG.
>
> The internal networks consist of some of which are offsite locations
> 192.168.1.X
> 192.168.2.X offsite
> 192.168.3.X offsite
> 192.168.4.X offsite
> 192.168.5.X offsite
> 192.168.10.X
> 192.168.11.X
> 192.168.12.X offsite other side of wifi bridge
> 192.168.13.X offsite other side of wifi bridge
> 192.168.14.X offsite other side of wifi bridge
>
> The remote sites work fine, the site on the opposite side of the bridge
> will also not serve addresses. It is supported by the main buildings DHCP
> server. I can turn on DHCP via the Cisco router but would like to keep it
> on
> the server so I have dynamic dns entries being made. I am beginning to
> think
> it has some to do with AD thinking that the server is a rogue DHCP server
> on
> the network. Not sure though. I will ethereal the interface and see if
> requests are being replied to. ?????
>
> Rich
>
> "TimeTraveller" wrote:
>
>> See my post and the answer to it on Sept 02 in this newsgroup, about 2
>> screens down titled
>> "DHCP won't handout addresses on new scope"..Might the same problem I was
>> having.
>>
>> TimeTraveller
>>
>>
>> "Rich M" <Rich (E-Mail Removed)> wrote in message
>> news:B38E116A-51DC-432E-8F76-(E-Mail Removed)...
>> > My issue is that I have a 2003 server that has DHCP server on it and
>> > and
>> > is
>> > supposed to be serving a 192.168.10.X addresses but it does not.
>> > The server has been set up in its own domain on an existing network
>> > with a
>> > 192.168.1.X network and different domain.
>> > I cannot get the clients to accept addresses from the new server at
>> > all. I
>> > have also done the following.
>> >
>> > Rebuilt server
>> > Re-installed DHCP
>> > De Authorized and Re-Authorized server
>> > De Authorized Server in other domain on network
>> > Tried different hardware altogether
>> >
>> > The current DHCP server setup has issues that were existing previous to
>> > my being here. The clients sometimes have to reboot the workstations if
>> > they
>> > dont know how to do a relase/renew or repair on their NIC. I am
>> > attemping
>> > to
>> > build a parallel network and mgrate all users to it but I cant do that
>> > without getting dhcp working on the new server.
>> >
>> > Any help would be greatly appreciated!
>> >
>> > Regards,
>> >
>> > Rich
>> >
>> > (E-Mail Removed)
>> >

>>
>>
>>



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Windows 2003 server serving up "wrong" MAC to arp clients? Rob G Windows Networking 4 09-17-2009 08:51 PM
Server 2003 obtaining multiple multiple IP addresses via DHCP pbrommer@gmail.com Windows Networking 1 03-29-2007 02:24 AM
DHCP Server Leasing Addresses to MAC Addresses of 00-00-00-00-00-00 nomorespameventhoughthejapanesespamgivesmeachuckle Linux Networking 9 12-05-2006 09:49 PM
2003 server in 2000 domain serving only read-only Tim Windows Networking 2 07-14-2004 11:06 PM
Static Versus Dynamic(DHCP) IP addresses on Windows 2000/2003 Servers Frank Wijten Windows Networking 9 05-27-2004 09:31 PM



1 2 3 4 5 6 7 8 9 10 11