TMG Connectivity Verifiers Not Working
-
Thursday, November 15, 2012 2:07 PM
I have TMG deployed at a customer for publishing Exchange 2010. I am having trouble with the Connectivity Verifiers. I created 3 Server Farms (one for OWA, one for ActiveSync and one for RPC) and each server farm was set to verify the specific virtual directory in question.These farms are set to go to the actual servers themselves and not through the load balancer.
OWA: https://*/owa/
ActiveSync: https://*/Microsoft-Server-ActiveSync/
RPC: https://*/rpc/
At first, it seemed to work, but now those do not work at all, even though I can manually browse to those virtual directories from the TMG server. However, when I change the Connectivity verifiers to either the Ping method or Port method (443), the verifiers work. Any ideas on why the other verifiers are not working?
MCITP Exchange 2010 | MCTS Exchange 2007 | MCITP Lync Server 2010 | MCTS Windows 2008 | MCSE 2003
All Replies
-
Friday, November 16, 2012 1:53 PMModerator
It depends on what HTTP response you get back as to whether TMG sees it as healthy as described here: http://technet.microsoft.com/en-us/library/cc441459.aspx
From memory, a connection to ActiveSync from a browser actually generates a '501 Not Implemented error', which TMG would interpret as a failed connection as it is not an expected success response.
You may have to use a single path for validation (like /owa) for all services, as at least you then know IIS is responding to the GET request which is better than ping or a 443 port request.
Cheers
JJ
Jason Jones | Microsoft MVP | Silversands Ltd | My Blogs: http://blog.msedge.org.uk and http://blog.msfirewall.org.uk
- Marked As Answer by Nick Gu - MSFTMicrosoft Contingent Staff, Moderator Friday, November 23, 2012 6:32 AM
.png)
