Re: SBS 2003 and Outlook RPC over HTTP issues

Hi,

I haven't got the answer to your problem but I'd strongly recommend closing port 80 on your firewall, it is definitely not needed and only lowers your security.

Regards Colin.

"Ted" <Ted@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:ABD35145-C381-4DF7-A583-03AE7BEDE6BF@xxxxxxxxxxxxxxxx
Hi,

SBS 2003 that has been running for 3 years with minimal issues. I have
setup SBS and configured exchange on this machine years ago. Recently I
tried to configure an Outlook 2003 client on Winxp with all updates to
connect via RPC over HTTP with no luck.

I have about 20 of these SBS machines at other locations and have never had
an issue getting RPC over HTTP to work. I re-ran the email connection wizard
with no luck. Checked all ports on the firewall and 80 & 443 are forwarding
to the server. I can initiate a session via HTTP only which works fine.
However I can not get RPC to work. I have tried this on several machines
and it is most definitely something that is screwed up on the server. I know
for a fact that at one point this was working. I did install CRM about 2
years ago but the customer didnt want to use this after a while so I
uninstalled this. I am thinking that the CRM did something to my box but I
cannot seem to figure this out. I even tried my own laptop which I use to
test other customers machines with no luck. I am also unable to get any
windows mobile devices to connect either. It may be an issue with my
certificate, authentication is setup correctly. I checked the RPC
permissions in IIS and it is setup to use basic authentication for RPC
requests.

Any ideas? Both the server 2003 and the XP pro clients are fully patched,
office 2003 is up to SP3. I have also tried to run from a Vista client with
office 2007 and it still is failing. The windows mobile device is version 5
with activesynch.

Any help is appreciated greatly...

Ted

.

Relevant Pages

  • Re: SBS 2003 and Outlook RPC over HTTP issues
    ... the article is incorrect in stating that port 80 is needed. ... "The only ports you'll need to open on your firewall ... that port 443 and port 80 must be open to use RPC over HTTP. ... I have about 20 of these SBS machines at other locations and have ...
    (microsoft.public.windows.server.sbs)
  • RE: [fw-wiz] RPCs over HTTPS through the firewall
    ... >> it matter much if we add RPC to the sludge? ... > a similar risk profile, although encrypting traffic over 443 ... of the firewall admin's major bugbears. ...
    (Firewall-Wizards)
  • Access limitations(?), and moving to a simple LAN
    ... both machines were able to ping the ... >> couldn't see shares defined on the RPC. ... > connection will set the default route to the modem so everything goes ... and from each machine I can ping all three devices. ...
    (comp.sys.acorn.networking)
  • Re: Turning external RPC off
    ... the internal network, and there's no firewall to stop it from spreading. ... The answer about using a firewall if you want to block RPC for external ... They do tell you how to disable DCOM over RPC if you had some good reason ...
    (microsoft.public.security)
  • Re: SBS 2003 and Outlook RPC over HTTP issues
    ... SBS 2003 that has been running for 3 years with minimal issues. ... all updates to connect via RPC over HTTP with no luck. ... I have about 20 of these SBS machines at other locations and have ... be an issue with my certificate, authentication is setup correctly. ...
    (microsoft.public.windows.server.sbs)