Re: SBS 2003 and Outlook RPC over HTTP issues
- From: "Gregg Hill" <bogus@xxxxxxxxxxx>
- Date: Sun, 30 Mar 2008 10:06:43 -0800
Ted,
Port 80 IS NOT NEEDED. All of us would not be saying that if it were needed!
Something else is still wrong with your server. If your server is set up
properly with SSL required, and you still have port 80 open, entering
mail.dds1978.com/exchange into a browser should immediately go to
https://mail.dds1978.com/exchange. Your OWA does not come up if I enter only
mail.dds1978.com/exchange (and port 80 appears to be open because telnet
answers to a blinking cursor).
If I temporarily open port 80 on my router and go to
mail.mydomain.net/exchange, it immediately flips over to the SSL site.
I run my systems with port 80 closed.
I just remembered that I somehow hosed OWA about four years ago, and Ray
Fong (MSFT) recommended recreating OWA.
Here are his steps, which correspond to Method 3 in this article:
http://support.microsoft.com/kb/883380/en-us
********************************************
Ok, let's recreate the OWA
1. Go to IIS, right-click servername (local computer), Properties.
Backup/Restore Configuration to save a copy of IIS settings
2. Expand servername (local computer), Web Sites, Default Web Site.
3. Delete Exadmin, Exchange, ExchWeb, Microsoft-Server-ActiveSync, OMA (Do
Not delete exchange-oma)
4. Stop IISAdmin service
5. Make a backup of WINDOWS\system32\inetsrv\MetaBase.xml
6. Open MetaBase.xml with Notepad.
7. Locate the following object where ID = 61472
<IIsConfigObject Location
="/LM/DS2MB/HighWaterMarks/{57F70E62-7E37-472B-A9F0-3BE08883AC5A}">
<Custom
Name="UnknownName_61472"
ID="61472" (<---- This one)
Value="53322"
Type="STRING"
UserType="IIS_MD_UT_SERVER"
Attributes="NO_ATTRIBUTES"
/>
8. Change the Value to "0". Your original number will not be "53322".
9. Save the file.
10. Restart all the services stop by IISAdmin
11. Restart Exchange System Attendant
12. Run CEICW (ToDoList -> Connect to the Internet). Make sure you select
Enable Firewall.
After the changes, close and reopen the snapin and try OWA again.
Ray Fong
Microsoft SBS Product Support
This posting is provided "AS IS" with no warranties, and confers no rights.
********************************************
I recommend rebuilding OWA, as it may fix your other problem as well
(needing port 80). Sorry I did not remember this issue sooner!
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: Gregg Hill
- Re: SBS 2003 and Outlook RPC over HTTP issues
- References:
- Prev by Date: Brooktrout TruFax 200 drivers
- Next by Date: Re: SBS 2003 and Outlook RPC over HTTP issues
- 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
|
Loading
