<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>RE: Vista keeps name server options from previous lease</title>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Where did you come up with this
workaround? <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Ben Wiechman</span></font><font
color=navy><span style='color:navy'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Wisper High Speed Internet</span></font><font
color=navy><span style='color:navy'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Office: 866.394.7737</span></font><font
color=navy><span style='color:navy'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Direct: 320.256.0184</span></font><font
color=navy><span style='color:navy'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Cell: 320.247.3224</span></font><font
color=navy><span style='color:navy'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>ben@wisper-wireless.com</span></font><o:p></o:p></p>
</div>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
dhcp-users-bounce@isc.org [mailto:dhcp-users-bounce@isc.org] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Randall C Grimshaw<br>
<b><span style='font-weight:bold'>Sent:</span></b> Saturday, September 15, 2007
9:09 AM<br>
<b><span style='font-weight:bold'>To:</span></b> dhcp-users@isc.org;
dhcp-users@isc.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: <st1:place w:st="on">Vista</st1:place>
keeps name server options from previous lease</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p style='margin-bottom:12.0pt'><font size=2 face="Times New Roman"><span
style='font-size:10.0pt'>see bottom<br>
<br>
-----Original Message-----<br>
From: dhcp-users-bounce@isc.org on behalf of Frank Sweetser<br>
Sent: Sat 9/15/2007 9:19 AM<br>
To: dhcp-users@isc.org<br>
Subject: Re: <st1:place w:st="on">Vista</st1:place> keeps name server options
from previous lease<br>
<br>
Kirsten Petersen wrote:<br>
>> What we are<br>
>> seeing with <st1:place w:st="on">Vista</st1:place> clients is this:
the client picks up a lease from the<br>
>> wireless network and gets the options for the main campus name
servers.<br>
>> Then, the user plugs into a wired port in the residence hall and gets
a<br>
>> new lease from the dhcp server on that network. However, their
name<br>
>> server option does not get updated. Thus, they don't get
redirected to<br>
>> the registration page, because they are talking to the wrong
nameservers.<br>
<br>
>This sounds like you're running into an issue that's been brought up a
couple<br>
>of times, so far with no resolution. If you search through the list
archives<br>
>for a thread with a subject of "dhcpinform request from <st1:place
w:st="on">Vista</st1:place> gets wrong Name<br>
>servers" you'll see all the details, but the short version is that the
dhcp<br>
>server uses a slightly different set of logic to calculate what options
should<br>
>be returned to DHCPINFORM requests than DHCPDISCOVER ones.<br>
<br>
-------------------------------------------------------------------------<br>
<br>
There is a workaround that works much of the time but not all. <st1:place
w:st="on">Vista</st1:place> always does a dhcpinform request but does not
always include the nameserver option in the request. It seems that the trigger
for including the nameserver option is a failure to resolve IPv6 tunnel
coordination server names. The workaround is to define the servers in your
captive DNS. It may not always be required that they are reachable. As an
aside, I was not amuzed to look up how destructive a teredo is.<br>
<br>
; these are the vista workarounds<br>
teredo.ipv6.microsoft.com.wherever.edu.
IN A
65.54.227.136<br>
teredo.ipv6.microsoft.com.wherever.edu.
IN A
65.54.227.138<br>
teredo.ipv6.microsoft.com.wherever.edu.
IN A
65.54.227.140<br>
teredo.ipv6.microsoft.com.wherever.edu.
IN A
65.54.227.142<br>
teredo.ipv6.microsoft.com.wherever.edu.
IN A
65.54.227.144<br>
teredo.ipv6.microsoft.com.
IN A
65.54.227.136<br>
teredo.ipv6.microsoft.com.
IN A
65.54.227.138<br>
teredo.ipv6.microsoft.com.
IN A
65.54.227.140<br>
teredo.ipv6.microsoft.com.
IN A
65.54.227.142<br>
teredo.ipv6.microsoft.com.
IN A
65.54.227.144<br>
6to4.ipv6.microsoft.com.wherever.edu.
IN A
192.88.99.1<br>
6to4.ipv6.microsoft.com.
IN A
192.88.99.1<br>
time.windows.com.wherever.edu.
IN A
207.46.130.100<br>
time.windows.com.
IN A
207.46.130.100<br>
dns.msftncsi.com.wherever.edu.
IN A
131.107.255.255<br>
dns.msftncsi.com.
IN A
131.107.255.255<br>
<br>
<><Randy</span></font><o:p></o:p></p>
</div>
</body>
</html>