Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Netshare 10.1.2 Client question (corrected version...)

Created: 03 Nov 2011 • Updated: 04 Nov 2011 | 21 comments

Noob question: I read on another forum post that when you open a netshare file, it's copied (encrypted) to the local workstation and de-crypted and opened. Makes sense.

I was testing this with an MSI installer file from two Windows 7 clients (32 and 64...both using 10.2.0). In both cases, after the Windows 7 security prompt, and clicking Run, I get "The installtion package could not be opened". BUT if I manually copy the MSI file to the desktop, it remains encrypted (as expected) and will open and launch just fine. 

Exact same issue with a PDF file in a 2nd netshare on a different server.

Netshare #1 is Win2008 R2 64-bit.

Netshare #2 is Win2008 R1 32-bit.

I'm actually having similar problems with SAS files on these same two netshares, but don't have SAS installed on the clients...that's next.

I'm hoping for some clarity on the mechanics of double-clicking versus copying and opening.

Thanks for any info.

Bobby Hilliard

Atlanta, Ga.

Comments 21 CommentsJump to latest comment

Tom Mc's picture

When you access a NetShare protected file, it is transferred to your computer in an encrypted state, and automatically decrypted in the background upon arrival.  If you copy a NetShare protected file to a location outside the Netshare protected folder, it normally will retain the encryption (but this is not 100% in practice). 

Does this answer/explain the concern?

When you consider your issue resolved, please click Mark As Solution on the most helpful response.

Search the Knowledge Base &

Tom Mc's picture

To be more comprehensive, I probably should add that if you access a NetShare protected file by it associated application, and then save it from the application to a folder that does not have NetShare protection, the newly saved copy of the file will not be encrypted.

When you consider your issue resolved, please click Mark As Solution on the most helpful response.

Search the Knowledge Base &

rehilliard's picture

The problem I'm having is that some, but not all, file-types on a 2008 R1 and R2 netshare post errors when double-clicked to open from Windows 7 client machines (using  PGP 10.2.0). 32 and 64-bit clients.

BUT...when I copy the file to the local machine, it appears to preserve the encryption (icon shows lock and restarting PGP causes passphrase prompt), the files open okay.

I have a group of users who's data files were moved to a 2008 R1 32-bit netshare at some time in the past. They all are now on Windows 7 64-bit clients (10.2.0 PGP client), and are having a devil of a time being able to access certain file-types. 

I just built a new 2008 R2 64-bit server and created a test netshare. Some file-types open okay from Win7-64, some won't. BUT copying those that dont to the local workstation and the open fine. I can't get anything useful to be logged.

Symantec tells me to wait on the next version. 

I'm just looking for clues as to who is having the issue:

- PGP 64-bit client?

- PGP and 2008? 

- Win7-64 and PGP?

- Win7-64, PGP, and 2008?

I'm off to run thru tests using XP client to see what shakes out.

I'll post any results. 

Thanks.

Julian_M's picture

I´m almost sure that MSI installers need specials permissons/policy to be installed from a shared folder location. (encrypted or not)

You should google and find the solution.

As for PDF files, what is the error message? Inmediately after receiving message , open PGP Desktop , Tools menu, View log files.

Tell us if you find anything meaningful.

When you consider the issue resolved, please click Mark As Solution on the post that best provided the solution.
 

rehilliard's picture

Well, for reasons known only to the gods, I can't get to the Symantec support site to help me "remember" how to setup debug logging. I get the "unavailable due to system maintenance" error. (reminds me of my enterprise vault days!)

If I de-crypt the MSI, I can launch it with no problems from the file-share.

PDF error: adobe reader could not open <filename> because it is either not a supported file type or because the file has been damaged...".

- if I copy to desktop, I can open (appears to remain encrypted)

- if I create a new netshare on desktop and copy to it, I can open

- if i un-encrypt the PDF I can double-click and open from the file-share.

This particular test was on Win7 32 with PGP 10.2.0.

The MSI netshare is on 2008 R2 64-bit. It was created via PGP 10.2.0 on Win7 64-bit.

The PDF netshare is on 2008 R1 32-bit. It was created via PGP 10.2.0 on Win7 32-bit.

I'm building a WinXP box and will try 10.2.0 on it for both netshares. 

Thanks for the reply.

rehilliard's picture

Using the previously posted netshares and files...I have no problems opening from an XP SP3 32-bit with PGP 10.1.2 client.

On the Windows 7 clients, firewall and UAC are both off.

So, my original question remains: why does it fail when double-clicking in netshare but work when copying to (a) desktop or (b) netshare on desktop? Wouldn't that be some sort of clue? 

Thanks for any info.

Julian_M's picture

I´m almost sure that MSI installers need specials permissons/policy to be installed from a shared folder location. (encrypted or not)

When you consider the issue resolved, please click Mark As Solution on the post that best provided the solution.
 

rehilliard's picture

The MSI launches and installs fine from the share if unencrypted. Only has problem if it is encrypted and client is Win7 (32 or 64) with PGP 10.1.2. XP client DOES NOT have the problem with PGP 10.1.2.

This is also true for the PDF file.

I'm hoping this is a clue to the issues that we're seeing.

rehilliard's picture

The account being used is a domain account and is in the local admin group on all clients. Netshare servers are also domain members.

Thanks.

Julian_M's picture

"Only has problem if it is encrypted and client is Win7 (32 or 64) with PGP 10.1.2. XP client DOES NOT have the problem with PGP 10.1.2."

 

 

Please clarify which version has the problem

I have heard of this issues happening in 10.1.2 but being fixed on 10.2

When you consider the issue resolved, please click Mark As Solution on the post that best provided the solution.
 

rehilliard's picture

I am having the problem with PGP Desktop 10.1.2. build 9 (i originally had the wrong version in the posting title).

1. on Windows 7 32-bit: yes

2. on Windows 7 64-bit: yes

3. on Windows XP SP3 32-bit: not a problem

On the Windows 7 machines:

- double-clicking the file in the netshare window fails.

- copying the file from the netshare to desktop opens without a problem

This happens to multiple file-types...but not all.

There is obviously something "new" happening during the movement of the encrypted file from the netshare to the local machine resources when it's double-clicked that was not an issue in XP.

That's all I got so far...

Julian_M's picture

I have heard of this problem for PDF, actually was a bug for 10.1.2

Please upgrade to 10.2 MP1 since it does not seems to have issues.

When you consider the issue resolved, please click Mark As Solution on the post that best provided the solution.
 

rehilliard's picture

upgraded to 10.2.mp1 on 64-bit Win7 client. Same results. Tested with a PDF file and a SAS file. 

rehilliard's picture

 

\\rsrw01\pgptest is the name of the netshare. this was from win7 64-bit 10.2.0 client.
 
10:09:34 Email Debug >> PGPocWaitForAllThreadsToTerminate
10:09:36 Email Debug << PGPocWaitForAllThreadsToTerminate
10:09:36 Email Debug >> PGPocTrayPurgePassphraseCache
10:09:36 Email Debug << PGPocTrayPurgePassphraseCache
10:09:36     ----- PGP Desktop stopped -----
10:09:42     ----- PGP Desktop started -----
10:09:42     PGP Desktop 10.2.0 (Build 1950) (1950)
10:09:42     Today's date is Monday, November 07, 2011
10:09:43 PGP Info Setting logging level to: 0xF3F
10:09:43 Email Debug >> PGPocTrayLoadAccountData
10:09:43 Email Debug << PGPocTrayLoadAccountData
10:09:43 Email Debug << PGPocTrayLoadPrefsData
10:09:43 Email Debug << PGPocInitApplication
10:09:43 Email Warning Your current PGP Desktop license does not support proxying
10:09:43 Email Warning Outgoing email messages will not be secured by PGP
10:09:43 Email Debug >> PGPocInitThreads
10:09:43 Email Verbose Listening on port 33333
10:09:43 Email Debug >> PGPocInitializeWorkerThreads
10:09:43 Email Debug << PGPocInitializeWorkerThreads
10:09:43 PGP Verbose Worker threads started
10:09:43 Email Verbose Connection accepted
10:09:43 Email Debug Queueing socket 0x57C for worker
10:09:43 Email Debug Socket 0x57C dequeued by worker
10:09:43 Email Debug Received OIPCINIT
10:09:43 Email Debug >> PGPocInitIndirectSession
10:09:43 Email Debug Session-type: LSP
10:09:43 Email Debug Not redirecting LSP session
10:09:43 Email Debug << PGPocInitIndirectSession
10:09:43 Email Debug PGPocInitIndirectSession succeeded
10:09:43 Email Debug Sending OIPCINITRESP
10:09:43 Email Debug Closed client socket: 0x57C
10:09:44 Email Debug << PGPocInitThreads
10:09:44 Email Debug Token thread successfully loaded PKCS11 driver ''
10:09:44 Email Debug Starting initialization procedure
10:09:46 Email Debug >> PGPocTrayLoadPrefsData
10:09:46 Email Debug << PGPocTrayLoadPrefsData
10:09:46 Email Verbose Looking for account data for mail server pgprw01.msm.edu; PGP server pgprw01.msm.edu; user (null); and address (null)
10:09:47 Email Debug >> PGPocTrayLoadPrefsData
10:09:47 Email Verbose Found existing service for messaging server pgprw01.msm.edu
10:09:47 Email Verbose Existing entry is (untitled)
10:09:47 Email Debug << PGPocTrayLoadPrefsData
10:09:47 Email Debug >> PGPocTrayCacheAccountPassphrases
10:09:47 Email Debug << PGPocTrayCacheAccountPassphrases
10:09:47 PGP Info Initiating daily maintenance procedures
10:09:48 Email Debug >> PGPocTrayLoadPrefsData
10:09:48 Email Debug << PGPocTrayLoadPrefsData
10:09:48 Email Debug >> PGPocAccountMaintenance1
10:09:48 Email Debug << PGPocAccountMaintenance1
10:09:48 Email Debug >> PGPocTrayKeyringMaintenance
10:09:48 Email Debug >> PGPocTrayLoadPrefsData
10:09:49 Email Debug << PGPocTrayLoadPrefsData
10:09:51 Email Debug << PGPocTrayKeyringMaintenance
10:09:51 Email Debug >> PGPocAccountMaintenance2
10:09:51 Email Debug << PGPocAccountMaintenance2
10:09:52 Email Debug >> PGPocTrayLoadPrefsData
10:09:52 Email Debug << PGPocTrayLoadPrefsData
10:09:53 NetShare Verbose Policy update initiated
10:09:53 NetShare Verbose Custom location-based Blacklist: no items
10:09:53 NetShare Verbose Location-based Whitelist: no items
10:09:53 NetShare Verbose Custom app-based Blacklist: no items
10:09:53 NetShare Verbose App-based Whitelist: no items
10:09:59 Email Debug >> PGPocTrayLoadPrefsData
10:09:59 Email Debug << PGPocTrayLoadPrefsData
10:10:16 NetShare Info PGP NetShare unlocked [\\rsrw01\PGPTest]
10:10:20 Email Debug >> PGPocTrayLoadPrefsData
10:10:22 Email Debug << PGPocTrayLoadPrefsData
10:10:23 Email Debug >> PGPocTrayLoadPrefsData
10:10:23 Email Debug << PGPocTrayLoadPrefsData
10:10:24 Email Debug >> PGPocTrayLoadPrefsData
10:10:24 Email Debug << PGPocTrayLoadPrefsData
10:10:25 Email Debug >> PGPocTrayLoadPrefsData
10:10:25 Email Debug << PGPocTrayLoadPrefsData
10:10:25 Email Debug >> PGPocTrayLoadPrefsData
10:10:26 Email Debug << PGPocTrayLoadPrefsData
10:10:26 Email Debug >> PGPocTrayLoadPrefsData
10:10:26 Email Debug << PGPocTrayLoadPrefsData
10:10:29 Email Debug >> PGPocTrayLoadPrefsData
10:10:29 Email Debug << PGPocTrayLoadPrefsData
rehilliard's picture

Can you tell me what this means? It's been in release notes going back a few versions.

 

Mapped local drives. Do not map a local drive on Microsoft Windows Vista, Windows 7, or Windows Server

 

2008 and then encrypt the contents of a folder on the mapped drive. Doing so could cause your data to become
corrupted. [27680]
 
 
Does this mean use UNC paths instead of literal mapped-drives on the client doing the encryption? 
Thanks.
Tom Mc's picture

Here's an example.

When you consider your issue resolved, please click Mark As Solution on the most helpful response.

Search the Knowledge Base &

rehilliard's picture

I would've expected to see "SUBST" in the statement instead of mapping local drive. Thanks Tom.

rehilliard's picture

Can you confirm that this combination is prone to problems at this time?

Why do I say this?

I created a test netshare on Win2003 R2, and put the test files there and can open them just fine from both 32 and 64 bit Win7 clients. (using both PGP 10.2.0 and 10.1.2). Fails if netshare is on 2008 (R1 or R2). 

I'm just looking for verification so I can determine how to proceed to help the affected users.

Thanks.

abechter's picture

Anything new on this problem?

I can confirm pgp encrypted TIF file residing on 2008 r2 server SP1 cannot be opened(using windows photo viewer or 3-rd party irfanview) by win7 client running pgp desktop 10.2.

XP clients can open the same files ok from the server.

For win7 client, encrypted file opens ok if copied to local machine.  

If the same encrypted file is copied to win server 2003 SP2, both XP and win7 clients can open the file.

Andreas Zengel's picture

We have seen similar issues before. Can you please try with the latest PGP Desktop Maintenance Pack (version 10.2.0 2081 or higher)?

Maintenance Packs are available through http://fileconnect.symantec.com by providing the serial number on your purchase order