First of all we need to know if shortcuts are working for other users, Second you want to rule out how users are connected to exchange (local network, RPC over HTTPS or VPN) once we know that then only we can progress from there on. If the same users while using the same machines can access shortcuts on local network and shortcuts only break down when users are using RPC over HTTP that is all together a different issue because you will have to implement a reg key on the machines for which you can either run search on powerlinlek.emc.com or open a ticket with support an they can help you with that.
If shortcuts are failing for all users on the network, then open users mailbox on EX server to see if you can open shortcuts there is shortcuts cannot be opened on ex server itself then problem might be on EX server and you might want to engage support engineer to help you there.
Always remember that EX shortcut addin queries EmailXtender contact in AD to find out were to send the http request for shortcut resolution. If that url is not working shortcuts will fail.
Thanks for your response. As far as I can tell, shortcuts for all of our users on our local network seem to work. They can view the messages as well as pull back the attachments. For the users who are having a problem, they are located at a small satellite office and are connected via a point-2-point T1 line. There is no VPN connnection in this case, and their network traffic is routed through us. In addition their computers are not joined to our domain however their Outlook 2k3 clients are configured to connect to our Exchange box via IP. They have to authenticate each time they open Outlook.
I am under the assumption that the Outlook client essentially communicates only one way with Exchange. Am I wrong?
Long ago in similar situation I have tried using EmailXtender support note for RPC over HTTP(s) which happens to resolve issue for the customer. I am not sure if that is still a valid case but it's never too late to test on one machine. The reason if EX needs to query AD to get the EX server name and location of query.asp. Solution provides work around to not to query AD and use the local provided registry key. But you will have to make sure that users can resolve the query from their desktops.
Search powerlink for the support note and then follow it. If it does not work try to speak to a support engineer in your region they might be able to help.
RKatwal
2 Intern
•
600 Posts
0
May 15th, 2008 18:00
First of all we need to know if shortcuts are working for other users, Second you want to rule out how users are connected to exchange (local network, RPC over HTTPS or VPN) once we know that then only we can progress from there on. If the same users while using the same machines can access shortcuts on local network and shortcuts only break down when users are using RPC over HTTP that is all together a different issue because you will have to implement a reg key on the machines for which you can either run search on powerlinlek.emc.com or open a ticket with support an they can help you with that.
If shortcuts are failing for all users on the network, then open users mailbox on EX server to see if you can open shortcuts there is shortcuts cannot be opened on ex server itself then problem might be on EX server and you might want to engage support engineer to help you there.
Always remember that EX shortcut addin queries EmailXtender contact in AD to find out were to send the http request for shortcut resolution. If that url is not working shortcuts will fail.
Hope this helps.
Thanks,
Raj
trapspeed
15 Posts
0
May 20th, 2008 15:00
Thanks for your response. As far as I can tell, shortcuts for all of our users on our local network seem to work. They can view the messages as well as pull back the attachments. For the users who are having a problem, they are located at a small satellite office and are connected via a point-2-point T1 line. There is no VPN connnection in this case, and their network traffic is routed through us. In addition their computers are not joined to our domain however their Outlook 2k3 clients are configured to connect to our Exchange box via IP. They have to authenticate each time they open Outlook.
I am under the assumption that the Outlook client essentially communicates only one way with Exchange. Am I wrong?
RKatwal
2 Intern
•
600 Posts
0
May 20th, 2008 20:00
Long ago in similar situation I have tried using EmailXtender support note for RPC over HTTP(s) which happens to resolve issue for the customer. I am not sure if that is still a valid case but it's never too late to test on one machine. The reason if EX needs to query AD to get the EX server name and location of query.asp. Solution provides work around to not to query AD and use the local provided registry key. But you will have to make sure that users can resolve the query from their desktops.
Search powerlink for the support note and then follow it. If it does not work try to speak to a support engineer in your region they might be able to help.
Regards,
Rajan