Network drive...

Got a problem with Viscosity or need help? Ask here!


Posts: 1
Joined: Thu Apr 02, 2020 12:33 pm

Post by starion » Thu Apr 02, 2020 12:37 pm
Now I know this is probably not a Viscosity problem, but here it is.

When I do a reboot of my Mac, Viscosity connects without issue to my NAS drive. On said NAS drive is a shared Apple volume. EVERY time I reboot, it gives me a message that there was an error connecting to my network volume and I have to manually do a command-k to mount it, at which point it mounts with no problem.

This is clearly a timing issue.

Any way to solve?


User avatar
Posts: 2004
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Fri Apr 03, 2020 7:45 pm
Hi starion,

It's likely one of two things:

1. The drive is set to connect at login, using an address only accessible through the VPN connection, and it attempts to connect before the VPN connection is ready. Or;
2. The drive is set to connect at login, and the VPN connection is ready, but it's using the wrong IP address.

My recommendation would be to first figure out how it is set to auto-connect, and double-check it is using the correct details. It's probably a macOS Login Item, but it could also be a script or automator action set to run at login. If it is using the correct details already, my recommendation would be to remove the Login Item or script, and instead have a "Connected" script in Viscosity automatically mount the drive when the VPN connection connects: ... connected/

There is an example scripts for connecting to a file server at: ... mmon-tasks

James Bekkema
Viscosity Developer

2 posts Page 1 of 1