Intermittent error messages from Outlook 2003 saying that "Outlook is trying to retrieve data from the Microsoft Exchange Server {server name}"
We have recently changed telecom providers. Since then, most of our users get the above-mentionned Outlook error message. Outlook reconnects immediately, but the performance is significantly affected. These problems did not occur before the telecom switch.
The Exchange server is a virtualised server which runs out of our colocation facility. It uses Exchange 2000 and our clients use Outlook 2003. We have installed Outlook 2003 on another virtual server at the same physical location and running on the same blade server to test whether this client would experience the same problems and it has not.
From our remote location, we have pinged the exchange server and got no packet loss. Other network tasks such as printing and moving files work without problem.
I reviewed posts on expert-exchange relating to my problem but could not find any that dealt with a change in telecom provider or equipment.
Does anyone have an idea where to look?
The Exchange server is a virtualised server which runs out of our colocation facility. It uses Exchange 2000 and our clients use Outlook 2003. We have installed Outlook 2003 on another virtual server at the same physical location and running on the same blade server to test whether this client would experience the same problems and it has not.
From our remote location, we have pinged the exchange server and got no packet loss. Other network tasks such as printing and moving files work without problem.
I reviewed posts on expert-exchange relating to my problem but could not find any that dealt with a change in telecom provider or equipment.
Does anyone have an idea where to look?
Ubertam
Did you change your bandwidth? I get that error with users that have huge mailboxes or if I'm opening multiple mailboxes. This could easily happen if, say, you went from a 100 Mbit to 10 Mbit connection, etc.
I have resolved this on many systems in the past by hard coding the NIC on the Exchange server to that of the network speed.
Typical procedure I take is update the NIC drivers on the Exchange box and go into the config and lock it down to 1GB if a GB network or 100MB Full Duplex. If possible I take another step on the switch and lock that port to the speed of the network. At times servers have issues with the auto negoitation...
Typical procedure I take is update the NIC drivers on the Exchange box and go into the config and lock it down to 1GB if a GB network or 100MB Full Duplex. If possible I take another step on the switch and lock that port to the speed of the network. At times servers have issues with the auto negoitation...
ASKER
We have not decreased the bandwith. For one site, we have in fact increased in from 10 MBits to 100 Mbits.
Following EndureKona's post, we have hardcoded the NIC on the Exchange server to that of the network speed and rebooted Exchange.
This did not solve the problem.
Following EndureKona's post, we have hardcoded the NIC on the Exchange server to that of the network speed and rebooted Exchange.
This did not solve the problem.
If you're still having this issue, try modifying the following registry key on one of your computers:
HKLM | Software | Microsoft | Exchange | Exchange Provider | Rpc_Binding_Order
The default is: ncalrpc,ncacn_ip_tcp,ncacn
Change it so it looks like this: ncacn_ip_tcp,ncalrpc,ncacn
This will use a different protocol (TCP/IP) first and will usually speed up startup by a couple seconds and may solve this issue as well. I'm not 100% that it will specifically solve this issue, but I have had very much success with performance in multi-site domains with this tweak.
HKLM | Software | Microsoft | Exchange | Exchange Provider | Rpc_Binding_Order
The default is: ncalrpc,ncacn_ip_tcp,ncacn
Change it so it looks like this: ncacn_ip_tcp,ncalrpc,ncacn
This will use a different protocol (TCP/IP) first and will usually speed up startup by a couple seconds and may solve this issue as well. I'm not 100% that it will specifically solve this issue, but I have had very much success with performance in multi-site domains with this tweak.
ASKER
Our setup is: ncacn_ip_tcp,ncacn_spx,nca
So, TCP/IP is already our preferred protocol
So, TCP/IP is already our preferred protocol
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.