This is because Vista enables the DHCP Broadcast flag, which is *part of the specification for DHCP*. The ISP is using servers that don't support all recommended features of the spec. Look it up.
This is because Vista enables the DHCP Broadcast flag, which is *part of the specification for DHCP*.
In so much that the RFC states: "This addition to the protocol is a workaround for old host implementations. Such implementations SHOULD be modified so that they may receive unicast BOOTREPLY messages, thus making use of this workaround unnecessary. In general, the use of this mechanism is discouraged."
It's a deprecated feature in DHCP that Vista relies upon, Windows DHCP servers push, and alternative DHCP servers don't implement. The problem here is Microsoft standardizing on deprecated features.
Now that we've thrown 'em off the trail, use the form below to get in touch with the people at Engadget. Please fill in all of the required fields because they're required.
This is because Vista enables the DHCP Broadcast flag, which is *part of the specification for DHCP*. The ISP is using servers that don't support all recommended features of the spec. Look it up.
This is because Vista enables the DHCP Broadcast flag, which is *part of the specification for DHCP*.
In so much that the RFC states:
"This addition to the protocol is a workaround for old host
implementations. Such implementations SHOULD be modified so
that they may receive unicast BOOTREPLY messages, thus making
use of this workaround unnecessary. In general, the use of
this mechanism is discouraged."
It's a deprecated feature in DHCP that Vista relies upon, Windows DHCP servers push, and alternative DHCP servers don't implement. The problem here is Microsoft standardizing on deprecated features.