RE: Discussion of Configuring Outlook 2003 RPC over HTT... - 8.Jan.2004 8:32:00 PM
You can indeed create a profile while not on the network hosting the Exchange 2003 server... In my experience, all Outlook will do is complain that it cannot verify the login and you can just continue on and configure for RPC-HTTPS... Once you start Outlook, it will connect via RPC-HTTPS as usual...
Thanks! I've never been able to make it work that way. Maybe I wasn't trying hard enough? It seemed that the profile creation process just halted when the client wasn't able to connect and confirm the account. I'll have to try things again and see what happens.
RE: Discussion of Configuring Outlook 2003 RPC over HTT... - 10.Jan.2004 1:21:00 AM
Yes sir, After configuring Windows Server 2003 and Exchange 2003 to accept RPC/HTTPS, as well as configuring the PIX to only allow ports 80, 143 and 443 through to Exchange 2003. I was able to sucessfully configure my Outlook 2003 client at my home office to connect to Exchange via RPC/HTTPS throught the PIX.
Outlook 2003 complains about not being able to verify the account because 135 is not availible, but after finishing up the configureation, the connection is able to be made.
sbs 2003 behind a NAT router. Ports 143, 443 & 80- are fwd' to the server. I am running a new exchange owa site (created from within Exchange sys mgr). This site has a fqdn of webmail.url.com.
I cannot set up the client pointing to that fqdn. only the internal name will work. ie (servername). I have tried throwing 'server.domain.com' and it says the server isn't available. In any case...I have configured the 'connect over http' settings many different ways including the way you showed. I have ssl enabled on the owa site, as well as a certificate already created (which works fine).
Port 143/tcp is IMAP and isn't needed for RPC over HTTPs. Is the CA for the certificate imported in "Trusted Root CA"? Have you tried <servername>.<ad domaine> in The "Microsoft Exchange Server? In Exchange Proxy settings the server name need to be the domain name the certificat is issued to.
But you'v already made a tunnel throug the frontend server. This is the only way i'v got it to work behind a router with only port 80 and 443 open. Then again i haven't tried without the patch for UPN logon...
Sure, if you can connect with RPC while configuring the profile the client resolves the correct servername and configures it in the profile. But if you only have HTTPs access you have to be very specific with the FQDN for the exchange server.
Hi Everyone. I have port 135 blocked by my ISP. I have NEVER had the computer I'm setting up the Outlook profile, on the internal network. I have tried everything I can think of, and cannot get a connection using ONLY Rpc over HTTP. It does however work great from another external site that DOES have 135 open and able to resolve the internal server name. Anyway, I'm ready to try the ORK solution, but I don't understand how others have gotten this to work, and why Microsoft would design it not to connect if the machine never sees port 135. ANY help is most appreciated. It seems there must be something I'm missing as I am for certain that if 135 goes through, I can connect, using the same settings on another computer just on a different cable modem with a different ISP. I am also FOR CERTAIN that when it connects it is using HTTPS - so I know the servers are correct.
Thanks for any thoughts anyone has on the subject.
Hello Tom - I can't believe I get a response back from the master himself. Well, just leaving "Check Name" alone does not work. Not when 135 is blocked. I am at the building now with the laptop, and it works using RPC over HTTP. However, even here it wants to use some TCP to cache the mailbox and that sort of thing. If I look at my connection status here at the building in Outlook 2003 - it has 4 connections : 2 TCP and 2 HTTPS. I figured now that I've established the Outlook profile, I can go back to my problem network with no port 135, and see if I can get in.