If i have a Mapped drive or just use \\computername\C$ windows XP pro sp1 for an EXE file (maybe others) it comes up with a File Download like i would if i were to download a file from internet(except save is grayed out)

How can i get this to just run the file?



(It doesn't do this to *.wma *.zip or *.rar files with others.)

Nathan

I see the exact same thing happening on Windows Server 2003 STD from a basic load. This is the way it is setup.
I believe it to be a security issue, but have as yet to find what it is. I just started playing with Server 2003 over the weekend so I haven't had a lot of time to mess with it. Just wanted to get Exchange running

Alec, I am connecting with an account with admin rights on each box. I can log on to the box with the same accoutn and not have any issues. It bascially comes up with the same dialog box as if you were downloading the file from IE or trying to open an attachment in Outlook.
I know it's a security setting, just not sure where. It may have something to do with a local policy that got set automatically and I may need to reverse it. I'll play more this weekend

I have the same problem. I have 2 XP machines running on a network. On one of them, if I click on a shortcut to a .exe or .mdb file, it runs fine. On a new PC, clicking on a shortcut to the same files opens the "File Download" window. If I open Access and then open the .mdb file, it opens fine.

It's a security limitation on the ability to execute files within the explorer/iexplorer processes in the newer versions of Windows. The idea is to remind you that you are attempting to run an executable across a network connection, and that connection (or source) may not be trustworthy (standard response given to all attempts). I would file this as a "good idea" for the OS, although it might cause you some heartburn. This behavior will occur regardless of permissions.

marktg,

Check to see if you are running identical versions of IE, as there may have been a patch that initiated this behavior on one machine and not the other. Also, check to see if there are differences in security settings in your IE zones (not sure if this will address it, but it might be worth checking).