s this simply not possible over a Windows XP LAN?

I have a wireless network in my home with one remote computer. I have
shared a folder containing installation files. Some are zip files,
others are executables. I want to install software on the remote
machine by opening shared .exe installation files, but when I try to
Open them, nothing happens. I can see why this might be considered a
security risk, but is there a way to tell Windows XP to open them
anyway? (I have already disabled the firewall.)

TIA,
Chuck

Chuck Anderson wrote:
> s this simply not possible over a Windows XP LAN?
>
> I have a wireless network in my home with one remote computer. I
> have shared a folder containing installation files. Some are zip
> files, others are executables. I want to install software on the
> remote machine by opening shared .exe installation files, but when
> I try to Open them, nothing happens. I can see why this might be
> considered a security risk, but is there a way to tell Windows XP
> to open them anyway? (I have already disabled the firewall.)

PSEXEC?

Not sure exactly what it is you are trying to do/your setup.

Are you saying you are sitting on the OTHER machine (not the one with the
SHARED folder - but the one ACCESSING the shared folder) and when you
double-click on the installer - nothing happens?

Can you copy the executable to the local desktop or something and run it?

Get any specific error messages?

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

To run install files or zip, there is not difference with wired or wireless
networks.

You need to have all PCs:

1) on the same IP network (ex 192.168.1.xxx)
2) be part of the same workgroup / domain
3) Share the folder
4) Set up File / Printer sharing access thru the software filewalls
5) Check and configure anti-virus Internet worm modules to let NetBIOS name
resolution for your network (LAN.)



On 22/05/2008 Chuck Anderson <websiteaddress@seemy.sig> wrote:
>s this simply not possible over a Windows XP LAN?
>
>I have a wireless network in my home with one remote computer. I have
>shared a folder containing installation files. Some are zip files,
>others are executables. I want to install software on the remote
>machine by opening shared .exe installation files, but when I try to
>Open them, nothing happens. I can see why this might be considered a
>security risk, but is there a way to tell Windows XP to open them
>anyway? (I have already disabled the firewall.)
>
>TIA,
> Chuck

Shenan Stanley wrote:
> Chuck Anderson wrote:
>
>> s this simply not possible over a Windows XP LAN?
>>
>> I have a wireless network in my home with one remote computer. I
>> have shared a folder containing installation files. Some are zip
>> files, others are executables. I want to install software on the
>> remote machine by opening shared .exe installation files, but when
>> I try to Open them, nothing happens. I can see why this might be
>> considered a security risk, but is there a way to tell Windows XP
>> to open them anyway? (I have already disabled the firewall.)
>>
>
> PSEXEC?
>
> Not sure exactly what it is you are trying to do/your setup.
>

I'm not sure what to call the two machines (or if it matters).

Computer A: I have installed a wireless router on my "main" PC - wired
to an ethernet port.

Computer B: I have another (new/used) Windows XP computer with a
wireless card that is connected to the wireless network.

I am trying to install an application on B by going to a shared folder
on A and opening an executable installation file
(TweakUiPowertoySetup-new.exe). I have files and printers shared and
can even open zip files on A (from B), but when I double-click, or
right-click-Open the shared file, nothing happens ... no error, no
popup, nothing happens. If I double click on a zip file, I get a
warning about "potential security risk" but then I can open it.

> Are you saying you are sitting on the OTHER machine (not the one with the
> SHARED folder - but the one ACCESSING the shared folder) and when you
> double-click on the installer - nothing happens?
>

Correct.

> Can you copy the executable to the local desktop or something and run it?
>

I can, ... but it seems like it would be more efficient to keep one copy
on A and install it on B over the network.

> Get any specific error messages?
>

No message at all.

smlunatick wrote:
> To run install files or zip, there is not difference with wired or wireless
> networks.
>
> You need to have all PCs:
>
> 1) on the same IP network (ex 192.168.1.xxx)
>

Yep.

> 2) be part of the same workgroup / domain
>

Same workgroup.

> 3) Share the folder
>

Yep. I can access the folder on the "remote" machine and open zip files.

> 4) Set up File / Printer sharing access thru the software filewalls
>

Firewall is off on remote machine. Using Zone Alarm on the "main -
server?" but have put the remote machines IP address in the trusted zone

> 5) Check and configure anti-virus Internet worm modules to let NetBIOS name
> resolution for your network (LAN.)
>

No anti-virus running.

> On 22/05/2008 Chuck Anderson <websiteaddress@seemy.sig> wrote:
>
>> s this simply not possible over a Windows XP LAN?
>>
>> I have a wireless network in my home with one remote computer. I have
>> shared a folder containing installation files. Some are zip files,
>> others are executables. I want to install software on the remote
>> machine by opening shared .exe installation files, but when I try to
>> Open them, nothing happens. I can see why this might be considered a
>> security risk, but is there a way to tell Windows XP to open them
>> anyway? (I have already disabled the firewall.)
>>
>> TIA,
>> Chuck
>>


--
*****************************
Chuck Anderson • Boulder, CO
http://www.CycleTourist.com
Nothing he's got he really needs
Twenty first century schizoid man.
***********************************

No antivirus at all or you just disabled it for the install?


--
Ignore posts made by the person called Leythos, he is a stalker who's been
obsessed with me for years ever since I spurned his advances towards me.




"Chuck Anderson" <websiteaddress@seemy.sig> wrote in message
news:DuadnZcCRI2tRqjVnZ2dnUVZ_uCdnZ2d@comcast.com. ..
> smlunatick wrote:
>> To run install files or zip, there is not difference with wired or
>> wireless networks.
>>
>> You need to have all PCs:
>>
>> 1) on the same IP network (ex 192.168.1.xxx)
>>
>
> Yep.
>
>> 2) be part of the same workgroup / domain
>>
>
> Same workgroup.
>
>> 3) Share the folder
>>
>
> Yep. I can access the folder on the "remote" machine and open zip files.
>
>> 4) Set up File / Printer sharing access thru the software filewalls
>>
>
> Firewall is off on remote machine. Using Zone Alarm on the "main -
> server?" but have put the remote machines IP address in the trusted zone
>
>> 5) Check and configure anti-virus Internet worm modules to let NetBIOS
>> name resolution for your network (LAN.)
>>
>
> No anti-virus running.
>
>> On 22/05/2008 Chuck Anderson <websiteaddress@seemy.sig> wrote:
>>
>>> s this simply not possible over a Windows XP LAN?
>>>
>>> I have a wireless network in my home with one remote computer. I have
>>> shared a folder containing installation files. Some are zip files,
>>> others are executables. I want to install software on the remote
>>> machine by opening shared .exe installation files, but when I try to
>>> Open them, nothing happens. I can see why this might be considered a
>>> security risk, but is there a way to tell Windows XP to open them
>>> anyway? (I have already disabled the firewall.)
>>>
>>> TIA,
>>> Chuck
>>>
>
>
> --
> *****************************
> Chuck Anderson • Boulder, CO
> http://www.CycleTourist.com
> Nothing he's got he really needs
> Twenty first century schizoid man.
> ***********************************
>

On 22 May, 20:17, Chuck Anderson <websiteaddr...@seemy.sig> wrote:
> s this simply not possible over a Windows XP LAN?
>
> I have a wireless network in my home with one remote computer. *I have
> shared a folder containing installation files. *Some are zip files,
> others are executables. *I want to install software on the remote
> machine by opening shared .exe installation files, but when I try to
> Open them, nothing happens. *I can see why this might be considered a
> security risk, but is there a way to tell Windows XP to open them
> anyway? *(I have already disabled the firewall.)
>
> TIA,
> * Chuck


If using File And Printer Sharing, you go to a shared folder on a
remote computer, and run an EXE then it runs on your local machine,
not the remote one.

I don't know why nothing happens when you double click one, but
clearly it is not what you want anyway.

One way to run it is to access the screen of the remote machine, and
execute the file. Windows remote desktop(it is built into windows
xp). or VNC.
Another way is a command line program by "sysinternals" calls psexec.

And maybe telnet might do it too.. windows xp (NT?) has a built in
telnet server you can start.

For remote desktop.. To start the server, (server is for the remote
machine, you do some checkbox within ctrl panel..system..). To start
the client(do this on the local machine), you do
start...run..mstsc<ENTER> to run mstsc.exe

Whatever servers you are running.. I suggest you have the windows
firewall On. And allowing them through. BUT LIMIT (what windows
firewall calls) "THE SCOPE" to your own network. So that other
computers cannot connect.. The NAT Router you probably use should stop
them anyway. But it isn't really designed with that purpose.. The
Firewall should be set to stop them.
You may want to go to a port scanning website like Shields Up on
grc.com, and try that

note: Steve Gibson who runs GRC and made Shields Up, is a very bad
character.. Don't take him seriously.. His website information is
propaganda to obfuscate things in order to make -real- technical
information more obscure, and confusing, so as to hide knowledge from
potential hackers learning from his website. He admitted himself that
he "set up a deliberate disinformation campaign". He is on tape saying
that, audio online somewhere. There used to be a website called
grcsucks that exposed him.. A few of its files are still around.
Very evil dangerous man.. But I have found his Shields Up thing
useful.

On May 23, 6:44*am, Chuck Anderson <websiteaddr...@seemy.sig> wrote:
> > 1) *on the same IP network (ex 192.168.1.xxx)
>
> Yep.
>
> > 2) be part of the same workgroup / domain
>
> Same workgroup.
>
> > 3) Share the folder
>
> Yep. I can access the folder on the "remote" machine and open zip files.
>
> > 4) Set up File / Printer sharing access thru the software filewalls
>
> Firewall is off on remote machine. Using Zone Alarm on the "main -
> server?" but have put the remote machines IP address in the trusted zone
>
> > 5) Check and configure anti-virus Internet worm modules to let NetBIOS name
> > resolution for your network (LAN.)
>
> No anti-virus running.
>
Chuck,

You'll need to "Remote Desktop" into the machine with the .exe on it.
That will allow you to run the executable on the remote machine.

If on the other hand you want to run the executable that is located on
the remote machine on you local machine (the one you are now sitting
at) then will have to copy the exe from the remote to the local, and
then run it.

Good luck.

pcbutts1 [MS MVP] wrote:
> No antivirus at all or you just disabled it for the install?

No anti-virus at all. I only run the antivirus program (AVG) on-demand.

It would seem from a couple other posts I've gotten here now, that you
cannot "simply" run an executable from a shared folder. That's okay by
me. I just thought it would be more efficient to not have to copy it first.

--
*****************************
Chuck Anderson • Boulder, CO
http://www.CycleTourist.com
Nothing he's got he really needs
Twenty first century schizoid man.
***********************************

cornedbeef007-groups******.com.au wrote:
> On May 23, 6:44 am, Chuck Anderson <websiteaddr...@seemy.sig> wrote:
>
>>> 1) on the same IP network (ex 192.168.1.xxx)
>>>
>> Yep.
>>
>>
>>> 2) be part of the same workgroup / domain
>>>
>> Same workgroup.
>>
>>
>>> 3) Share the folder
>>>
>> Yep. I can access the folder on the "remote" machine and open zip files.
>>
>>
>>> 4) Set up File / Printer sharing access thru the software filewalls
>>>
>> Firewall is off on remote machine. Using Zone Alarm on the "main -
>> server?" but have put the remote machines IP address in the trusted zone
>>
>>
>>> 5) Check and configure anti-virus Internet worm modules to let NetBIOS name
>>> resolution for your network (LAN.)
>>>
>> No anti-virus running.
>>
>>
> Chuck,
>
> You'll need to "Remote Desktop" into the machine with the .exe on it.
> That will allow you to run the executable on the remote machine.
>

I wanted to give Remote Desktop a try someday anyway.

> If on the other hand you want to run the executable that is located on
> the remote machine on you local machine (the one you are now sitting
> at) then will have to copy the exe from the remote to the local, and
> then run it.
>

Works for me.

Thanks.

--
*****************************
Chuck Anderson • Boulder, CO
http://www.CycleTourist.com
Nothing he's got he really needs
Twenty first century schizoid man.
***********************************

jameshanley39******.co.uk wrote:
> On 22 May, 20:17, Chuck Anderson <websiteaddr...@seemy.sig> wrote:
>
>> s this simply not possible over a Windows XP LAN?
>>
>> I have a wireless network in my home with one remote computer. I have
>> shared a folder containing installation files. Some are zip files,
>> others are executables. I want to install software on the remote
>> machine by opening shared .exe installation files, but when I try to
>> Open them, nothing happens. I can see why this might be considered a
>> security risk, but is there a way to tell Windows XP to open them
>> anyway? (I have already disabled the firewall.)
>>
>> TIA,
>> Chuck
>>
>
>
> If using File And Printer Sharing, you go to a shared folder on a
> remote computer, and run an EXE then it runs on your local machine,
> not the remote one.
>

Makes sense. I can simply copy it from the shared folder (and then
delete it it I really feel the need).

> I don't know why nothing happens when you double click one, but
> clearly it is not what you want anyway.
>
> One way to run it is to access the screen of the remote machine, and
> execute the file. Windows remote desktop(it is built into windows
> xp). or VNC.
> Another way is a command line program by "sysinternals" calls psexec.
>
> And maybe telnet might do it too.. windows xp (NT?) has a built in
> telnet server you can start.
>
> For remote desktop.. To start the server, (server is for the remote
> machine, you do some checkbox within ctrl panel..system..). To start
> the client(do this on the local machine), you do
> start...run..mstsc<ENTER> to run mstsc.exe
>
> Whatever servers you are running.. I suggest you have the windows
> firewall On. And allowing them through. BUT LIMIT (what windows
> firewall calls) "THE SCOPE" to your own network. So that other
> computers cannot connect.. The NAT Router you probably use should stop
> them anyway. But it isn't really designed with that purpose.. The
> Firewall should be set to stop them.
> You may want to go to a port scanning website like Shields Up on
> grc.com, and try that
>
> note: Steve Gibson who runs GRC and made Shields Up, is a very bad
> character.. Don't take him seriously.. His website information is
> propaganda to obfuscate things in order to make -real- technical
> information more obscure, and confusing, so as to hide knowledge from
> potential hackers learning from his website. He admitted himself that
> he "set up a deliberate disinformation campaign". He is on tape saying
> that, audio online somewhere. There used to be a website called
> grcsucks that exposed him.. A few of its files are still around.
> Very evil dangerous man.. But I have found his Shields Up thing
> useful.
>

Thanks for all the advice. I checked my system with Shields up with my
previous 4 port router. I think I'll give it a shot with this new
wireless one now, too.


--
*****************************
Chuck Anderson • Boulder, CO
http://www.CycleTourist.com
Nothing he's got he really needs
Twenty first century schizoid man.
***********************************

You "can" run an executable from a shared folder but that depends on the
executable. If it is a setup file it should work however there are viruses
and spyware that will prevent that if you are infected. I'm talking about
installing software on the computer you are in front of when the setup file
is on the remote computer. If you are trying to install that software onto
the remote computer then you have to use the "AT" command which you can run
from your computer. More info on the "AT" command can be found here
http://support.microsoft.com/kb/313565


--
Ignore posts made by the person called Leythos, he is a stalker who's been
obsessed with me for years ever since I spurned his advances towards me.




"Chuck Anderson" <websiteaddress@seemy.sig> wrote in message
news:GuKdnVmby5rUjKvVnZ2dnUVZ_uGdnZ2d@comcast.com. ..
> pcbutts1 [MS MVP] wrote:
>> No antivirus at all or you just disabled it for the install?
>
> No anti-virus at all. I only run the antivirus program (AVG) on-demand.
>
> It would seem from a couple other posts I've gotten here now, that you
> cannot "simply" run an executable from a shared folder. That's okay by
> me. I just thought it would be more efficient to not have to copy it
> first.
>
> --
> *****************************
> Chuck Anderson • Boulder, CO
> http://www.CycleTourist.com
> Nothing he's got he really needs
> Twenty first century schizoid man.
> ***********************************
>

In article <4qmZj.1357$N87.634@nlpi068.nbdc.sbc.com>, pcbutts1
@leythosthestalker.com says...
> Ignore posts made by the person called Leythos, he is a stalker who's been
> obsessed with me for years ever since I spurned his advances towards me.
>
Advanced towards you? HA HA HA - you create and post links about me and
others, filthy pornographic links, on YOUR WEBSITE, you even stalk me by
creating a domain name about me, and you claim I'm stalking your sorry
little person?

The fact is that your a sad little man, one that strongly appears to
pirate code from other people/vendors and then edit it to show your name
and then you take credit for the works and never give the real authors
credit for it.

The fact is that you are completely shunned by the anti-malware
community, you are looked on as a thief and pirate by all reputable
people in the community, you have posted links to your website that
contain filthy pornographic materials that you have proudly claimed you
created (which appear to also have been stolen from sites).....

Not one reputable person will come to vouch for you, and you want to
claim I made "advanced" towards you.... More of your delusional crap
Chris.

The link to the site that shows the links you've posted to Usenet are in
my Sig for all to see, links that YOU POSTED taking claim for the
content that is very nasty.

--
Leythos - spam999free@rrohio.com (remove 999 to email me)
Fight exposing kids to porn, complain about sites like PCBUTTS 1.COM
that create filth and put it on the web for any kid to see: Just take a
look at some of the FILTH he's created and put on his website:
http://forums.speedguide.net/archive.../t-223485.html all exposed
to children (the link I've include does not directly display his filth).
You can find the same information by googling for 'PCBUTTS1' and
'exposed to kids'.

In article <8WpZj.1723$mh5.928@nlpi067.nbdc.sbc.com>, pcbutts1
@leythosthestalker.com says...
> Ignore posts made by the person called Leythos, he is a stalker who's been
> obsessed with me for years ever since I spurned his advances towards me.
>
Chris, you've been posting my name in EVERY ONE OF YOUR POSTS ALL OVER
USENET, if you don't want to see me reply then stop posting my name in
your posts - it's that simple. Take my name out of your posts and I'll
stop replying to them. It's your choice, keep harassing me in every post
and I'll keep replying to defend my name.

--
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
spam999free@rrohio.com (remove 999 for proper email address)

On 23 May, 01:35, Chuck Anderson <websiteaddr...@seemy.sig> wrote:
> pcbutts1 [MS MVP] wrote:
> > No antivirus at all or you just disabled it for the install?
>
> No anti-virus at all. *I only run the antivirus program (AVG) on-demand.
>
> It would seem from a couple other posts I've gotten here now, that you
> cannot "simply" run an executable from a shared folder. *That's okay by
> me. *I just thought it would be more efficient to not have to copy it first.
>

some terminology.

Computer A accesses Computer B
So computerA is LOCAL.
computerB is REMOTE.



You can run an executable -from- a "shared folder"(so from the remote
machine's hard drive), but it runs -on- the local machine (I don't do
it often, but I just tried it)

In your case, you say it is not doing anything, which is strange..

And you said you want it to run on the remote machine. Or did you mean
you want to run it FROM the remote machine, but ON your local
machine? In both cases it is running from the remote machine..Or
rather, read from the remote machine's hard drive.
But,
File and printer sharing, it runs ON local. Meaning, it runs on the
local machine's CPU. So programs open up on the local machine.
And regarding Whose C drive it sees. It sees what the local one calls
C, which happens to be local.

Copying the file onto your local machine's drive might help if for
some odd reason it wasn't working.


If you wanted to run it from and on the -remote- machine, then double
clicking the file is not what you are looking for. File and printer
sharing is not what you are looking for.

The purpose of FnP, and
The way it works, is the file is stored on the remote machine. On the
remote machine's hard disk. So it is read from there, can be modified
and saved back there. . That is the limit of what can happen to those
files on the remote machine with "file and printer sharing"

So if you double click it, then whether it is a txt or an exe,
windows acts like it is any other local folder. The idea is that
although you are using the remote machine's hard drive

(note- it's not really "sharing"- like a business has co-owners.
sharing implies ownership. You don't each get a portion. It's
USING. remote runs the server whose service your local client
software is using. There are no owners when it comes to computers.
People own things. You use it, it's like it's yours. Who owns it is
about paper, not computers).

FnP makes it appear as if it makes no difference that it happens to
be located remotely. It may as well be your hard drive.

And so if you double click a file, it opens as if it was on your hard
drive - just your hard drive located remotely / far away. A directory
on the remote hard drive, is yours - maybe limited access like read-
only, or may be read-write access, but it's yours to use.

And if you execute a file, it opens as if it is on your hard drive .
It executes on your computer, so on your CPU, and typically puts files
on C which happens to be a drive in your computer.


Actually, as a test, I was on \\laptop, and put speedfan.exe into a
"shared folder" called qw. .. \\greycomp\qw .
I ran it from my laptop.. It opened on my laptop but extracted into
the directory it was installed in, which was the remote comp.
The reason was..
It ran on my laptop's CPU, so it sees my laptop's hardware.
But as far as directory/folder/storage is concerned. The file and
printer sharing makes it seamless.
It extracts into the current directory(the directory where it
resides).. that happens to be the remote comp, then fine.
Or, it extracts files into c:\something , then the files go on my
laptop hdd. Because C is always going to be the drive of the remote
machine. Which was my laptop.

The bottom line, is it uses the CPU of the local machine. And since
it typically installs files to C. it tends to put files on the local
machine.
And since it reads/writes files from C, e.g. the registry perhaps ,
it's certainly not going to be installing on the remote machine.

I know that was very repetitive, but what the heck.

Fact is.. you were very unclear.. It looked like you were talking
about running it on the remote machine.
Then you talked about a solution of copying it to a local folder..
Maybe if the concept is clearer - I doubt my post will help clarify
it- but if it does, then maybe you can get your terminology clearer.