![]() |
|
Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
|||||||
| Networking with Windows Vista Networking issues and questions with Windows Vista. (microsoft.public.windows.vista.networking_sharing) |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Hi all,
I have a mapped drive on a NAS that has all my downloaded software on it. When I run one of the installers it always asks for a login. What gives? I'm already logged into the drive. Why is it asking for login again? How do I stop this annoying behaviour? Sean. |
|
|||
|
When you run the install program it is actually executing on your main
machine and not the server. Some of the support files may be written to be put in a folder adjacent to the Source file your are trying to install. This may be what's prompting the logon to your server request. Try moving the install file to a folder in the "Program Files" folder, named appropriately. Then run Install from there. -- Regards, BobF. "Sean S" wrote in message news ![]() Hi all, I have a mapped drive on a NAS that has all my downloaded software on it. When I run one of the installers it always asks for a login. What gives? I'm already logged into the drive. Why is it asking for login again? How do I stop this annoying behaviour? Sean. |
|
|||
|
"Bob F." wrote:
Some of the support files may be written to be put in a folder adjacent to the Source file your are trying to install. Even if it it trying to write to the folder it's in I have write permission to that folder and am already logged in. Why is it asking for login *again*? |
|
|||
|
Because it's the installer trying to access the folder not you Windows
Explorer. There's a big difference in how that happens. -- Regards, BobF. "Sean S" wrote in message news ![]() "Bob F." wrote: Some of the support files may be written to be put in a folder adjacent to the Source file your are trying to install. Even if it it trying to write to the folder it's in I have write permission to that folder and am already logged in. Why is it asking for login *again*? |
|
|||
|
"Sean S" wrote in message
news ![]() "Bob F." wrote: Some of the support files may be written to be put in a folder adjacent to the Source file your are trying to install. Even if it it trying to write to the folder it's in I have write permission to that folder and am already logged in. Why is it asking for login *again*? Because mapped network drives belong to the Intranet security zone rather than Local machine. Some kinds of setup are sensitive to this. Regards, --PA |