Recently I installed a watchguard xtm 21 appliance.
Everything went fine until I updated from Office 2007 to Office 2010.
Behind my watchguard appliance I've got an Exchange 2007 server, which I was able to reach with Outlook 2007 (when working remote over ssl vpn connection).
Now with Outlook 2010, working remote over ssl vpn, I'm not able to reach my Exchange server.
Do I need to change some settings, (port configuration?) specific for Outlook 2010 on my wachtguard appliance?
Did Outlook 2010 try to autoconfigure your account when you set it up? If so, it might have picked up some not working settings for Outlook Anywhere and be trying to connect over those instead.
Be aware that Outlook 2010 will attempt to use the CAS services (autodiscover etc) even if you think it shouldn't. Chances are that you will need to allow access to your CAS servers to be able to make progress with Outlook 2010.
I recently added a new subnet of servers in a remote site and tried to add a VPN tunnel to access them. The VPN connection was previously in use and is working for some of the routes but not all. I have Watchguard x5500 at both sites.
The Office -> Remote DC looks like:
192.168.40.0/24 <==> 10.0.10.0/24
192.168.40.0/24 <==> 10.0.20.0/24
192.168.40.0/24 <==> 192.168.10/24
The Remote -> Office lookls like:
10.0.10.0/24 <==> 192.168.40.0/24
10.0.20.0/24 <==> 192.168.40.0/24
192.168.10/24 <==> 192.168.40.0/24
The 10.0.x.x/x routes are working correctly. The new subnet (which works fine locally) does not connect. I cannot ping or talk to those servers in anyway.
Anyone know a good way to troubleshoot BOVPN tunnels for Watchguard?
Turns out you have to be very careful with VPN IP addresses. We had an old setting for a VPN to a network that previously used that subnet. Once that old setting was removed and only the new VPN claimed that range, it connected.