Re: Open Remote executable?

On 24 May, 21:31, Chuck Anderson <websiteaddr...@xxxxxxxxx> wrote:
pcbutts1 [MS MVP] wrote:
It sounds like a permissions issue, I don't have that issue on mine. Check
the security of the document and settings folder see if your account has the
proper permissions.

Without really understanding what I'm doing, I've gotten this working.  
I disabled Simple File Sharing on my XP Pro PC and looked at Security
for the folder that works (C:/temp) and for the "Install Files" folder
(in Documents and Settings) - both Shared.  Seeing that C:/temp had an
entry for "Everyone" (with Read&Execute, List  Folder Contents, and Read
permission enabled), I clicked on Add in the Install Files folder (in
Documents and Settings) and added "Everyone," which appeared along with
the same permissions settings (Read&Execute, List  Folder Contents, and
Read permission).

Now I can copy and even execute the shared install files (.exe) from the
remote machine (XP Home) - even if I re-enable Simple File Sharing.

Problem solved.

.... It seems to me that when I shared the folder in Documents and
Settings, the "Everyone" entry should have been added by Simple File
Sharing, but for some reason, it was not.  At least I have it working now.

Thanks for the help .... and for hanging in there with me.


Very stupid and ignorant of you.

You should have said that when you double clicked the EXE you get some
"Access Denied" error.. and written it exactly.

What you said, was that nothing happened.


Like the idiot customer on the wordperfect tech.. Who saw a black
screen with a C, and thought that was "Nothing". Or the guy who
when he clicked Save and nothing popped up on the screen, he thought
nothing had happened. It didn't occur to him that it had saved the
entry.

Or the guy who wrote a program, ran it, and couldn't understand how
nothing had happened. Actually he hadn't printed anything on the
screen. But I wouldn't put you on his level.

Your case was more stupid. You got a fucking error message popping
up.
I'm not suggesting reading it to make sense of it, but putting it into
google would be useful. A specific error message, worded the way it
is, even if the error message is complete nonsense, it only comes up
in certain situations. And you can usually find solutions quite easily
from googling it.

I can't remember the specific errors, but it could be the "make this
folder private" box was ticked in SFS for that folder in DnS.. Or
perhaps less likely, the "Allow users to change my files" wasn't
ticked and the exe was trying to write there.

.