[THIN] Re: DHCP Question for Windows 2003 Server

  • From: "Roy A. Tokeshi" <roy@xxxxxxxxxxx>
  • To: thin@xxxxxxxxxxxxx
  • Date: Wed, 07 Apr 2004 01:39:25 -0400

I have been trying to piece this one together from all of the replies.

Have you tried to establish a superscope?  This will allow a single DHCP 
server to sevice two scopes according to:

There was a mention of reducing the lease time.  The problem is that by 
default the DHCP server doesn't delete after the lease expires until the 
grace period.
This grace is 4 hours.  If there is an issue with granting leases, it 
will initiate a  cleanup.  This cleanup will occur by default every 60 
minutes.  Still you will need to modify the grace period.



Rusty Yates said the following on 4/6/2004 4:37 PM:
> I'm having this issue w/ everything from XP Pro to Thin Clients that are
> running Win CE. 
> -----Original Message-----
> From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
> Of Chris Lynch
> Sent: Tuesday, April 06, 2004 3:31 PM
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Re: DHCP Question for Windows 2003 Server
> This is for non-Windows 2000 clients.  Windows 2000 and greater client will
> be able to modify their DNS records.  This group allows the DHCP server to
> update WINS and DNS (if configured to) automatically on half of the client
> that cannot do this.
> Chris 
> -----Original Message-----
> From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
> Of Paul Bergson (MP)
> Sent: Tuesday, April 06, 2004 1:23 PM
> To: 'thin@xxxxxxxxxxxxx'
> Subject: [THIN] Re: DHCP Question for Windows 2003 Server
> I have been studying for my upgrade on 2003 and there was some talk about a
> new group that the dhcp service account has to belong to when updating the
> DNS record for clients that can't do the update themselves.  If not included
> in this group then the user won't have the ability to expire the dns record.
> So not sure if this is related but it is a shot.  The group name was
> something like dhcpproxyupdate.
> Hope this helps.
> Thanks
> Paul
> -----Original Message-----
> From: Rusty Yates [mailto:ryates@xxxxxxxxxxxxxxxxxx]
> Sent: Tuesday, April 06, 2004 3:04 PM
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] DHCP Question for Windows 2003 Server
> Importance: High
> I've posted this before but I wanted to try one more time.  Currently we are
> running into an issue with our DHCP Server (Windows 2003 Enterprise. Server)
> that will not issue an IP address to any thin client, laptop, or pc if it
> already has a lease on another scope.  You can do the release and renew
> thing all day long but the DHCP server will not assign an IP until the lease
> for the PC is deleted from the scope that it last got an IP address from.
> I've never seen this problem before until I started working on this server.
> Is this new in Windows 2003 Server?  It sounds like a security setting or
> something.  
This Week's Sponsor - RTO Software / TScale
What's keeping you from getting more from your terminal servers? Did you
know, in most cases, CPU Utilization IS NOT the single biggest
constraint to scaling up?! Get this free white paper to understand the
real constraints & how to overcome them. SAVE MONEY by scaling-up rather
than buying more servers.
Useful Thin Client Computing Links are available at:
For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link:

Other related posts: