PulseLearning
asked on
Outlook 2003 Client Stops Responding with RPC over Https
Hello,
I have setup a single server instance Exchange 2003 with RPC over Https. All is working fine with this setup but i have had intermittent problems with some clients continually having ro restart their Outlook 2003 client because it hangs during a send recieve.
These same clients when in the home office work just fine, what is also more puzzling is these same clients work fine in other locations outside of the office.
I have checked and rechecked the Server side of things and all is great. This problem is very intermittent but extremely anoying when present as the person has to restart Outlook many many times when this problem shows its ugly head.
i would appreciate any help you can offer, thanks.
I have setup a single server instance Exchange 2003 with RPC over Https. All is working fine with this setup but i have had intermittent problems with some clients continually having ro restart their Outlook 2003 client because it hangs during a send recieve.
These same clients when in the home office work just fine, what is also more puzzling is these same clients work fine in other locations outside of the office.
I have checked and rechecked the Server side of things and all is great. This problem is very intermittent but extremely anoying when present as the person has to restart Outlook many many times when this problem shows its ugly head.
i would appreciate any help you can offer, thanks.
One thing you could check is the firewall / router configuration. Since RPC over HTTPS uses some non-standard connection methods, it could be that the firewall is interfering or simply not compatible with these kind of connections.
ASKER
Thanks Villo,
But I have double checked and the required ports are open to allow the connections, if they were not open no person would ba able to make a connection. It is difficult to understand because sometimes it works find and other times it just locks up.
What is even more wierd is that i can have multiple people in the same location all trying to connect via RPC over Https and some will work and others will not.
I am beginning to think it is related to bandwidth, but from my understanding RPC is supposed to minimize bandwidth usage.
But I have double checked and the required ports are open to allow the connections, if they were not open no person would ba able to make a connection. It is difficult to understand because sometimes it works find and other times it just locks up.
What is even more wierd is that i can have multiple people in the same location all trying to connect via RPC over Https and some will work and others will not.
I am beginning to think it is related to bandwidth, but from my understanding RPC is supposed to minimize bandwidth usage.
I didn't mean the port forwarding configuration, but any "fragmented packet" or "Spam" filter you may have.
You can also start outlook using the switch "/rpcdiag", maybe something comes up. I have used RPC over HTTPS with slow modem connections and it is reliable (slow but it doesn't normally hang).
You can also start outlook using the switch "/rpcdiag", maybe something comes up. I have used RPC over HTTPS with slow modem connections and it is reliable (slow but it doesn't normally hang).
ASKER
We outsource our SPAM filtering so that would have no effect, besides if it were something like that it would affect everyone all the time and it doesnt. If fact the same person is not effected all the time and it is not isolated to any one person or location.
Do you have sufficient Exchange licenses on your server? It shouldn't hang outlook which should wait for a license to be come available - but might exhibit symptoms like hanging.
ASKER
Thanks for that dave, I think we have enough licenses but I will invistagate and find out. Do you know if there is an easy way to check the number of licenses installed and how many are free?
ASKER
I have completed a check of the installed licenses and we have more than enough so this would not prevent users from accessing.
I am really struggling with this problem since i have posted this question 2 more users have seen the problem and it has disappeared. This is really stange as it comes and goes and doesnt always effect the same person.
I am really struggling with this problem since i have posted this question 2 more users have seen the problem and it has disappeared. This is really stange as it comes and goes and doesnt always effect the same person.
I am also experiencing the same exact problem - any update on resolution?
ASKER
Hello,
I have found the source of this problem, it was the binding order of the network interface adapters. This was causing the RPC to timeout and hang. I reordered the bindings of the network adapters and put the most used network adapter at the top of the binding order and volia it solved my problem.
This question can be closed, as I solved this awarding points to anyone would not be fair, thanks for all those that did reply.
I have found the source of this problem, it was the binding order of the network interface adapters. This was causing the RPC to timeout and hang. I reordered the bindings of the network adapters and put the most used network adapter at the top of the binding order and volia it solved my problem.
This question can be closed, as I solved this awarding points to anyone would not be fair, thanks for all those that did reply.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.