I've been trying to setup RPC over HTTP between a SBE 2003 Server and an Outlook 2003 client running XP.
I've got a pix doing firewalling that only allows port 80 & 443 (I've tested this with telnet on port 443. OWA works just fine, I got a wildcard cert that will do the whole domain.
Both server and client is updated with the latest patches and updates, I've ran through the tutorials and how tos from this site. Rebooted the server after the configuratiion.
Outlook is configured as per the tutorials, I can get to a login window. Asking me for a username and password. I've tried all the various logins possible (username@domain.com, servername\username, domainname.com\username) and keep getting rejected by the server.
If I log in with OWA the username and password works perfectly.
I have no idea what the problem is. Has anyone experienced this problem before?
The Connection Status shows the client trying to open HTTPS to the correct URL, only to drop and disconnect when ever I try to log in. I'm sure the password is correct because it works in OWA.
Posts: 3004
Joined: 9.May2007
From: India
Status: offline
hi, Try this Control Panel => Mail Setting => create a new profile under that microsoft Exchagne Server : Give your exchange server FQDN and test and then click on more setting... then go to conneciton tab => click rpc over https configuration then go to https://typeyourowaurl and leave msstd blank and click ok and finish it.
Go to regedit... HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\RPC Note : if you don't have RPC folder under outlook please create it.
Then create a Reg_dword value : EnableRPCtunnelingUI and set it to 1
I really don't get this problem. I can do a telnet session on 443 and I can see the connection status attempting to open to my url with a HTTPS request.
If I get prompted with a un/pw that means I've openned session to the server right?
I can log in with OWA, why can't I log in with the same credentials with Outlook RPC?
I wonder if my problem is the fact that I've used the tutorials and made changes to the registry and various other changes that were explained in the tutorials, instead of just using the SBS wizard?
I think I'm starting to understand what the problem is now. It seems that the RPC component on the server isn't working properly.
I've run a "rpcdump /s servername /v /i /p ncacn_http" and get back "0 Registered endpoints found" followed by a "rpcdump.exe - Application Error, The exception Integer division by zero. (0xc0000094) occurred in the application at location 0x01001e30. Click on OK to termiate the program, Click on CANCEL to debug the program.
From the client PC, when I run "rpcping -t ncacn_http -s FQDN -P user,domain,password -I user,domain,password -u 10 -a connect -H 1 -F 3 -e 6001" -> I get back, "Exception 1722 (0x000006BA)
So basically my RPC component isn't working properly. So I check the location of the RPCProxy.dll locations, the registry settings, the cert, the IIS security settings etc. Basically everything what I did during the install process and everything checks out.
Posts: 3004
Joined: 9.May2007
From: India
Status: offline
hi mate,
I guess we need to get a expert who knows about configuration even i m also clueless here, I tried rpc over https going the link which i had forwarded to you and it is working for me.
Let see and kindly update the portal if you come across with any solution
Posts: 4093
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline
How did you setup RPC over HTTPS on the server? Did you do it manually using the registry changes or did you enable it using the wizards? If you did it manually then that was your first mistake.
Rule number one with SBS. Use the wizard. If there isn't an wizard then you probably haven't looked hard enough.
Re-run the Connect to the Internet and Email wizard from the Server Management console and ensure that RPC over HTTPS - Outlook over the Internet - is enabled. Next. On the client, browse to https://host.domain.com/rpc If you get an SSL certificate prompt, then the feature will not work. You should get an authentication prompt. Don't try and authenticate, as it will always fail.
Yeah, I think my mistake was that I didn't use the wizard.
Anyway, I've managed to finally solve the problem.
I realized that the problem was related to the RPC component not working. So I,
1) removed the RPC component, restore IIS config to a earlier config, added the CA component (not sure if this was necessary because I had a wildcard cert and didn't need to generate a cert but did this way), and rebooted
2) set it up again, after a few reboots and the problem was fixed.
If anyone encounters the same problem, the poster above was correct in saying, "use the wizard"!
If you using RPC over HTTP on server 2003, you "MUST" apply a commerical certificate for exchange. If you using build in (self-signed) certificate. it WILL NEVER work.
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2003] >> Exchange 2003 SBS >> RPC over HTTP 
RPC over HTTP - 
RE: RPC over HTTP - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
