NAS-windows 7 question

[stevech]

Windows 7 64 bit... Synology NAS. Works fine, but...
PC in workgroup mode (not domain).
When I reboot the PC, then open 'networks' using Windows Explorer (click on networks), there are red X's on the mapped drive letters that go to the NAS.
I simply click on one, and it correctly displays the files on the NAS.

Another program that runs as a windows service says 'cannot connect to network shares' (or some such). Until after I (the human) do the above one-time after booting).

It's like the service program does not or cannot authenticate with the NAD. And too, there are those red X's on the mapped drive letters one time after boot-up.

Other than this, there are no access problems but I have to do that click on mapped drives' icons in networks to get other stuff to run correctly each time I boot.

I use hibernate and don't boot very often, but it is a PITA.

Any ideas?

EDIT: I changed one of the drive letter mappings to "use other credentials" and entered the NAS user 'admin' and the admin password. Windows didn't authenticate. The admin/password I used are indeed correct.

 

[tipstir]

Your using Map drives in the Computer Explorer where as I click on Network and access my XXXNAS that way to get it shared folders. Does all your PCs on your network share the same Admin passwords an name?

On NSA 325 this is how I get around on my network on the shares and streaming. UPnP (Network Media Players) and the SMB (Windows Shares Folders)

 

[stevech]

my main desktop PC boots to my username no password; my preference since my sensitive files are in an encrypted virtual disk (SafeHouse software).

The first-time access issue is when Win 7 comes out of hibernate. The network shares always work first try by me the user, but background programs and service get an access failure on shares and/or mapped drive letters until I the user access them manually the first time. An example background program is SecondCopy (Centered Systems), runnin as an app, not a service, auto-started at boot up and not re-lanuched when Win 7 resumes from hibernation.

 

[theonlyski]

The software that you're using likely is attempting to access the drive by it's letter mapping. When it tries, Windows has a tag on it saying that it's unavailable because as far as it knows, it is unavailable (lost network connection in hibernate).

When you double-click it, Windows re-establishes the connection and the drive mapping will work again.

If you can try to get the software to access the share via the UNC instead of the share mapping, that would probably fix it.