Looks like I missed a rule about original posting. This is the fourth try, this time as a reply.
Pardon if this is a repeat, I’ve sent it twice before, once Wednesday and once Thursday and have yet to see it in the list. I know this is a long shot, but I have to ask. We set up MS Direct Access using MS UAG. So far it has worked pretty good, with one unintended side effect. When setting this up, the docs say to unblock the ISATAP dns entry and add the internal ISATAP IPv4 address in DNS. For some odd reason, several of our servers on the same subnet as the UAG server have 2002:… ipv6 address and have registered those ip addresses in our DNS server. I see that the 2002: prefix is on the tunnel adapter named ISATAP.domain.com The few workstations that are on the same subnet as the servers don't seem to be effected, but other workstations on other subnets are experiencing extremely long login times. 20 minutes or more in some cases. Also some machines are having problems connecting to our EX2010 server. Especially when they try to set the out of office function. I think the delay is due to the fact that there is no IPv6 router between the subnets and at this time, I have no desire to jump into that pond. Has anyone deployed Direct Access and seen this problem and solved it? I see lots of posts that say not to disable IPv6 on servers, but how do I prevent clients from using it and servers from registering those IPv6 addresses in DNS? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
