I recently installed the Win95 Exchange client on two Pentium computers. One system
comes up instantaneously. The other takes 15 minutes to come up.
After searching the MSKB I was able to reference an article (Q136516) which
describes this problem as attributable to the "RPC binding order."
The problem is attributed to the MS Exchange client stepping through all of
the protocols until it has established communication with the server. This
takes a considerable amount of time and the search proceeds according to the
"RPC binding order." Supposedly, this delay would not occur if the first
protocol happened to be the protocol in use by the server. The proposed
solution to the problem assumes that the MS Exchange Client setup (which
resides on the server) is specifying the protocols in the wrong order at
the time of installation. The proposed solution is to edit the Setup on
the Exchange server to "modify the RPC protocols."
I find it hard to believe that this is a problem in the setup because
it is only occuring on one client... and all of the clients have been
installed from the same copy of setup that resides on the Exhange 4.0 server. The
client machine is an HP XM4 Pentium/Pro 200 with an on-the-motherboard
10BaseT PCI ethernet interface. All other network interactions occur at normal
speed and once the Exchange Client starts up there it runs at normal speed.
It seems as if there should be a way to get into some .INI file or .CFG
file to edit the RPC binding order. Most other clients on the network do not have
the integrated PCI ethernet interface, but have an ISA 3COM 3c509B card.
Any thoughts, suggestions, workarounds or solutions would be greatly appreciated.