Terminal Server Apps: won't run

[Spirit]

Hi All,

Its been a while since I set up a TS.

I've got it working on a member server 2003 SP1 running in application mode, licenses have been activated users given Remote Desktop permissions, in ADU&C they are not DENIED Access and in dial in they have "allow".

My problem is whenever a user tries to run an application that requires access to network drives I get the following;
"Windows cannot access the specified device, path, or file. You may not have the apprpriate permissions to access the item."

It runs fine when logged into the Server directly and connected via Remote Desktop as Admin1. But I get this message if I log in directly or using RDP when using Admin2.

Admin2 is a direct copy of Admin1 created to help troubleshoot this. Application has been installed using both the change user /install and Add/Remove Programs.

I am sure I've had something similar before and its a check box somewhere......

Any help would be greatly appreciated.

Iain

 

[Spirit]

Additional:

I can open remote word & excel files but not Access and .exe files using Admin2.

The Firewall on W2k3 SP1 is disabled in the Services but is there something else somewhere blocking it?

Cheers,
Iain

 

[Spirit]

Ok so I uninstalled Windows Server 2003 Service Pack 1 and low and behold everything works perfectly......

I know that W2k3 SP1 introduces the same firewall as XP SP2 but it was disabled as far as I know and there was no GP being applied other than the default domain one.

I don't have time to figure this out at the moment so the server will have to live without SP1 until either I stumble across the solution or someone can point me in the right direction........

iain

 

[peted20]

Hi Iain,
I just spent most of the day trying to implement terminal services and fix what I think is the same problem which you were having with SP1. I'm on Win2k3 SP1, having trouble running any app (.exe) from a network share.

Turns out, for me, it was that the server sharing the executables must be added to Internet Explorer's Local Intranet or Trusted Sites zones (in the form of file://servername). I think this is probably part of the whole Internet Explorer Enhanced Security Configuration (yuck).

This post is really helped me track it down:
[URL unfurl="true"]http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.pub...[/url]

I found it interesting that I could go to a command prompt and type "cmd \\server\share\app.exe" and have the app load (as in the above post).

Since I am also running it on a terminal server, I needed to dive into the registry to add the server to my Local Intranet zone for ALL users on the terminal service machine (when doing it from the GUI, it only affects the current user).

See this link for help with that:

http://support.microsoft.com/kb/303650

I basically added a new KEY named 'servername' (with my server's name, of course) in the following location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\EscDomains

This is the text of the exported registry file to show the final registry:

----


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\EscDomains\servername]
"file"=dword:00000001

----

Just add the appropriate registry entry (or entries, if you have apps on more than one server) to your terminal server, log off connected clients, log back in, and voila! The apps should work (assuming you were having the exact problem I had)

Good Luck! Hope it works for you as well.
Pete

 

[58sniper]

You can also add them as UNC paths. The end result is the same - they appear in the trusted zones. This also fixes the prompt asking if they are sure they want to open the app (another common TS issue)

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