Re: Outlook 2007 rpc over http


Hi Ian:

You don't need port 80 forwarded to your SBS for anything, and it should not
be. If you are hosting a public web site, that is a bad idea.

The cert has to be imported into the Vista cache by starting IE with RunAs
Administrator. You should only have to do this one time.

Are other remote systems, of any version, able to connect with Outlook
Anywhere? The setup requires that you follow the instructions to the
letter. If you have done this before, then I guess you know that, but the
first time it is a bit screwy as you tend to over read the instructions.

Here is a good article for Vista and OL 2007 in SBS 2003:

http://www.microsoft.com/downloads/details.aspx?FamilyID=9bf2f1e4-1b2c-471b-a284-e0c8c169fac3&displaylang=en

As for the rest of the ports:

SMTP 25 - Simple Mail Transfer Protocol
HTTP 80 - Home Page Web

SSL 443 - Home Page Web Secured

HTTP2 444 - Second SSL Secured on alternate port for SharePoint

PPTP 1723 - VPN Connections

RDP 3389 - Remote Desktop Protocol (only needed for direct access, if using
RWW website, only 4125 is needed)

RWW 4125 - Remote Web Workplace

Optional:

POP3 110 - If using POP3 mail connections

IMAP 143 - Good for iPhones (1st Generation)

IMAP SSL 993 - Even better for iPhones (1st Generation)


--
Larry Struckmeyer
Get your SBS Health Check
at www.sbsbpa.com


"Ian Zahn" <IanZahn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EE83ADE4-67B3-4ACC-89B1-FCFFBB63D3BC@xxxxxxxxxxxxxxxx
I have a client that has the following situation.
SBS2003 with SP 2 for exchange, client is windows vista SP2 with outlook
2007 SP2.
I have followed the instructions on the remote website. but i cannot get
the
outlook client to connect via RPC. I have rerun the Internet connection
wizard, recreated web certificate. Even after I install the certificate
to
the workstation I still get a certificate error.
Do I have to purchase a certificate for them? I was under the impression I
didn't.
I have port 443 and 80 forwarded to the SBS. Just running out of options.
I have read a few post in the discussions but I still cannot get it to
connect.

I get the certificate error as well when going to OWA as well. Not sure of
my next option.

Any pointers appreciated.


.

Relevant Pages

  • Re: Not able to connect to SBS using both domain mane or IP remote
    ... >>> connection using SBS. ... >>> Certificate but it's still not working. ... >>> but not to the server or any of the services. ... >> Your server is answering on port 25, ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Outlook RPC over HTTP issues
    ... Your cert is barfing due to the fact that the names do not match. ... some weird certificate error now though...if you want to see it ... As pointed out by others, port 80 does NOT need to be open, and yes, ... record pointing that to your SBS, and you have port 443 open and ...
    (microsoft.public.windows.server.sbs)
  • Re: Problems applying godaddy SSL certificate to WSS 3.0 website for external access
    ... The side-by-side installation you followed is only for SBS 2003 users and therefore problems after doing it apply only to SBS 2003 users. ... > websites are using the self signed SSL certificate generated within SBS with the same name. ... I used a self signed certificate that I ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Not able to connect to SBS using both domain mane or IP remote
    ... The way I had things setup worked before, as far as for the www record ... >> I setup SBS 2003 Standard and everything was working fine, ... >> " Cannot manage Certificate Services. ... > Your server is answering on port 25, ...
    (microsoft.public.windows.server.sbs)
  • Problems applying godaddy SSL certificate to WSS 3.0 website for external access
    ... SBS NG but feel it may be more appropriate to post here. ... I've got all my sharepoint services websites published for external access ... that I can use to access my SSL site using the below listed links. ... I went to godaddy and requested a web certificate. ...
    (microsoft.public.sharepoint.windowsservices)