Mustafa, If everything else is OK as you mention, I can only think of your SSL certificate. May be the common name used to issue the certificate does not match the URL used to access the RPC over HTTP. This was a problem I had in the lab, and found it out the hard way. Unlike OWA, RPC over HTTP will not warn you if the certificate names do not match. Instead, it will simply timeout. Can you tell me the url you are using to access the RPC over HTTP, and the "Issued To: " part of your SSL certificate. Regards, Raj -----Original Message----- From: Mustafa Cicek [mailto:mbcicek@xxxxxxxxx] Sent: Wednesday, September 15, 2004 12:43 PM To: [ExchangeList] Subject: [exchangelist] RE: RPC over HTTPS and Outlook 2003 http://www.MSExchange.org/ Hi Raj, I tried that also before. It doesn't help me. I wonder that no it expert knows about it!!! Or some know the solution, and they don't tell it?! If I don't find any solution, I risk my job. It's really bad! Best Regards Mustafa ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this MSEXchange.org Discussion List as: raj.periyasamy@xxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to listadmin@xxxxxxxxxxxxxx