Re: DHCP Option 119

From: MarkAtwood <MarkAtwood.1qlvwz@xxxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 13 Jun 2005 21:58:19 -0500

Tanu Mutreja [MSFT] wrote:
> Hi Micheal,
> Currently we don't have plans to support this.
> Thanks and regards[/QUOITE]
>
>
> Well then, could you please fix
> http://support.microsoft.com/?id=275553
>
> It is telling a lie, saying "You cannot configure DHCP to send out a
> domain suffix search list. This is a limitation of the DHCP protocol
> itself and not the result of limitations in any particular vendor's
> DHCP implementation."
>
> This is a limitation of MICROSOFT's implementation. Everyone else
> got it right.

--
MarkAtwood
------------------------------------------------------------------------
Posted via http://www.webservertalk.com
------------------------------------------------------------------------
View this thread: http://www.webservertalk.com/message1039657.html

.

Follow-Ups:
- Re: DHCP Option 119
  - From: Tony

Prev by Date: TCP/IP Stack Improvements in Windows Server 2003 and Windows Server 2003 Service Pack 1
Next by Date: Re: Two accounts getting locked out
Previous by thread: TCP/IP Stack Improvements in Windows Server 2003 and Windows Server 2003 Service Pack 1
Next by thread: Re: DHCP Option 119
Index(es):
- Date
- Thread

Relevant Pages

Re: DHCP Option 119
... clients will ask for a valid dns server on their ... own after proper dhcp dns server inclusion and attach that suffix ... >> DHCP implementation." ... >> This is a limitation of MICROSOFT's implementation. ...
(microsoft.public.win2000.networking)
jumpstarting across networks
... DHCP has a reponse size limitation of 255 chars. ... copious paths required for a jumpstart, ... Sun basically refuses to address the inetboot netmask limitation, ...
(SunManagers)
Re: How do I setup static routing on Linksys
... Yeah, that would be true if the router was not using DHCP. ... static IPand still the limitation applies as to which ones can be ...
(comp.security.firewalls)