Re: RPC Over HTTP

From: Les Connor [SBS MVP] (les.connor_at_DEL.cfive.ca)
Date: 02/11/04 

Date: Wed, 11 Feb 2004 09:04:30 -0600

Madison,

Think about it this way:

What URL do you use to access your SBS from a remote client ? In other
words, what do you type into IE to make a connection ?

For example:

You have a fixed public IP address for your SBS - 123.456.789
>From the internet, you can ping your server at 123.456.789
and/or
>From the internet, your server will respond to: "telnet 123.456.789 443" (or
whatever port you know is open)

then you can reach your SBS from the internet at this url:

https://123.456.789/remote or https://123.456.789/exchange.

In this case, you need to specify 123.456.789 as the FQDN when you run the
CEICW and create the certificate. Once the certificate is created, the first
time you connect from a remote client, you will receive a certificate
prompt. View, and Install the certificate.

If you have a registered domain name (company.com), and a dns record exists
that points to your fixed IP (as above), then you could use company.com in
place of the IP address. You could also have a new record created, such as
server.company.com that resolves to 123.456.789.

In this case, you could use server.company.com as the FQDN when you run the
CIECW, and from a remote client you would go to the url
https://server.company.com/remote .

The key here is that the name you specify when you create the certificate in
CIECW, and the url you use to access the server from the internet *must*
mach. 

--
Les Connor [SBS MVP]
-------------------------------------
SBS Rocks !
"Madison" <.> wrote in message news:u$3$qsK8DHA.2524@TK2MSFTNGP11.phx.gbl...
> Ray, Is "public" the key here??  I to have encountered the very same
issues.
> The cert name is we chose was different.  Everything else that uses the
cert
> is fine???  Outlook just keeps asking for PW over and over.
>
>
> --
> Sweet things happen on Friday!!!!
>
>
> "Ray Fong [MSFT]" <rayfong@online.microsoft.com> wrote in message
> news:UhjxlfK8DHA.2508@cpmsftngxa07.phx.gbl...
> > When you run CEICW, it will ask for the Web Certificate Name, change
that
> > to public IP.
> > Next, connect to the Remote Web Workplace, follow the step there again
> > (Some info will be difference based on the new name we use in CEICW).
> > Verify you have installed the "public IP" cert on the client, verify all
> > the steps you have followed there.
> >
> > Ray Fong
> > Microsoft SBS Product Support
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> >
> > >
> > >I've done the CEICW and very carefully followed the
> > >configuration instructions from the RWW link.  When I try
> > >to start the Outlook client it takes several seconds and
> > >responds with the login screen.  I enter the login
> > >credentials domain\username and password.  It tries for
> > >several more seconds and comes back with "unable to
> > >connect" "need to be online" etc, etc.  I have a full
> > >time broadband connection on the client end that works
> > >for everything else and I tried it with another client
> > >machine on a different full time broadband connection.
> > >Neither connects to the server even though I can do the
> > >https thing with IE.  There must be a secret button
> > >someone is not telling me about, I just don't get it.  I
> > >know this stuff and it is not working.
> > >>-----Original Message-----
> > >>If you run CEICW (ToDoList -> Connect to the Internet),
> > >you have the option
> > >>to publish RPC Over HTTP. That's all you need to do at
> > >the server side.
> > >>
> > >>As far as the client side, logon to https://FQDN/remote,
> > >click the link
> > >>Configure Outlook over the Internet. Follow the steps by
> > >steps guide.
> > >>
> > >>Ray Fong
> > >>Microsoft SBS Product Support
> > >>
> > >>This posting is provided "AS IS" with no warranties, and
> > >confers no rights.
> > >>
> > >
> >
>
>