Ok I have COMPLETELY reinstalled everything on Exchange 2010 SP1. Mainly because I couldn't get RPC to work nor Autodiscover. So now I just want to concentrate on Autodiscover. When I run the testexchangeconnectivity.com tool it ALWAYS returns this: Attempting to send an Autodiscover POST request to potential Autodiscover URLs. Autodiscover settings weren't obtained when the Autodiscover POST request was sent. Test Steps ExRCA is attempting to retrieve an XML Autodiscover response from URL https://hosted.compsysar.com/Autodiscover/Autodiscover.xml for user jdixon@compsysar.com. ExRCA failed to obtain an Autodiscover XML response. Additional Details A Web exception occurred because an HTTP 401 - Unauthorized response was received from Unknown. So when I use a browser to go to: https://hosted.compsysar.com/Autodiscover/Autodiscover.xml it just continues to prompt me for my username and password over and over. I've tried DOMAIN\username, username, UPN (email), and even different users. Oh did I mention that I can browse to this internally (using the internal FQDN) and it accepts my credentials and displays the XML page with error code 600 and Invalid Request (which this is what it is supposed to do when you browse to it via browser I believe) Like I said I have reinstalled a new DC and EX2010 because I thought something was messed up with my last one.

Hi, Have a look into these post they have some good troubleshooting steps that might help : http://forums.msexchange.org/Throubleshotting_RPC_over_HTTP_(Outlook_Anywhere)/m_1800521362/tm.htm http://social.technet.microsoft.com/Forums/en-US/exchangesvrclients/thread/e507dffe-a6ce-475b-8a12-9d66f98db99f/ Also have u enable outlook anywhere option in CAS server option??Ripu Daman Mina | MCSE 2003 & MCSA Messaging

Do you have any firewall such as ISA or TMG in front of the Exchange server that does any form of publishing? You are correct on the 600 message when browsing the autodiscover/autodiscover.xml file, this is expected behavior. Martin Sundstrm | Microsoft Certified Trainer | MCITP: Enterprise Messaging Administrator 2007/2010 | http://msundis.wordpress.com

I'm not doing just a CAS. The way I have it setup is one DC runnig 2008 R2 and one Exchange 2010 SP1 multi tenant (mailbox, client access, hub transport). I did enable Outlook-Anywhere. I also have looked at those links and tried but I'm not really getting anywhere. I think the problem is I'm confused. I have port 443, 25, 110, imap4 opened to my Exchange 2010 server.

No the only thing I have is a sonicwall. The ports are port-forwarded and working. Now my certificate only has the domain hosted.compsysar.com. I prefer not to have to purchase a SAN certificate since we had this one already. I thought I read somewhere that if you used SRV records then you didn't need a cert for the autodiscover

RPCPing results: rpcping -t ncacn_http -s hosted.compsysar.com -o RpcProxy=hostd.compsysar.com -P "administrator,hosted.local,*" -I "administrator,hosted.local,*" -H 2 -u 10 -a connect -F 3 -v 3 -E -R none Sending ping to server Response from server received: 401 Client is not authorized to ping RPC proxy Ping failed This is from another computer. I have vlanning setup so the computer is from a different subnet, but the router is capable of routing between them

Hi, Have a look into this article for outlook anywhere: http://exchangeserverpro.com/how-to-configure-exchange-server-2010-outlook-anywhere & also http://www.msexchange.org/articles_tutorials/exchange-server-2007/planning-architecture/uncovering-new-rpc-client-access-service-exchange-2010-part1.html these article might clear the confusion Ripu Daman Mina | MCSE 2003 & MCSA Messaging

from reading ithink part 2 might be what i need. see i find all kinds of tutorials for deploying this with the mailboxes seperate from the client aceess but we can do that. i have to use one DC and thrn one Exchange and im havjng trouble getting it to work that way. now im also not using a SAN cert. is there a way for me not to use a san so i can just get a certificate for the external domain name? based on what i read everyonr seems to get a SAN cert Edit: Uhm I'm not sure that will fix my issue. All these ports are open and the Exchange can talk to the DC. I'm just wondering if this would work better in my situation to put the Exchange server on the DC. I'm sorry but I'm not finding a reason as to why this isn't working. I've tried all sorts of things and the server is listening on 6001,6002,6003, and 6004.

from reading ithink part 2 might be what i need. see i find all kinds of tutorials for deploying this with the mailboxes seperate from the client aceess but we can do that. i have to use one DC and thrn one Exchange and im havjng trouble getting it to work that way. now im also not using a SAN cert. is there a way for me not to use a san so i can just get a certificate for the external domain name? based on what i read everyonr seems to get a SAN cert Edit: Uhm I'm not sure that will fix my issue. All these ports are open and the Exchange can talk to the DC. I'm just wondering if this would work better in my situation to put the Exchange server on the DC. I'm sorry but I'm not finding a reason as to why this isn't working. I've tried all sorts of things and the server is listening on 6001,6002,6003, and 6004. Another Edit: I got the RPCping to work. The problem was I was using -H 2 instead of -H 1. Apparently -H 2 is for NTLM and I need to do basic. Still a problem with exchange online not working correctly and outlook clients not connecting though :-(

I tried setting up a outlook client and it kept prompting for credentials. Then on the Exchange server I noticed: Event ID: 4625 An account failed to log on. Subject: Security ID: NULL SID Account NAme: - Account Domain: - Logon ID: 0x0 Logon Type: 3 Account for Which Logon Failed: Security ID: NULL SID Account NAme: jdixon@compsysar.com Account Domain: Failure Information: Failure Reason: Domain sid inconsistent State: 0xc000006d .... .. Detauled Authentication Inforamtion: Logon Process: NtLmSsp Authentication Package: NTLM Uhm.. isn't supposed to be NTLM

Solution: It appears the issue was copying a VM. Even the Microsoft person said it shouldn't of mattered since the machine I copied was just a fresh install of Server 2008 R2 (as in no domain, dc, dns, etc). So I found that even though I copied two more and set it up I kept getting the same results. So then I setup two more environments without copying the VM and it works just fine. Strange! Might be a bug.. something was obviously retained that Exchange didn't like when the VM was copied.