Problem saving files to network folder

[Unknown_User_916]

I discovered this program only a few days ago and I think it is great, but I have 1 problem:

When I try to save an attachment from an email in Hotmail and try to save it to My Documents I get an error (translated from Dutch):

[#]Save As[#]: Filename is not valid.

I just tried to save a Word-document as TEST.doc

Is this because My Documents are located on a network folder (\\nasserver\Jeroen)?

I can save it to an existing local drive.

[Unknown_User_916]

I just tried to install a program but it gave an error that it could not access a sub-folder of my documents (My pictures).

Is there a workaround for this?

[tzuk]

Maybe it would work if you exclude sandboxing on the My Documents folder. Trying adding

OpenFilePath=%UserProfile%
OpenFilePath=%Personal%

to Sandboxie.ini.

[Unknown_User_916]

I added both lines to the sandboxieini file, but I still can't save to My Documents from Hotmail. I can outside sandboxie
??

Also I can't access my 2 mapped network folders, except when I add them to the ini file as OpenFilePath=X:\ OpenFilePath=Y:\

[Paul_K]

OpenFilePath=%Personal% should open a path to your unsandboxed 'My Documents' folder. For example:
C:\Documents and Settings\(your logon name)\My Documents

Sandboxie gets the value for %Personal% from the Windows Registry.

In WINXP this Registry key is located at:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders

Is "Personal" listed on the right side in that Key, and what is it's value?

[Unknown_User_916]

The value is: \\nasserver\Jeroen

[Paul_K]

Disclaimer: I haven't done much with network folders, so this qualifies as a guess on my part.
I assume there's a drive letter associated with this path, in which the drive letter equates to a location on the network drive, and your nasserver folder appears to be in the root of that drive. (If the nasserver folder does not appear to be in the root of that drive, you'll have to adjust the statement, below)

So what happens if you specify something like this in the configuration file for Sandboxie (where Z: represents the network drive letter):
OpenFilePath=Z:\nasserver\Jeron\

This should open an unsandboxed path to the Jeron folder (and all sub-folders, because of the final \ character)

If that works, and you only want one sandboxed program to write directly to this unsandboxed folder, then qualify the statement by including that program's name in the statement:
OpenFilePath=firefox.exe,Z:\nasserver\Jeron\
or
OpenFilePath=Thunderbird.exe,Z:\nasserver\Jeron\

If you don't want to open an unsandboxed path to the folder, you would use the 'RecoverFolder=' statement, instead of OpenFilepath. Then, files that you save to that folder will stay in the sandox and would have to be Recovered manually, or you can configure Sandboxie to automatically ask you if you want to Recover it.

[Unknown_User_916]

@Paul: thank you for trying to help!

There is no drive letter assigned to \\naserver\Jeroen.
I do have drive letters assigned to \\nasserver\Public, which is X and \\nasserver\Qdownload which is Y.

I have a Qnap TS-101, which is a nasserver, so \\nasserver\ equals 192.168.1.100 in my home network

The folder Jeroen is in the root of the NAS.

If I assign Z to that folder (and add OpenFilePath=Z:\) I get another error if I try to save an attachment(translated):
Could not copy TEST. Task is completed
The title of the window is: Error copying file or folder.

When I try to save again it says the file already exists. When I check the file is 0 bytes. When I press t continue I get the same error again.

I even tried changing the access rights to everyone, but nothing helps

[Paul_K]

Sorry I couldn't help. I'm officially out of ideas, and out of my depth as well.

[Unknown_User_916]

No Problem, I hope Tzuk has an idea.

Thanks anyway.

[dlguild]

I have a BuffaloTech NAS, which like the Qnap, is based on Linux. I can save from Sandboxie to it with no problems. It sounds like this is really a networking issue and the Qnap settings need to be 'tweaked' a little bit.

1. Make sure the NAS folder is defined as a 'file server' (not FTP, media, etc).
2. Make sure the IP subnet mask & workgroup matches the subnet & workgroup on the computer.
3. Both the NAS & your computer must share the same initial 3 segments of the IP address (for example 192.168.0.100 & 192.168.0.55).
4. Finally, you must be able to browse from 'Network Neighborhood' directly to the folder on the NAS without having to enter a login and password. If you can not do this, then try setting the login/password to be identical on both the NAS folder & the computer (remember Linux is case sensitive, Windows is not).

Beyond the above, the only other thing that comes to mind is the possibility that it is a firewall issue. Do you have one installed? If so, remember Sandboxie is making the network call, not you, so you will have to open the firewall to allow Sandboxie to do so.

I'm not an expert at networking issues. This is just the list of things I had to do to get my NAS working with Sandboxie.

[Unknown_User_916]

How do I "Make sure the NAS folder is defined as a 'file server' (not FTP, media, etc). "
With the Qnap I added a share (Jeroen) wich contains my documents. I cannot define a type.
All shares are accessible through the home lan and through FTP (and even through telnet)

The mapped drives (X & Y) are also not accessible from sandboxie. (except when I add OpenFilePath) but then I still can't save to them. I can only see what files and folders are in it

IP of NAS = 192.168.1.100, my PC: 192.168.1.101 same workgroup
I connect wireless

I can browse the network without passwords in explorer and total commander (outside sandboxie), but not inside sandboxie.
I can access the shares directly, but not if I start with "entire network" --> Windows network --> workgroup -->
I then get the error that the workgroup is not accessible and thata I don't have enough rights followed by: the RPC-server is not available.

My firewall is Comodo.
I tried to save a download with Comodo down, but still the same error.

When I try to save a download I can navigate to My Documents perfectly and see erverything, I just can't save to it.
It just creates a 0 byte file with the same name.

[tzuk]

Is this problem closely related to the file server? In that case the file server may respond to queries/commands a little differently than Sandboxie expects, and confuse Sandboxie.

For example, a while ago someone reported installing Sandboxie into a Linux filesystem that was available in Windows through a special driver, and that too confused Sandboxie. So it's not impossible that different file systems behave differently.

JayWheel, is it possible for you to reproduce this problem by using Windows shares instead of NAS shares? This serves two purposes, one, to prove this is not related to the NAS file server, and two, to allow me to reproduce and fix it quickly.

[Unknown_User_916]

@Tzuk:

I created a windows share on another PC and mapped that to Z:\ on my laptop (with sandwboxie)
I even added OpenFilePath=Z:\

But I get the same problem: when I try to save, a zero byte file is created with the same name and I get the error.

I have a DebugView-log of the attempt to save the file.
I could send it to you if you like.

[dlguild]

What you are experiencing sounds more and more like a network configuration issue and less and less like a Sandboxie issue. Tzuk may disagree, however, and want to look at your debug log.

I can access the shares directly, but not if I start with "entire network" --> Windows network --> workgroup -->
I then get the error that the workgroup is not accessible and thata I don't have enough rights followed by: the RPC-server is not available.

Is this behavior happening outside the sandbox as well as inside the sandbox? If so, your Windows network configuration may have gotten corrupted. Check system services to make sure Remote Procedure Call (RPC) is started and set to start automatically. Also, you may want to rerun the 'Set up a home or small office network' wizard on your computer again. This sometimes resolves network connectivity issues.