Failed Outlook Connectivity Test

I am running an Outlook Connectivity test using the Microsoft Remote Connectivity Test and it seems to fail on the last test. We are running Windows Server SBS 2003. Does anyone have any suggestions?

The HTTP authentication test failed.
       
      Additional Details
       
An HTTP 403 forbidden response was received. The response appears to have come from IIS6. Body of the response: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>You are not authorized to view this page</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=Windows-1252">
<STYLE type="text/css">
BODY { font: 8pt/12pt verdana }
H1 { font: 13pt/15pt verdana }
H2 { font: 8pt/12pt verdana }
A:link { color: red }
A:visited { color: maroon }
</STYLE>
</HEAD><BODY><TABLE width=500 border=0 cellspacing=10><TR><TD>

<h1>You are not authorized to view this page</h1>
The Web server you are attempting to reach has a list of IP addresses that are not allowed to access the Web site, and the IP address of your browsing computer is on this list.
<hr>
<p>Please try the following:</p>
<ul>
<li>Contact the Web site administrator if you believe you should be able to view this directory or page.</li>
</ul>
<h2>HTTP Error 403.6 - Forbidden: IP address of the client has been rejected.<br>Internet Information Services (IIS)</h2>
<hr>
mail2clkAsked:
Who is Participating?
 
mail2clkAuthor Commented:
If I choose basic as the authentication method then the error is


      Attempting to ping the MAPI Mail Store endpoint with identity: server.mydomain.local:6001.
       The attempt to ping the endpoint failed.
        Tell me more about this issue and how to resolve it
       
      Additional Details
       
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
Elapsed Time: 3037 ms.
0
 
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
This is caused if you have IIS configured to reject connections from specified domains or IPs.  There is a good document from Microsoft which explains this:

http://support.microsoft.com/kb/248043

Follow the document and add required domains/IPs to the allowed list (or remove them from the reject list).
0
 
mail2clkAuthor Commented:
I am now down to one error

       
Not all the required authentication methods were found.
Methods Found: Basic
Methods Required: NTLM
HTTP Response Headers:
MicrosoftOfficeWebServer: 5.0_Pub
Content-Length: 1656
Content-Type: text/html
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
Go to IIS and change Authentication from Basic to NTLM.
0
 
mail2clkAuthor Commented:
with NTLM

       
      Additional Details
       
Not all the required authentication methods were found.
Methods Found: Basic
Methods Required: NTLM
HTTP Response Headers:
MicrosoftOfficeWebServer: 5.0_Pub
Content-Length: 1656
Content-Type: text/html
Date: Mon, 06 Oct 2014 20:03:17 GMT
Server: Microsoft-IIS/6.0
0
 
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
Sorry, leave both Basic and Windows Authentication enabled.
0
 
mail2clkAuthor Commented:
This is the error I received

Attempting to ping the MAPI Mail Store endpoint with identity: server.mydomain.local:6001.
       The attempt to ping the endpoint failed.
        Tell me more about this issue and how to resolve it
       
      Additional Details
       
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
Elapsed Time: 3312 ms.
0
 
mail2clkAuthor Commented:
I changed the valid ports to 100-6100

Open Registry Editor on the Client Access server or on the front-end server, and verify that the ValidPorts registry value exists under HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\Rpcproxy. Also confirm that the key includes the NetBIOS and FQDN for all mailbox servers and for each required port (that is, for ports 6001, 6002, and 6004).
0
 
mail2clkAuthor Commented:
Troubleshoot name resolution, and verify that the server acting as the RPC proxy can correctly resolve the internal fully-qualified domain name (FQDN) of the mailbox server or of Exchange 2003.

I can ping and do a nslookup on server.mydomain.local
0
 
mail2clkAuthor Commented:
To test endpoint connectivity, open a Telnet session on the Client Access server or on the front-end server, and then Telnet to each port on the mailbox servers (that is, on ports 6001, 6002, and 6004).

I can telnet to these ports from a client computer
0
 
mail2clkAuthor Commented:
I managed to resolve the issue by following the article below.

 http://social.technet.microsoft.com/Forums/exchange/en-US/be2e134b-9334-47ca-90cc-2c5ac19a6c43/exchange-outlook-anywhere-does-not-work?forum=exchange2010


HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy



Value name: ValidPorts

Value data: ExchangeServer :6001-6002; ExchangeServerFQDN :6001-6002; ExchangeServer :6004; ExchangeServerFQDN :6004


Note:   * ExchangeServer should be the NetBIOS name of Mailbox server.

   * ExchangeServerFQDN should be the fully qualified domain name (FQDN) of Mailbox server.
0
 
mail2clkAuthor Commented:
It solved my problem.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.