Troubleshooting RPC Problems with Windows 3.x Client (154268)
The information in this article applies to:
- Microsoft Exchange Server 5.0
This article was previously published under Q154268 SUMMARY
This article lists steps to help you troubleshoot problems when you
attempt to use the Microsoft Exchange Windows 3.x client to connect to a
Microsoft Exchange Server computer using remote procedure call (RPC). The
following problems are discussed:
- The client cannot connect to the server on a Microsoft network.
- The client cannot connect to the server on a Novell NetWare network.
- The server cannot connect to the client.
- The client cannot open a public folder on the server.
- The client cannot connect to the server when you are using shared
installations of Windows and Microsoft Exchange.
MORE INFORMATIONThe Client Cannot Connect to the Server on a Microsoft Network
If you are unable to connect to a Microsoft Exchange Server computer on a
Microsoft network, the problem may be caused by any of the following
situations:
- The server is not available.
- The client or server is connected to a private network.
- The client and server are not using the same network protocols.
- There is a version mismatch between the client and server.
- The client is not configured properly.
- There is not enough free memory.
To work around this problem, use the appropriate method:
The Client Cannot Connect to the Server on a Novell Netware Network
If you are unable to connect to a Microsoft Exchange Server computer on a
Novell NetWare network, the problem may be caused by any of the following
situations:
- The server is not configured to support NetWare clients.
- The Nwipxspx.dll or Nwcalls.dll file does not exist on the client or
is not located in a folder that is included in the PATH environment
variable.
- There is a version mismatch between the client and server.
- There is a frame type mismatch between the client and server.
- There is not enough free conventional memory on the client.
- The client or server is unable to log on to a Service Advertising
Protocol (SAP) computer.
To work around this problem, use the appropriate method:
The Server Cannot Connect to the Client
If the client is able to connect to the server, but the server is unable
to connect to the client, the client may not be configured for enough IPX
sockets or SPX connections.
To work around this problem, increase the IPX Sockets and SPX Connections
settings in the Protocol IPXODI section of the Net.cfg file. Both
settings should be at least 50.
The Client Cannot Open a Public Folder on the Server
If the client is able to connect to the server, but it cannot open a
public folder on the server, the problem may be caused by either of the
following situations:
- The client is not configured for enough IPX sockets or SPX connections.
- One or more necessary services are not running on the server.
To work around the problem, use the appropriate method:
- Increase the IPX Sockets and SPX Connections settings in the Protocol
IPXODI section of the Net.cfg file. Both settings should be at least
50.
- Verify that all the necessary services are running on the server.
The Client Cannot Connect to the Server When You Are Using Shared
Installations of Windows and Microsoft Exchange
If the client cannot connect to the server and you are using shared
installations of Windows and Microsoft Exchange, the RPC_REG_DATA_FILE
setting in the [RPC Runtime Preferences] section in the Win.ini file is
invalid.
To work around this problem, modify the RPC_REG_DATA_FILE setting so that
it includes the full path to a valid Rpcreg.dat file that is not read-
only. In addition, verify that the root folder on the drive on which the
Rpcreg.dat file is located is not read-only.
NetWare is manufactured by Novell, a vendor independent of Microsoft; we
make no warranty, implied or otherwise, regarding this product's
performance or reliability.
Modification Type: | Minor | Last Reviewed: | 4/28/2005 |
---|
Keywords: | kb3rdparty kbinfo kbnetwork KB154268 |
---|
|