RPC over HTTP not working on Small Business Server 2003

Hi guys,

We have been battling a recent Exchange deployment trying to get RPC over HTTP to work.  

Client-side, I am not able to establish a connection to the Exchange server via RPC-HTTP.  I have installed the certificate, configured the exchange account to point to "mail.domain.com", configured the HTTP proxy to point to the same domain, set up mutual SSL authentication (msstd:mail.domain.com), enabled basic authentication.  When I run "outlook /rpcdiag", it prompts for login credentials twice, tries to establish a connection, and then displays an error that "the connection to Microsoft Exchange is unavailable."

I have triple-checked that the server is configured correctly and I've run the CEICW wizard multiple times.  The firewall is allowing ports 80 & 443 to pass to the SBS box.  OWA works great.

The server is running Small Business Server 2003, SP2.

The workstation is Windows XP Pro, SP1  with Office 2003, SP3.

I have read countless articles for configuring RPC-HTTP including TechNet articles and troubleshooting steps.  Still, I am unable to find the issue.  I would really appreciate a few tips or maybe some things I've overlooked.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Anything in the event logs or IIS logs on the server/ Client

I hope this helps !
Jian An LimSolutions ArchitectCommented:
my suggestion is to setup Remote workplace

go through your CEICW wizard again
make sure you tick remote workplace and outlook via the internet

goto https://<SBSserver>/remote and there are instruction there how to do it .

make sure you save your certificate to your PC (if you open your IE, you must not get a certificate error)
Adam GrahamEnterprise ArchitectCommented:
Are you using a trusted certificate or the home grown SBS cert? Best of my knowledge you need a trusted cert to configure RPC over HTTP on SBS.

Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

the self cert setup by the ceicw works fine and although it generates a warning in ie to the effect its not a truely trusted source it causes no problems to do so. as i have many sbs  servers configured for exactly this scenario.

ensure the certificate is saved into the "trusted root certificate " store manually when you save it from within IE and that it  matches the domain name (it shouldnt let you save the certificate if its not)

as per limjianan the remote web workplace link for rpc configuration instructions is actually generated from your configuration so it would show the wrong instructions if you have mis configured it anywhere.

Adam GrahamEnterprise ArchitectCommented:

I am refering specifically to RPC over http not working with the home growen certificate.

jtgerdesAuthor Commented:
I am using the certificate that the server generated when I ran the CEICW wizard.  The domain name on the certificate does match the domain name I'm trying to access.  I have already installed it manually in the trusted root certificates.

When I try to view the RWW, I get an error that "Directory listing denied."  I can access the main "company" website on the SBS.

Nothing in particular in the event viewer....
jtgerdesAuthor Commented:
Hi all.

I have found a solution to the issue!  I've changed so many settings and tried so many things over the last 4 days that I'm surprised it ended up configured correctly .... except for one small thing on the client side.  I had the exchange server address as "mail.domain.com," not the INTERNAL NetBIOS name of the server.  Once I changed the Exchange server address to the internal address and set the RPC proxy address to the "mail.domain.com," I was able to connect successfully.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Adam GrahamEnterprise ArchitectCommented:
Glad your sorted.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.