Re: SBS 2003 and Outlook RPC over HTTP issues
- From: "Gregg Hill" <bogus@xxxxxxxxxxx>
- Date: Tue, 25 Mar 2008 16:07:27 -0700
Ted,
As pointed out by others, port 80 does NOT need to be open, and yes, it is
FAR MORE of a risk than having SSL open. Port 80 is probably the
most-attacked port on the Internet.
Did you try Steve's suggestion to "Use https:// with the cert name you setup
in the CEICW."?
For example, if your MX record is "mail.yourdomain.com" and you have an A
record pointing that to your SBS, and you have port 443 open and forwarded
to your SBS, you should be able to have port 80 closed and use
https://mail.yourdomain.com/exchange to get to OWA.
On the LAN, can you go to https://servername/exchange and get to OWA? If
not, it will never work with SSL from the WAN side for RPC over HTTP.
Self-signed certificate or official SSL cert?
If you have a self-signed cert, re-run the CEICW and uncheck all the items
to allow via the Internet. Then re-run it, create a new web cert that
matches your MX record FQDN, and re-enable all the items you want via the
Internet.
Test it with https://mail.yourdomain.com/exchange to get to OWA.
Let us know how it goes.
Gregg Hill
"Ted" <Ted@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9BA0F1BD-DAA4-442C-829F-01893A44734B@xxxxxxxxxxxxxxxx
port 80 has to be open so users can get webmail, otherwise how in Gods
earth
are they going to get remote mail? i havent had any issues port
forwarding
this to my server it works fine, anytime a port is open it leaves a
security
risk. anytime a new user is assigned an account its a security risk,
any...need i go on...
"Colin" wrote:
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
.
- Follow-Ups:
- References:
- Re: SBS 2003 and Outlook RPC over HTTP issues
- From: Colin
- Re: SBS 2003 and Outlook RPC over HTTP issues
- From: Ted
- Re: SBS 2003 and Outlook RPC over HTTP issues
- Prev by Date: Re: SBS 2003 and Outlook rpc over http issue
- Next by Date: Re: HELP! Workstation on SBS Lan keeps losing connection
- 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
|
