UAG error: “A timeout occurred. The 6to4 network interface cannot be enabled”
I was trying to configure DirectAccess on UAG in a test environment, and kept getting the above error whenever I tried to activate my configuration.
The solution is simple. UAG needs two consecutive public IP addresses assigned on the external network interface. In a test environment, you would sometimes use a private IP range like 10.0.0.0 or 192.168.0.0 for the external interface, which is not supported. Also note, the UAG DirectAccess server cannot be behind a NAT.
Change the IP address on the external interface to a public IP address, and the error will go away! 
Shijaz Abdulla is a Partner Technology Advisor at Microsoft, helping their top tier partners build on their Microsoft practice. He is also a trusted advisor to medium enterprise customers in Qatar. He is a blogger, tech enthusiast, and a Microsoft evangelist.
New blog post: http://tinyurl.com/yddtkhc – #UAG error: “A timeout occurred. The 6to4 network interface cannot be enabled”
Thanks a lot Shijaz!
I’m trying to deploy UAG DirectAccess in my work environment and was banging my head for this error message. I used 2 consecutive private IP NATed to a public IP and I was hoping that things would work. I kept getting the same error and reading your blog was sobering for me. During my research to set up UAG DirectAccess I read about the need for 2 consecutive public IPs on the external interface of the UAG but I thought that I could use NAT to handle things.
Once again, choukrane.
Ma ‘ salama!