StarfishTech
asked on
Access to Network Resources in Terminal Services
We are attempting to implement a terminal server at our client site. We have installed server applications that are network based on the server. Whenever a user RDP's to the server, they can't launch any network applications. They get the following error:
Windows cannot access the specified device, path, or file. You might not have appropriate permissions to access the item.
Now this obviously seems like a permissions issue to a network folder but we have granted everyone full control of the folder. What else could be preventing the RDP users from accessing things on these mapped drives? Even if we just attempt to run a setup.exe file off the network, we get this same error. This is a 2003 server that is going to be running terminal services. The file server that drives are mapped to is an sbs 2008 box. Thank you.
Windows cannot access the specified device, path, or file. You might not have appropriate permissions to access the item.
Now this obviously seems like a permissions issue to a network folder but we have granted everyone full control of the folder. What else could be preventing the RDP users from accessing things on these mapped drives? Even if we just attempt to run a setup.exe file off the network, we get this same error. This is a 2003 server that is going to be running terminal services. The file server that drives are mapped to is an sbs 2008 box. Thank you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Although it is not intuitive, the IE Enhanced Security does effect Windows Explorer permissions. I have run into this problem before.
I agree with summerdai; this is classic IE enhanced security on Windows 2003. An administrator logged on locally would run into the same issues.
See http://support.microsoft.com/kb/303650 for more details and how to work around the issue.
See http://support.microsoft.com/kb/303650 for more details and how to work around the issue.
Were you able to resolve this issue? If not, please advise us of the status of the issue so that we can be of further assistance.