oulook anywhere proxy setting uncheck after reboot
I have outlook anywhere setup on couple remote user and every time they reboot there computer the proxy sitting uncheck it self then it says disconnected.
I have one computer working fine with the same configuration so I am confuse, any help will be appreciated
I have one computer working fine with the same configuration so I am confuse, any help will be appreciated
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
At this remote site - could GPO be cancelling the setting?
ASKER
this is not a remote site, It just a couple users that work outside the office.
So no GPO's being applied to them that would resit this setting?
ASKER
No, everything were working fine until few days ago and have not make any changes are do any updates on the server.
You may not have changed something, but your web host may have done.
You need to an Autodiscover test within Outlook to see what information is being returned to the client.
Simon.
You need to an Autodiscover test within Outlook to see what information is being returned to the client.
Simon.
ASKER
simon,
I've test the connection and everything seems fine, I am running out of option.
I've test the connection and everything seems fine, I am running out of option.
Did you do the test from outside of your network?
I am seeing so many problems recently with Autodiscover being disrupted by changes made by web hosts that it is almost becoming the first thing to check.
You could also setup a test account and then run it through Microsoft's test site at https://testconnectivity.microsoft.com/
Simon.
I am seeing so many problems recently with Autodiscover being disrupted by changes made by web hosts that it is almost becoming the first thing to check.
You could also setup a test account and then run it through Microsoft's test site at https://testconnectivity.microsoft.com/
Simon.
ASKER
Simon,
When I run the test the only exception I get is.
Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
Every other check return fine.
When I run the test the only exception I get is.
Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
Every other check return fine.
That is a fairly normal configuration "error". It is because of changes to the root certificates that are constantly going on, which Microsoft no longer apply to the oldest versions of Windows.
If you browse (externally) to https://example.com/Autodiscover/Autodiscover.xml what happens?
That is the root of your public domain name. You must do it from outside of your network.
Simon.
If you browse (externally) to https://example.com/Autodiscover/Autodiscover.xml what happens?
That is the root of your public domain name. You must do it from outside of your network.
Simon.
ASKER
Simon,
I get the message below when I try to login
<?xml version="1.0" encoding="UTF-8"?>
-<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
-<Response>
-<Error Id="1046638289" Time="19:51:46.5971812">
<ErrorCode>600</ErrorCode>
<Message>Invalid Request</Message>
<DebugData/>
</Error>
</Response>
</Autodiscover>
I get the message below when I try to login
<?xml version="1.0" encoding="UTF-8"?>
-<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
-<Response>
-<Error Id="1046638289" Time="19:51:46.5971812">
<ErrorCode>600</ErrorCode>
<Message>Invalid Request</Message>
<DebugData/>
</Error>
</Response>
</Autodiscover>
Two things.
1 - that error is to be expected on Autodiscover, because you aren't an Outlook client.
2 - if that was to the root of your domain (as per my instructions) from an external machine AND the root of your domain does not point to your Exchange server, then you shouldn't have got anything - certainly not that XML response.
That suggests that my first suggestion - the problem being at your web host, is indeed the case.
Simon.
1 - that error is to be expected on Autodiscover, because you aren't an Outlook client.
2 - if that was to the root of your domain (as per my instructions) from an external machine AND the root of your domain does not point to your Exchange server, then you shouldn't have got anything - certainly not that XML response.
That suggests that my first suggestion - the problem being at your web host, is indeed the case.
Simon.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
ASKER