RPC over HTTP problems

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I'm starting a new thread on my RPC over HTTP problem ( here's the old
thread:
http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_thread/thread/2c6231eb1a48c87e/8daf572c86cf2ceb?lnk=st&q=author%3Achief120%40gmail.com#8daf572c86cf2ceb
). Right now I'm trying to enable RPC over HTTP on Small Business
Server 2003 so Outlook clients can access their email away from the
office. When configuring the server I went through the "Connect to
the Internet" wizard but didn't select "Outlook via the Internet."
Later, I discovered this Technet article on deploying RPC over HTTP
for SBS2003 ( http://technet.microsoft.com/en-us/library/bb123622.aspx
). I went through the "Connect to the Internet" wizard again with the
only difference being I checked the box for "Outlook via the
Internet." I then tried going to https://mail.example.com/rpc but it
wouldn't accept my credentials. However, I could authenticate to
https://mail.example.com/rpc/rpcproxy.dll.

Tonight I went through this Technet article on troubleshooting RPC
over HTTP ( http://technet.microsoft.com/en-us/library/bb124649.aspx
). The rpcproxy.dll file is there and I can access it by going
directly to the file from a client computer in Internet Explorer. IIS
is running on the server as I can access https://mail.example.com/exchange.
IIS has the self minted SSL cert associated with this IIS web site.
The IIS RPC virtual directory matches what Technet specifies and is
set to use basic authentication. IIS Proxy Server Extension lists
rpcproxy.dll as allowed. One thing I did note was that
HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy also had port 593
listed for both the NetBIOS and FQDN of the server (
http://technet.microsoft.com/en-us/library/aa998910.aspx ).

What could be holding me back on this? Should I go through the
"Connect to the Internet" wizard for a third time to see if that fixes
it? It feels like all the parts are there, there's just some checkbox
or setting that's not enabled.


Matthew
.

Relevant Pages

  • Re: RPC over HTTP Question
    ... allow specific traffic transfer and publish some web services to internet. ... On the Web Server Certificate page, ... The wizard automatically configures Exchange, IIS, and the RPC proxy ... >Subject: Re: RPC over HTTP Question ...
    (microsoft.public.windows.server.sbs)
  • Re: Internet syncronisation failed after installing security update
    ... which one is responsible) iis is ignoring the PUT-command via http. ... messing up the access replication. ... but the base problem is the same: "internet ...
    (microsoft.public.access.replication)
  • Re: Internet syncronisation failed after installing security update
    ... after the latest updates our internet> syncronisation behaved the same...not working anymore. ... after the newest patches iis is ignoring the PUT-command via http. ... before the patches were installed> the log shows http response 200 and 201 for the upload of tempfiles and> execution of mstrai40.exe. ... that leads to the conclusion that> the latest updates shut down the PUT functionality via http and by the way> messing up the access replication. ...
    (microsoft.public.access.replication)
  • Re: Outlook 2003 RPC over HTTP everywhere disadvantages
    ... I think RPC over HTTP is great for external access, ... recommend running it when inside your corporate LAN, for a start I find it a ... internet, the normal place for this is in the DMZ. ...
    (microsoft.public.exchange.admin)
  • Re: RPC over HTTP
    ... problem is using RPC over HTTP from somewhere over the internet to your SBS ... GRE is only for VPN and has nothing to do ...
    (microsoft.public.windows.server.sbs)