Microsoft KB Archive/161489

{|
 * width="100%"|

XCLN: Troubleshooting Windows Client over Internet

 * }

Q161489

-

The information in this article applies to:


 * Microsoft Exchange Windows 3.x client, version 4.0
 * Microsoft Exchange Windows NT client, version 4.0
 * Microsoft Exchange Windows 95/98 client, version 4.0

-

SYMPTOMS
When the Microsoft Exchange client is connecting over the Internet, you receive a message that says "server cannot be found."

CAUSE
Due to firewalls or name resolution issues, the client is unable to attach to Microsoft Exchange Server.

WORKAROUND
To resolve this problem, you need to work on both the client and the server.

On the computer running Microsoft Exchange Server, perform the following steps:

 Check the "Services" file in \System32\Drivers\etc. This will show the port numbers currently in use. If you are using a packet filter, you can force Microsoft Exchange Server to use a fixed port for remote procedure calls (RPC). To do this, perform the following steps:

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT or Windows 2000, you should also update your Emergency Repair Disk (ERD).

 Start Registry Editor (Regedt32.exe).  Under the HKEY_LOCAL_MACHINE subtree, go to the following subkey: "SYSTEM\CurrentControlSet\Services\MSExchangeDS\Parameters"  On the Edit menuc, click Add and add the following information:      Name: TCP/IP port Type: REG_DWORD Value: "decimal".

You must also configure the port number in your packet filter.

NOTE: The  may be any number over 1024 and must be in     decimal format. In addition, the DS and IS Port Number must be different. For example: "TCP/IP Port"=dword:00000400(1024)

The number 1024 for the DS above is 400 in hexidecimal format.   For the Information Store, create a registry entry called "TCP/IP port" under the following key: "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\" This is a DWORD and the value is "decimal".

NOTE: The  may be any number over 1024 and must be in decimal format. In addition, the DS and IS Port Number must be different.

For example: "TCP/IP Port"=dword:00000402(1026)

The number used was 1026 for the IS, 402 in hexidecimal format. </li>  Add a registry entry called "TcpipClientSupport" under the following subkey: "HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/LSA" This is a DWORD; set it to Hex 1. </li> Quit Registry Editor.</li></ol> </li> Configure your packet filter to allow TCP connections to the ports mentioned above plus port 135 (for the RPC End-Point Mapper service) on the Microsoft Exchange Server-based server.</li></ol>

On the client:


 * 1) Edit the Lmhosts file to have an entry for the computer running Microsoft Exchange Server. For example: tcp/ip address servername #PRE #DOM:domain name 200.246.248.29 enterprise #PRE #DOM:training
 * 2) Edit the Hosts file to have an entry for the computer running Microsoft Exchange Server. For example: ipaddress 200.246.248.29 enterprise.sao.nutecnet.com
 * 3) On the Tools menu, click Services, click Exchange Server, click Properties, and click Advanced. Clear the "When Using the network" check box, under Encrypt Information section.
 * 4) Make sure TCP/IP is first in the Exchange binding order. This procedure varies for the different Windows clients: For 32-bit clients (Windows 95 clients and Windows NT clients):

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows NT. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

<pre class="FIXEDTEXT">  a. Start Registry Editor (Regedt32.exe).

<pre class="FIXEDTEXT">  b. Under the HKEY_LOCAL_MACHINE subtree, go to the following subkey:

"SOFTWARE/Microsoft/Exchange/Exchange Service Provider"

<pre class="FIXEDTEXT">  c. Make sure the RPCBindingOrder value has ncacn_ip_tcp listed first.

<pre class="FIXEDTEXT">  d. Quit Registry Editor.

<pre class="FIXEDTEXT">  For 16-bit clients (Windows 3.x clients):

<pre class="FIXEDTEXT">  a. Open Exchng.ini (in the Windows directory).

<pre class="FIXEDTEXT">  b. In the [Exchange Provider] section, make sure "Rpc_Binding_order=ncacn_ip_tcp."

REFERENCE
For additional information, please see the following articles in the Microsoft Knowledge Base:

Q149692 XCLN: Error Message When Clients Try to Connect via Internet

Q152725 XCLN: How to Connect over the Internet to an Exchange Server

Also see

"http://www.microsoft.com/exchange/techinfo/administration/55/Security.asp" Additional query words:

Keywords : kbusage

Issue type :

Technology : kbExchangeSearch kbExchange400 kbExchangeClientSearch kbZNotKeyword kbZNotKeyword2 kbZNotKeyword3 kbExchange400NT