Using Files/Programs on Network Drives - Vista F%$&in Security!

  • Thread starter Thread starter +Bob+
  • Start date Start date
B

+Bob+

How can I shut off Vista's moronic behavior of blocking 50% of what's
on my local network shares for "security" reasons.

I'm having the following problems with programs and files that work
fine from my win2K and XP clients but with Vista I have problems like
these:

- Programs I try to run from network shares often fail because they
are not allowed to read files from the same shared directory they are
running from. They fail with odd errors... I copy the folder to the
local Vista system and it runs fine.

- Programs like MS-Access post warnings/stops when I try to open
databases with warnings about the database being on an "untrusted
source" and tell me I have to make a local copy.

- Programs I start that need data files from a network share often
open but the data that should show up is not there because security
didn't allow them to read it.


None of these programs had any issues at all on XP or 2000.
 
Have a sift through tthe above link!

http://technet.microsoft.com/en-us/library/bb727037.aspx

Have a read of the above link re Vista File and Printer Sharing.
Click to expand...

Thanks Mick, lots of good info. There are things there I know I will
use if/when I share out this system.

I have fixed my immediate problem after pouring over gobs of web pages
with supposed fixes. Most of them suggest altering group policies to
allow .exe files to run locally. Unfortunately that won't work with
Vista Home versions since there's no group policy editor. It also
ignores the root problem (below).

I did find a few related posts that got me on the right track. The
basic issue is that the local network shares (UNC) are considered on
the Internet, not the Intranet by default, so they bounce a warning. I
managed to cure that by adding the local network server to the
Intranet classification. Even though MS suggests that they
automatically detect the Intranet locations there are obviously flaws
in the process as it doesn't work for many folks.

One thing that I didn't try was to fix the workgroup name and see if
it figured out (better) that a local server being accessed with a UNC
was local simply by checking the workgroup name. I have corrected the
name but I'm reluctant to back off the other settings and do the
testing now that it's all working :-)

Question for you: In the diagram of the network in that document, they
show the local router ("unidentified network") being changed to be
"private". Is that correct? The router is a typical LAN/WAN - is it
public or private (seems like both to me!).
 
Back
Top