<div dir="ltr"><div>Sounds good. I'll see what I can dig up tomorrow.<br><br></div>Kurt<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 20, 2015 at 10:47 AM, Brzozowski, John <span dir="ltr"><<a href="mailto:John_Brzozowski@cable.comcast.com" target="_blank">John_Brzozowski@cable.comcast.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto">
<div>I can help. Can you send details how to setup the scenario please? Not only do I have access, I also have a long list of co-workers that are are capable and willing.<br>
<br>
<span style="font-size:13pt">John</span>
<div><span style="font-size:13pt"><a href="tel:%2B1-484-962-0060" value="+14849620060" target="_blank">+1-484-962-0060</a></span></div>
</div><div><div class="h5">
<div><br>
On Dec 20, 2015, at 13:43, Kurt Buff <<a href="mailto:kurt.buff@gmail.com" target="_blank">kurt.buff@gmail.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">
<div>Thanks!<br>
<br>
</div>
<br>
I'll go back to my notes tomorrow in the ticketing system, and see if I can give more detail.<br>
<br>
Failing that, I'm going to see if I can recruit someone to help recreate the problem - I don't have Comcast myself.<br>
<br>
Kurt</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sat, Dec 19, 2015 at 6:49 PM, Brzozowski, John Jason <span dir="ltr">
<<a href="mailto:jjmb@jjmb.com" target="_blank">jjmb@jjmb.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I run the IPv6 program for Comcast. Let me know how I can help.
<div><br>
</div>
<div>Adding my work email so I don't miss these emails.</div>
<span><font color="#888888">
<div><br>
</div>
<div>John</div>
</font></span>
<div>
<div>
<div><br>
On Saturday, December 19, 2015, Kurt Buff <<a href="mailto:kurt.buff@gmail.com" target="_blank">kurt.buff@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
All,<br>
<br>
I ran into an interesting situation some months ago which still<br>
baffles me, and though I was able to work around it, I expect it will<br>
happen again.<br>
<br>
We implemented MSFT DirectAcess at our company quite some time ago<br>
(using 2008R2 and Forefront 2010), and it works extremely well.<br>
<br>
At least it worked well for everyone until one of the employees got<br>
his Comcast connection upgraded, and then DirectAccess didn't work for<br>
that employee any more.<br>
<br>
We proved that if he tethered to his cell phone, that would work, and<br>
if he used an SSL VPN client while on his Comcast connect that would<br>
work, but DirectAccess would not work at home.<br>
<br>
Finally, I discovered that his Comcast-installed router was handing<br>
our IPv6 addresses on his home LAN. Turning that off enabled<br>
DirectAccess to work again.<br>
<br>
We do not have an assigned IPv6 block from our ISP, though of course<br>
MSFT OSes use it, and auto-assign themselves addresses, but for now<br>
we're ignoring it.<br>
<br>
Has anyone run into this problem and solved it - not by turning off<br>
iIPv6 address assignment for the home LAN, but really solved it? If<br>
so, how did you do that?<br>
<br>
Would getting and implementing an IPv6 assignment from our ISP cure<br>
the problem, or make it worse?<br>
<br>
I've found little guidance from MSFT about DirectAccess in an IPv6<br>
environment, though I admit I haven't been terribly diligent in my<br>
searches.<br>
<br>
Kurt<br>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div></div></div>
</blockquote></div><br></div>