hcittech
asked on
Exchange 2012 Outlook Web Access through Watchguard XTM26
Hi,
I am having trouble getting through a Watchguard XTM26 to a customers OWA.
To remove some variables, I am now simply trying to RDP into the server (to ensure I have the Firewall ports open as needed etc) but cannot even do that.
I have attached an image of the ports I have opened - is there anything else I should need to do to the XTM26 to enable outside access, whether it be for RDP or something more advanced as OWA.
Getting RDP to work would be a start - at least I would know I was on the right path! I know that in the past it has been as simple as just configuring the port to point to the server with everything else working 'out of the box' as they say...
Thanks in advance...
I am having trouble getting through a Watchguard XTM26 to a customers OWA.
To remove some variables, I am now simply trying to RDP into the server (to ensure I have the Firewall ports open as needed etc) but cannot even do that.
I have attached an image of the ports I have opened - is there anything else I should need to do to the XTM26 to enable outside access, whether it be for RDP or something more advanced as OWA.
Getting RDP to work would be a start - at least I would know I was on the right path! I know that in the past it has been as simple as just configuring the port to point to the server with everything else working 'out of the box' as they say...
Thanks in advance...
strivoli
The server itself might have a firewall such as the Windows Integrated Firewall or Microsoft's ISA/TMG.
Are you able to traceroute to the server? If not, where does it fail?
Can you "telnet REMOTEHOST 3389" Does it wait, or disconnect immediately?
If waiting, then you've connected to the TS. If it disconnects immediately, you aren't getting there in the first place.
Can you "telnet REMOTEHOST 3389" Does it wait, or disconnect immediately?
If waiting, then you've connected to the TS. If it disconnects immediately, you aren't getting there in the first place.
ASKER
Thanks for your quick response...
The Windows Fierewall is on but RDP is allowed on the Domain, Private & Public networks so should be accessable externally (I have not moved on to OWA yet, if I cannot get RDP through then I can forget OWA).
Thanks
The Windows Fierewall is on but RDP is allowed on the Domain, Private & Public networks so should be accessable externally (I have not moved on to OWA yet, if I cannot get RDP through then I can forget OWA).
Thanks
Even though RDP is allowed, it might be set to accept only connections from the local subnet.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Finally found solution via Watchguards latest help files...