Delay When Connecting MMC to Remote IIS Server (263117)
The information in this article applies to:
- Microsoft Internet Information Server 4.0
- Microsoft Internet Information Services 5.0
This article was previously published under Q263117 SYMPTOMS
When you connect to a remote Microsoft Internet Information Server (IIS) computer that has more than one network card using the Microsoft Management Console (MMC), a delay of approximately 30 seconds may occur on the first connection. Subsequent connections are much quicker.
CAUSE
The remote procedure call (RPC) returns the IP addresses for all of the network interface cards (NICs) on the IIS server. The list is tried in the order in which it is returned. If the first NIC returned is not reachable by the client where MMC is run, the process keeps trying the first address until 32 seconds have passed. After the timeout, it proceeds on down the list.
RESOLUTION
The order in which the list is returned is controlled by the binding order on the TCP/IP protocol. To alter the binding order on Microsoft Windows NT 4.0, follow these steps: - Open the network control panel on the IIS Server.
- Click the Bindings tab.
- Select Show Bindings for All Protocols.
- Expand the TCP/IP protocol.
- Highlight the NIC that you want at the top of the list, and then click Move Up until it is at the top of the list.
- Restart the IIS server.
To alter the binding order on Microsoft Windows 2000, follow these steps:
- Open the network control panel on the IIS Server.
- Click Advanced on the menu, and then select Advanced Settings.
- Highlight the NIC that you want at the top of the list, and then click the up arrow until the NIC is at the top of the list.
- Click OK.
REFERENCESFor additional information about network connection delays, click the article number below
to view the article in the Microsoft Knowledge Base:
288886 PRB: Delayed DCOM Activation on Multihomed Computers
Modification Type: | Minor | Last Reviewed: | 1/20/2006 |
---|
Keywords: | kbenv kbHardware kbprb KB263117 |
---|
|