Server 2012 R2 DirectAccess Teredo server cannot be started

Hi all,

Our 2012 R2 DirectAccess server worked without any problems. Last week I enabled cluster configuration with external load balancing and added a second server to the cluster. As a consequence the two consecutive public IP addressed switched over to the load balancer and the first server got two new IPs. Works like described in TechNet and still everything was fine.

For some internal reasons I had to change back to single server configuration. So I removed second server from cluster and disabled load balancing. As a consequence the two new IPs had been removed and the server got its old consecutive IP addresses back, all automatically like it should. But now I have a problem: Teredo server is not starting anymore. Basically the server works and users can establish IPHTTPS connections without any problems. But Remote Access console displays red cross for Teredo and says Teredo server has stopped working. If I check Teredo over PowerShell with netsh interface teredo show state I get State=offline and Error= unable to open primary socket.

I checked everything. IP addresses configured correctly, restarted services, restared whole server.

I dont know what to do. Any suggestions? Thanks in advance!

If you have questions or need additional information, just ask!

Sebastian  

April 24th, 2015 3:10am

Found a solution today. Following blog entry describes how Teredo can be added subsequently to an existing DirectAccess configuration:

http://directaccess.richardhicks.com/2015/04/28/enable-teredo-support-after-directaccess-has-been-configured/

I tried the PowerShell command "Set-DAServer TeredoState Enabled" and after a few seconds everything is back working!

  • Marked as answer by skrueck 47 minutes ago
Free Windows Admin Tool Kit Click here and download it now
May 5th, 2015 2:36am

Found a solution today. Following blog entry describes how Teredo can be added subsequently to an existing DirectAccess configuration:

http://directaccess.richardhicks.com/2015/04/28/enable-teredo-support-after-directaccess-has-been-configured/

I tried the PowerShell command "Set-DAServer TeredoState Enabled" and after a few seconds everything is back working!

  • Marked as answer by skrueck Tuesday, May 05, 2015 6:35 AM
May 5th, 2015 6:35am

Found a solution today. Following blog entry describes how Teredo can be added subsequently to an existing DirectAccess configuration:

http://directaccess.richardhicks.com/2015/04/28/enable-teredo-support-after-directaccess-has-been-configured/

I tried the PowerShell command "Set-DAServer TeredoState Enabled" and after a few seconds everything is back working!

  • Marked as answer by skrueck Tuesday, May 05, 2015 6:35 AM
Free Windows Admin Tool Kit Click here and download it now
May 5th, 2015 6:35am

Found a solution today. Following blog entry describes how Teredo can be added subsequently to an existing DirectAccess configuration:

http://directaccess.richardhicks.com/2015/04/28/enable-teredo-support-after-directaccess-has-been-configured/

I tried the PowerShell command "Set-DAServer TeredoState Enabled" and after a few seconds everything is back working!

  • Marked as answer by skrueck Tuesday, May 05, 2015 6:35 AM
May 5th, 2015 6:35am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics