Hello! I have just managed to our exchange server off the ground and up and running this week. Following lots of tutorials, running into lots of problems along the way, I finally managed to get it delivering mail, receiving mail, OWA working, AD setup, multiple domains on one exchange box, some additional tricks installed. Here is my current setup. -Windows Server 2003, updated -Exchange Server 2003 (32bit limitations), updated -One box hosting IIS,DNS,Exchange at winbox.myhost.net (FQDN) -Netios name winbox -No front-end -One client running Outlook 2007 with Vista Outlook Setup -MS Exchange Server: winbox.myhost.net (NOT CACHED) -Username: zcferres -Logon network security: Negotiate -Encryption: ticked -Connect to MSEx using HTTP: ticked -Connection: Using LAN -URL for proxy: winbox.myhost.net -Only connect to proxy servers that have principal name in certificate: NOT ticked -fast networks,slow networks: ticked -Proxy Auth: Basic Authentication Exchange/IIS Setup -Back-End RPC-HTTP topology -IIS shows all websites are running -ValidPorts Entry: winbox:6001-6002;winbox.myhost.net:6001-6002;winbox: 6004;winbox.myhost.net:6004 -RPC Properties, Auth Methods Anonymous disabled, integrated windows enabled, basic authentication ticked, domain winbox.myhost.net -NSPI Interface registry entry added, ncacn_http:6004 The Problem -Outlook prompts for password, I enter myhost\zcferres and my password and it thinks for a minute. It does NOT prompt for PW again. -Connection status shows TCP/IP and Connecting.... (should be HTTPS?, no?) -Times out and throws an error that server is unavailable Seems working -Certificate is good, I can login to OWA and the certificate doesnt pop-up. After the certificate was offered by godaddy, I imported it on the server and saved it from there. Then I imported the PFX to my client and installed it as a Root certificate. I really don't think the certificate is the problem here, IE tells me the certificate is good without even prompting. -I am able to RPC Ping the server from the client -I am able to connect to the exchange box with outlook on the server using same outlook anywhere settings and also without outlook anyhere. -OWA works great from everywhere -I was able to connect to https://winbox.myhost.net/rpc/rpcproxy.dll (logged in and got blank screen with SSL lock and no prompts)Troubleshooting: rpcping -t ncacn_http -s winbox -o RpcProxy=winbox.myhost.net -P "zcferres,myhost.net,password" -I "zcferres,myhost.net,password" -H 2 -u 10 -a connect -F 3 -v 3 -E -R none RPCPing v2.12. Copyright (C) Microsoft Corporation, 2002 OS Version is: 6.0 RPCPinging proxy server winbox.myhost.net with Echo Request Packet Sending ping to server Response from server received: 200 Pinging successfully completed in 640 ms -I am also able to RPC Ping from the server itself. HTTP_ERR log shows 2007-11-30 03:43:08 65.24.67.227 16465 208.109.232.64 443 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?winbox.myhost.net:6004 - 1 Connection_Abandoned_By_AppPool DefaultAppPool 2007-11-30 03:43:08 65.24.67.227 16466 208.109.232.64 443 HTTP/1.1 RPC_OUT_DATA /rpc/rpcproxy.dll?winbox.myhost.net:6004 - 1 Connection_Abandoned_By_AppPool DefaultAppPool IIS log shows 2007-11-29 23:02:36 W3SVC1 208.109.232.64 RPC_IN_DATA /rpc/ rpcproxy.dll - 443 myhost.net\zcferres 65.24.67.227 MSRPC 200 0 0 Event Viewer shows RPC Proxy successfully loaded in Internet Information Services (IIS) mode 6.0. Seems Broken -Using http://support.microsoft.com/kb/831051 I was able to try 'How to Use Basic Authentication and SSL to Connect to the Store's Port'. So I did a RpcPing -t ncacn_http -s winbox -o RpcProxy=winbox.myhost.net -P "zcferres,myhost.net,password" -I "zcferres,myhost.net,password" -H 1 - F 3 -a connect -u 10 -v 3 -e 6001 -From this RPCPing (coming from client) I got an error Exception 1722 (0x000006BA) RPC Server is unavailable The RPC service cannot be contacted. You may receive this response because there are problems with the RPC Proxy server (if this is the case, you can use the -E argument to verify that the RPC Proxy server is available), because the service stopped on Exchange 2003 backend server (for example store), because the Exchange 2003 backend server is down, because the ValidPorts registry key does not permit access to this server, because the ValidPorts registry key does not permit this port, because you tried to to access the EMP when it was not published (neither the -e switch or port 593 were available), or because you tried to access UUID when EMP was not published (for example, you used the -a switch without port 593 being available.). This is pretty much all the info that I can think of right now, but if you need more shoot it my way and I will get it in here. Thanks for your help in advance! Zach