DeepFat
asked on
Exchange Web services - EWS
Hi
I have a Exchange 2010 SP2 Dag environment.
Using exchange microsoft test connectivity tool.
When I set internal url the external test fails, when I set external url internal test fails.
When I set both url's in a single shell command, internal url fail.
Is anyone able to shed any light on this.
I have a Exchange 2010 SP2 Dag environment.
Using exchange microsoft test connectivity tool.
When I set internal url the external test fails, when I set external url internal test fails.
When I set both url's in a single shell command, internal url fail.
Is anyone able to shed any light on this.
What is the command used to set the URls?
ASKER
We have 3 cas servers so I use the following command naming each server
Set-WebServicesVirtualDire ctory –Identity ServerName\EWS* -InternalUrl https://mail.domain.co.uk/ews/exchange.asmx
I also found after applying the commands Microsoft test connectivity test show successful on the internal network but unsuccessful on external network and only for around 10 minutes, then my test fails on internal and is successful on external.
I have also tried the following and tests are only successful on the external network.
Set-WebServicesVirtualDire ctory –Identity ServerName\EWS* -InternalUrl https://mail.domain.co.uk/ews/exchange.asmx -ExternalUrl https://mail.domain.co.uk/ews/exchange.asmx
Set-WebServicesVirtualDire
I also found after applying the commands Microsoft test connectivity test show successful on the internal network but unsuccessful on external network and only for around 10 minutes, then my test fails on internal and is successful on external.
I have also tried the following and tests are only successful on the external network.
Set-WebServicesVirtualDire
Ensure that the host name resolves internally correctly to begin with.
You will probably need to use a Split DNS to ensure that works.
What error does the test fail with?
I would also upgrade the server - Exchange 2010 SP2 is no longer supported, you need to be on Exchange 2010 Sp3 to be supported.
Simon.
You will probably need to use a Split DNS to ensure that works.
What error does the test fail with?
I would also upgrade the server - Exchange 2010 SP2 is no longer supported, you need to be on Exchange 2010 Sp3 to be supported.
Simon.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This solution was not suggested by anyone else on the forum and required further investigation from other forums to resolve.
ASKER
Set-WebServicesVirtualDire ctory –Identity ServerName\EWS* -InternalUrl https://mail.domain.co.uk/ews/exchange.asmx -ExternalUrl https://mail.domain.co.uk/ews/exchange.asmx