If you are not using SSL with RPC/HTTP then there are a lot of changes you need to make. I have only ever got it successfully working with an SSL certificate.
The rpcproxy registry changes are the key thing to getting it to work. This the (modified) configuration from a live production system. I have put it line by line for ease of reading. Server07 is a frontend exchange - these can be dropped if you aren't using a frontend server. Server06 is the backend exchange Server03 is the domain controller with global catalog functionality. Internal AD is domain.com External address is external.com - this is what the clients enter to connect to the RPC/HTTP server in Outlook. If there are multiple addresses or the clients are likely to use IP addresses, then this needs to be entered as well. server07:100-5000; server06:6001-6002; server06.domain.com:6001-6002; server03:6001-6002; server03.domain.com:6001-6002; server06:6004; server06.domain.com:6004; server03:6004; server03.domain.com:6004; mail.external.com:6001-6002; mail.external.com:6004; server03:593; server03.domain.com:593; server06:593; server06.domain.com:593; mail.external.com:593; Don't forget to make the single registry change on the domain controller. (NSPI...) Hope this helps, Simon. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Microsoft Exchange List Server Sent: 17 June 2004 23:33 To: Exchange Discussions Subject: RPC over HTTP exchange2003 running on a member server. Hi all, I cannot make RPC over HTTP work. The problem: internet users using Xp+SP1+outlook2003 cannot create the outlook profile I got the following error while "check name". "The connection to the microsoft exchnage server is unavailable Outlook must be online or connected to complete this operation" I have 1 W2003 domain 2DCs which are GCs also, 1 windows2003member server running exchange2003. This is what I have done, 1) Before SP1 I have installed the HTTP proxy component and I have made the RPCPROXY registry "ExchangeServer:6001;ExchangeServerFQDN:6001;ExchangeServer:6004;Exchang eServerFQDN:6004" mod suggested in "Exchange Server 2003 RPC over HTTP deployment scenarios" May 28, 2004. ..rpc over http did not work..I hav echange ExchangeServer for the name of my server. 2) After SP1 release , I have installed SP1 and selected the back-end option.* 3) I can confirm that OWA works ok, using the same PC and same dial-up connection which blocks port 135. 4) We do not use SSL. 5) as you see we do not use any front-end back-end email configuration. all this time the only port open at the firewall for the email server is port 80. *the documentation states that I will receive a message saying that the registry keys are going to be modified I have never received that message. thx, _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang=english To unsubscribe send a blank email to %%email.unsub%% Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
