I am trying out Windows 2012 Direct Access!!
Without windows NLB IP-HTTPS inbound & manage out connections are working fine. However when I implement Windows NLB manage out connectivity stop working. Both NLB clusters are configured for affinity with single option.
My restrictive ISATAP router DNS record is pointing to NLB virtual IP. It is distributing ISATAP IPv6 and routes perfectly to manage out clients. With packet capture I can see my manage out traffic reaching internal virtual IP and after that no trace.
On remote client side I have enabled File and Printer Sharing (Echo Request - ICMPv6-In) firewall rule with allow edge traversal option and scope is open to any IP. And it is enabled on all profiles ;-). Still no luck. This config works fine without NLB. I have also enabled firewall logging at client side. No drops or accept packets are reported. So I assume they are getting dropped at NLB level.
Any clue what is going on?
Thanks,
Brajesh
Brajesh