DirectAccess on Machine with TMG: cannot reach internal servers with Teredo, ping works


my setup: ws 2008 r2 ent, tmg 2010 sp1. internal network uses native ipv6.

i've deployed directaccess, clients can succesfully connect via iphttps , teredo da server , reach internal servers ping.

after enabling edge traversal icmpv6, can ping teredo da client address internal network.

but, can access internal network services (dns, fileshare, http, etc.) when connected iphhtps. when disable iphttps , teredo still active, can ping.

from wf.msc console can see main mode , quick mode secure channels teredo clinet ip address (2001:...) established da server (2002:...).

how can teredo work?


mcitp: ea, ema, va; mcsa

i think @ point, your question seems point to a tmg configuration question. if may suggest , recommend, may better post to the tmg forum tmg specific assistance.

for convenience, here's link forum: http://social.technet.microsoft.com/forums/en/forefrontedgegeneral/

ace


ace fekay
mvp, mct, mcitp ea, mcts windows 2008 & exchange 2007, mcse & mcsa 2003/2000, mcsa messaging 2003
microsoft certified trainer
microsoft mvp - directory services

this posting provided as-is no warranties or guarantees , confers no rights.



Windows Server  >  Network Infrastructure Servers



Comments

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

Cannot access Anywhere Access using domain name?

WMI Failure: Unable to update Local Resource Group