Crossroads305
asked on
HTTP over RPC & Out Of Office
I currently have an Exchange Server on Domain 1 and clients who reside on Domain 2. They are accessing the Exchange server using HTTP/S over RPC with no problems, except when they go to set there Out of Office they get an error stating:
"Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later."
Now I know this is a classic Autdiscover website issue, which I believe it still is, however my problem is BOTH the clients domain and the excange servers domain are the same name with NO vpn between the two. My understanding is the autodiscover.clientdomain.
"Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later."
Now I know this is a classic Autdiscover website issue, which I believe it still is, however my problem is BOTH the clients domain and the excange servers domain are the same name with NO vpn between the two. My understanding is the autodiscover.clientdomain.
I would suggest that you use DNS internally to set an A record to point directly to the internal address of the Exchange server that resolves the autodiscovery.
Inside the network also not working?
create an A record autodiscover.domain.com poiting to ur server
ASKER
JonGarretUK: When you say use "DNS internally to set an A record" are you saying set clientdomain.com internally to resolve to the external exchange server address? If that is what your stating, I do - it's impossible and will cause serious problems internally since clientdomain.comw ill be point to an external non accessible server for Domain information.
Abbasiftt: I already have an A record and inside which network? As I stated they are two seperate domains physically but have the same domain name.
Abbasiftt: I already have an A record and inside which network? As I stated they are two seperate domains physically but have the same domain name.
create an A record in the domain where your client is located
ASKER
Abbasiftt: I already have one and I am still getting the error.
The internal A record should be set to the internal IP address rather than the external address
If you ctrl+right click on the Outlook icon in the systray and do test autodiscovery what are the errors?
If you ctrl+right click on the Outlook icon in the systray and do test autodiscovery what are the errors?
ASKER
The client machines cannot connect to the internal IP of the Exchange Server.
ASKER
JonGarrettUK: When running the Autodiscover check I get a few errors related to the Autodiscover:
Autodiscover to https://autodiscover.clientdomain.com/autodiscover/autodiscover.xml FAILED (ox899c8203)
Local Autodiscover for clientdomain.com FAILED (0x8004010F)
Again when i run this outside the domain it works fine.
Autodiscover to https://autodiscover.clientdomain.com/autodiscover/autodiscover.xml FAILED (ox899c8203)
Local Autodiscover for clientdomain.com FAILED (0x8004010F)
Again when i run this outside the domain it works fine.
Sorry so there is a barrier between the 2 server and the clients either a firewall of networking infrastructure?
Is there an ISA in the way?
Is there an ISA in the way?
ASKER
There is no "barrier" per say they are two seperate networks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I think your on to somethign there... This might sound stupid but can I take the local http:// out of the XML file on the server so that it never tries to connect locally?
I have not tested that one personally but if you configure a local XML file to set without it then it should work.
To enforce the XML check first set the registry keys:
Office 2007 – HKEY_CURRENT_USER\Software
Office 2010 – HKEY_CURRENT_USER\Software
Value: 1
Type: DWORD
To set the path to the local XML file, set the following:
Office 2007 – HKEY_CURRENT_USER\Software
Office 2010 – HKEY_CURRENT_USER\Software
To enforce the XML check first set the registry keys:
Office 2007 – HKEY_CURRENT_USER\Software
Office 2010 – HKEY_CURRENT_USER\Software
Value: 1
Type: DWORD
To set the path to the local XML file, set the following:
Office 2007 – HKEY_CURRENT_USER\Software
Office 2010 – HKEY_CURRENT_USER\Software
ASKER
I have made some progress. If I uncheck the:
"On Fast networks, connect using HTTP first, then connect using TCP/IP"
"On slow networks, connect using HTTP first, then connect using TCP/IP"
During the Microsoft Exchange Proxy setttings, the OOF seems to work now! I'm guessing thats a long the same line of thoughts that you had. Thank you for your help!!!!! Any idea if I can remove the local autodiscover http address from the server file itself rather then have to make changes to every workstation? If you'd rather I can start a new Question on Experts Exchange.
"On Fast networks, connect using HTTP first, then connect using TCP/IP"
"On slow networks, connect using HTTP first, then connect using TCP/IP"
During the Microsoft Exchange Proxy setttings, the OOF seems to work now! I'm guessing thats a long the same line of thoughts that you had. Thank you for your help!!!!! Any idea if I can remove the local autodiscover http address from the server file itself rather then have to make changes to every workstation? If you'd rather I can start a new Question on Experts Exchange.
Have a look here, seems that you can just by using the FQDN:
http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/f0e5a388-8a07-412a-9e35-672cfe8dd31c/
http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/f0e5a388-8a07-412a-9e35-672cfe8dd31c/
ASKER
Thanks for your help, i'm not sure about the FQDN part but I think that's best saved for another Experts Exchange Post.