Re: SBS 2003 and Outlook RPC over HTTP issues
- From: "Gregg Hill" <bogus@xxxxxxxxxxx>
- Date: Sun, 30 Mar 2008 10:39:42 -0800
Ted,
Yes, the article is incorrect in stating that port 80 is needed.
His statement, "The only ports you'll need to open on your firewall are TCP
80 and, if using SSL, TCP 443" should read, "The only ports you'll need to
open on your firewall are TCP 80 if you are completely nuts and want to get
hacked, OR (not and) if using only SSL as you should, ONLY open TCP 443 and
CLOSE port 80.
As far as I know, the only inbound ports you need open for full
functionality of Exchange, RWW, OWA, OMA, and SharePoint via the Internet
are:
25 SMTP
443 SSL (RWW, OWA, OMA)
444 if you want SharePoint via the web
4125 RDP in RWW
Gregg Hill
"Ted" <Ted@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C2DCD4EE-659F-4F71-9534-96DBDB4BF4CD@xxxxxxxxxxxxxxxx
OK I have this working, it was an issue with IIS the setting "Accept
Client
Certificates" was checked and I had to set that to "Ignore Client
Certificates" and presto everything was peachy. When CRM was installed it
might have changed that I am not sure.
Also,
The link http://www.petri.co.il/testing_rpc_over_http_connection.htm
states
that port 443 and port 80 must be open to use RPC over HTTP. Is this a
mistake, I know that you all have said that you do not need 80 open.
Thanks everyone for your help....let me know on the 80, I did try it and
was
unable to connect when I did disable 80.
"spm" wrote:
Ted wrote:
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
From what you have reported it is difficult to say where the issue is
rooted. It may be a certificate issue, but you haven't given enough
detailed information to conclude reliably. Here are some resources that
may help:
Testing RPC over HTTP/S:
http://www.petri.co.il/testing_rpc_over_http_connection.htm
Using RPC Ping Utility to troubleshoot:
http://support.microsoft.com/kb/831051
--
Regards,
Steve.
.
- Follow-Ups:
- Re: SBS 2003 and Outlook RPC over HTTP issues
- From: Ted
- Re: SBS 2003 and Outlook RPC over HTTP issues
- From: kj [SBS MVP]
- Re: SBS 2003 and Outlook RPC over HTTP issues
- References:
- Prev by Date: Re: Can't access shared resources via VPN
- Next by Date: Re: Can't access shared resources via VPN
- Previous by thread: Re: SBS 2003 and Outlook RPC over HTTP issues
- Next by thread: Re: SBS 2003 and Outlook RPC over HTTP issues
- Index(es):
Relevant Pages
|
