Zolly-Simon
asked on
RPC over HTTP setup fails
I have found several articles outlining the "How-To RPC over HTTP" but none for a multi server environment. I have tried to improvise on the instructions but have failed to achieve my goal.
My goal of setting up RPC over HTTP is to have my users gain access to the Microsoft Exchange Server, VIA Outlook 2003. I have set this up on other Windows 2003 SBS servers through the use of Wizards, but do not have the luxury of the wizards on a Standard Edition Server.
I have the following servers & their roles;
1) PDC - Windows 2003 Standard Edition.
2) BDC Windows 2000 Advanced Server
3) Exchange Server 2003 Standard Edition
4) File Server, Windows 2000 Enterprise Edition
5) SQL Server, Windows 2000 Enterprise Edition
I have no idea what difference it makes, having multiple servers while setting up RPC over HTTP, but I suspect that is what is causing my setup to fail.
I am aware of settings that need to change in Outlook under "More Settings" - "Connection" - "Connect to my Exchange Mailbox using HTTP", once I have successfully configured RPC over HTTP. I keep checking Outlook Connection Status VIA "hold down the "CTRL" key, right click on Outlook icon down on system tray (by clock) and choose "Connection Status...." from the popup" look in "Conn" column, if it says HTTP, you're good to go, Mine always says TCP/IP, not good to go!
TIA
My goal of setting up RPC over HTTP is to have my users gain access to the Microsoft Exchange Server, VIA Outlook 2003. I have set this up on other Windows 2003 SBS servers through the use of Wizards, but do not have the luxury of the wizards on a Standard Edition Server.
I have the following servers & their roles;
1) PDC - Windows 2003 Standard Edition.
2) BDC Windows 2000 Advanced Server
3) Exchange Server 2003 Standard Edition
4) File Server, Windows 2000 Enterprise Edition
5) SQL Server, Windows 2000 Enterprise Edition
I have no idea what difference it makes, having multiple servers while setting up RPC over HTTP, but I suspect that is what is causing my setup to fail.
I am aware of settings that need to change in Outlook under "More Settings" - "Connection" - "Connect to my Exchange Mailbox using HTTP", once I have successfully configured RPC over HTTP. I keep checking Outlook Connection Status VIA "hold down the "CTRL" key, right click on Outlook icon down on system tray (by clock) and choose "Connection Status...." from the popup" look in "Conn" column, if it says HTTP, you're good to go, Mine always says TCP/IP, not good to go!
TIA
ASKER
Thank you, I have bookmarked this article long ago. and have completed everything up to where I download Harry Bates RPC regedit tool. The problem is, I am running Windows 2003 Server Sp2, and Exchange SP2 also.
Will there be an issue if I run that tool (downloaded it just now)?
Will there be an issue if I run that tool (downloaded it just now)?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
There are areas where one may be concerned whether or not these instructions are applicable because of constant mention of SP1, (I am running SP2) and we all know, there is a world of difference between service packs. I boldly went where no man has gone before, or felt like I was. Thank you
http://www.petri.co.il/con
when the mean multiple servers, they mean multiple exchanges servers, a true frontend to backend solution. In your case you only have one exchange server so it would be a single server install.