Problem with Client Driven Migration over VPN

[Matt_Giannetto]

We're currently having a problem with client driven migration over our VPN connection.  Any time we try to migration a PST file using the client method, the PST file will be listed with a status of "Ready to Copy".  The file will be held in that status indefinetly. 

When we use client driven migration on a LAN connection, everything works fine.

Anyone know if there are ports we need to open up on the VPN client?

-Matt

[MichelZ]

Matt

Could you check the client's logfile?

There should be errors listed why he is not able to migrate.

(CTRL+SHIFT + Click on the "Search in Vault" Button)

You may want to increase the Log level there.

Cheers

Michel

[Leo_Wan]

Which type of client you're using? HTTP (Lite) or DCOM (Full Client)? If you're using HTTP client, it will only utilize TCP 80 and 443 only. But if you're using DCOM client, it will utilize TCP 135 (RPC). Also, client will also contact Domain Controller thru 389 LDAP.

[Matt_Giannetto]

Here are the relavent log entries I found at a brief glance.  Not sure what the criteria is for the VPN connection to be considered a LAN connection.

04/08/2008 19:33:12.115[ 288]: CDesktopCommon::IsLANConnection: 0x0
04/08/2008 19:33:12.118[ 288]: Internet connection state: 1 (81)
04/08/2008 19:33:12.119[ 288]: ~CDesktopCommon::IsLANConnection: 0x0
04/08/2008 19:33:12.119[ 288]: Client does not have a LAN connection - no PST files will be migrated
04/08/2008 19:33:12.120[ 288]: ~CPSTImporter::CopyPSTsToServer: 0x0
04/08/2008 19:33:12.120[ 288]: PST Importer sleeping for 60 minutes (there is no work to do)

RPC and LDAP are both allowed through the VPN client's firewall.

Thanks!

-Matt

[Leo_Wan]

Matt,

Did your client also configured RPC-over-HTTP in their Outlook Profile? It looks like your client have switched to run on RPC-over-HTTP (on slow networks), and there is a restriction for EV Outlook plug-in while running on RPC-over-HTTP.

Try this:

Go to the EV policy that associate with the user, from the Advanced Settings, select Outlook. And there is an option "RPC over HTTP restriction" which default is "Disable Outlook Add-in". Change it to "None", sychronize the policy and try again.

Leo

[Matt_Giannetto]

The client is not set to use RPC-over-HTTP.  Despite this, I tried the setting you suggested with no luck.  Same error message:

05/08/2008 18:22:46.628[2672]: Internet connection state: 1 (81)
05/08/2008 18:22:46.628[2672]: Client does not have a LAN connection - no PST files will be migrated
05/08/2008 18:22:46.629[2672]: PST Importer sleeping for 60 minutes (there is no work to do)

-Matt

[A_Z_rcher]

dear matt

i had nearly the same problem (flag 85). I've opened a case at symantec without any luck long time ago.

The client wont work due to INTERNET_CONNECTION_LAN  not connected state.

How it determines the connection:

The client determines the connection state by a call to InternetGetConnectedState.

The only suggestion was to change the LAN/VPN bindings under

Control Panels, Network, Menu Punkt Advanced ,Advanced Settings

But I had no luck with this. Maybe you have?

open a case and escalate it!