Re: Outlook RPC over HTTP

Hi Lanwench

Thanks for your post.

We havent created any certificates manually and have never assigned
Publishing.Domain.Local as a certifiicate. The only certificate setup
before was one through CEICW when we had an IP address as the FQN which was
changed to the Remote.Domain.co.uk reciently through CEICW.

Regards

Simon


"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:eancXJW9GHA.3264@xxxxxxxxxxxxxxxxxxxxxxx
In news:OkCKoAV9GHA.3264@xxxxxxxxxxxxxxxxxxxx,
Ben <Ben@xxxxxxxxxxxxxxxxxxxxxxxx> typed:
Hi

Thanks for your posts.

Thanks for your advice on the hard disk space, we have squeezed
everything off the drive, moved the last item that I could think of
last week, sbsmonitoring, to recover an extra 400mb. Looking forward
to the new server!

My appologies it was connected via TCP/IP, I had fast networks
unchecked in the HTTP setup. Now its checked it does not connect VPN
or otherwise. My appologies for any confusion.

In case it matters i have gone into IIS on the Server and checked the
server certificiate on the RPC site, it is setup as
Publishing.Domain.Local rather than that setup in CEICW:
Remote.Domain.co.uk

You need to use the CEICW. I'd undo whatever you did....SBS is incredibly
wizard-centric, and you are likely to botch stuff if you try to avoid the
wizards for most tasks.


Thanks
B


"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:OIupn6T9GHA.1492@xxxxxxxxxxxxxxxxxxxxxxx
In news:%23gNDaTT9GHA.3916@xxxxxxxxxxxxxxxxxxxx,
Ben <Ben@xxxxxxxxxxxxxxxxxxxxxxxx> typed:
Hi

Thanks for all your posts, from the top:

We dont have SP1 because it was an OEM install with a tiny 12gb

That's not tiny :)


partition which is boarding on 3/4GB free and are worried that it
will consume more space.

Nah. But you should move all your data (user shared folders,
clientapps, Exchange dbs/logs) to another drive/partition.



We are soon(ish) to install new SBS
hardware and use this machine (with more approprate partitioning) as
a remote office machine. SP1 will be installed on this then.

OK.



The certificate is installed (no red cross on certificate or
warnings).
Principal Name For Proxy Server now as below but still no luck:
msstd:remote.ourdomain.co.uk

We actually have the machine connected over VPN when testing (also
testing whilst not connected over VPN) is this as good as on the
LAN?

Well, it shouldn't matter, if (as you said) you'd set it to use
RPC/HTTP over both fast & slow connections.


I have run the CEICW and verified that OL over the Internet is
enabled.
Current situation: when connected to LAN over VPN I connect to
exchange but I think it is connecting over TCP/IP.

You can tell - hold CTRL and then right-click the OL icon in the
system tray, and check the connection status.

When disconnected
from VPN it repeatedly prompts for the username / password (i enter
Domain\Username and pw) but does not connect.

I would test this from a remote location, no VPN, with a new Outlook
profile.



Thanks
B


"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:%23zAvvwS9GHA.1808@xxxxxxxxxxxxxxxxxxxxxxx
Inline -

In news:%237WRnfF9GHA.3916@xxxxxxxxxxxxxxxxxxxx,
Ben <Ben@xxxxxxxxxxxxxxxxxxxxxxxx> typed:
Hi

We have a SBS 2003 (no service pack),

Why not?

running Exchange 2k3 SP2, ISA
2000.
We are having problems configuring Outlook to Communicate with
Exchange over HTTP.

We have configured the subdomain Remote.OurDomain.co.uk to point
to our server, we have a server SSL certificate configured for
https://Remote.OurDomain.co.uk and our client has the reletive
client cert, the domain is in the Intranet Site List on the client
and can browse to OWA & remote web workplace.

So the user went to https://Remote.OurDomain.co.uk/remote or
/exchange, and then *installed* the certificate, right? Didn't just
accept it?

I get the response "Forbidden: Read access is denied." when I goto
https://remote.ourdomain.co.uk/rpc which i hear is correct.

Nah.


I have configured Outlook as below:


Exchange Server: ourserver.ourdomain.local

That's good.

Username: my username

Exchange over the Internet Settings:
Checked : conect to my Exchagne mailbox using HTTP

Proxy Setttings:
URL: remote.ourdomain.co.uk
connect using ssl only: Checked
mutually authenticate the sesssion when connecting with SSL:
checked Principal Name For Proxy Server:
msstd:publishing.MyDomain.local

Nope....this is the problem. That should be:
msstd:remote.ourdomain.co.uk



On Fast Networks... Checked
On Slow Networks... Checked

Proxy Auth: Basic Auth

That's all good.



When I open outlook i get prompted for my username & password a
number of times and then it says disconnected.

Any advice would be much appreciated

Try fixing the proxy & try again.



Thanks
B





.

Relevant Pages

  • RE: CEICW fails on create on create secure web site configuration
    ... In the "Component Selection" page, change Action to Reinstall for Server ... Restart SBS and rerun CEICW. ... Delete SBS CompanyWeb Listener and SBS Web Listener ... On the "Web Server Certificate" page, choose to create a new Web server ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and self signed SSL certificate
    ... In CEICW, what did the Web server certificate page show: ... then when I click on the RWW I get a security warning about ...
    (microsoft.public.windows.server.sbs)
  • Re: CEICW and certificate FQDN
    ... CEICW still produced errors. ... CEICW was able to run and create the certificate ... Downloading and Installing Windows Small Business Server 2003 Service Pack ... Make sure your SBS internal and external network interface DNS is ...
    (microsoft.public.windows.server.sbs)
  • RE: 500 Internal Server Error
    ... I rerun CEICW according to your suggestion and everything works again great. ... Do you use self-singed certificate or commercial certificate? ... Please open SBS 2003 Server Management, ... List, click "Connect to the Internet" to bring up CEICW, click Next, select ...
    (microsoft.public.windows.server.sbs)
  • RE: CEICW Error, Web Certificate
    ... Server 2003, Premium Technologies ... Make sure your SBS internal and external network interface DNS is ... Restart SBS and rerun CEICW. ... certificate and then type the public FQDN or IP ...
    (microsoft.public.windows.server.sbs)
Loading