Windows 2003 Terminal Server execute on external fileserver 1

[bctechnzl]

Having mostly installed a Windows Server 2003 Terminal Service server for remote access to the company system, I find executable programs stored on the already existing file server or any other share will not run. Everything installed on the Terminal Server is fine.
This can be demonstrated with winmine.exe or mshearts.exe Program will run happily when logged in as administrator, but not as a user with administrator privileges.

When test running as a user I get:
Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.

User permissions on the file server are not the problem, one of the shares is simply on a pc, same problem.

I've looked and googled and searched but can't find a reference to this and it must be reasonably obvious somwhere.

 

[58sniper]

Go into the INTRANET zone in IE on the TS box, and add the name of the file server in the \\servername format.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt

 

[bctechnzl]

Fantastic, that worked. I'm speechless as to why that setting affects file servers but I'm grateful for the pointer.
Is there a way to do this with system policies, or system wide rather than on a per user basis?

 

[monsterjta]

Yes, you can deploy this with a policy. Under the user configuration, internet explorer maintenance, security zones, trusted sites. Add the file server as a trusted site.

Hope This Helps,

Good Luck!

(Enamoration by Automation)