Sharing application software across wireless network

That would require you sharing *critical parts of the O/S* exposing it to attack along with whatever application you're trying to share. Malware can easily attack a machine from the other computer. That's why you install the application on both machines and not go into sharing applications, unless you have a computer on the network that's doing application sharing on a network, which takes some expertise in setting up that computer along with its protection. Sharing files, folders and printer is one thing, but sharing applications in the manner you're wanting to do is a NO - NO.

If this is an NT based O/S such as Win 2K or XP, then you should try to set-up some kind of security/harden them to attack, which is particularly true for a wireless network that can be hacked at the drop of a hat with them being all over the top of the machines.

wpa-psk security enabled on router...firewall installed and active.

thought I had googled yesterday and found clear answer of how to...unfortunately couldn't do it and today cannot find the same info.

What has any of it got to do with you sharing resources on the LAN? You have already opened up the machines with the sharing that you have done and you want to take it further. That wireless encryption doesn't mean anything if a hacker wants to come after it. But really, all you or someone on the network with a machine has to do with the happy fingers clicking on a dubious Web sites or opening dubious email that's that will lead to the compromise the machine and any other machines you have opened up in the manner you're wanting to do, it's over.

Well, if you do find it, I wish you the best of luck The only way I would do something like that is if I was on an all wire network, not wireless, with the machines properly secured and protected.

Duane :)

On Sun, 22 Oct 2006 20:04:01 GMT, Rex's Mom wrote in :

Google "VNC".

Why? You add the performance penalty of not using the local drive.

That and a great many programs won't work without being "installed" properly. So even if you did simply mount \\\\otherbox\\c$\\progra~1\\application from the remote machine it wouldn't do you much good. You can, in some circumstances, install the application itself to a network share and run it from there. As in, mount \\\\otherbox\\sharename as a local drive letter and then use that as the install path. But that would only get you the app files on the share, you'd still have to run an installer on each machine. Some programs will let you execute stuff without installing but then you don't get the start menu program setups.

So really, why bother?

Rex's Mom:

Sharing software can be easy, or it can be difficult. There is some software, usually old win98 level programs (and below), that do not install themselves into the regestry on the local OS. For those, and DOS programs, simply share the drive on the machine with the software. Then use Netwok Manager to connect or map the shared drive on to the local machine. Go to the executable in the directory in which it is located double click on it. If it runs, then you can set up a shortcut to access it and everything will be fine. If not, then it is likely software that has to be installed on your local machine.

Another option is to have windows server on one machine where you want the software to share. Implement remote server and download the windows remote desktop from MS. Install it on the remote machine. Then you simply connect to the server and that desktop will open on your local machine and it will run, on the server, but your remote machine will control it.

That is about it. (You could also try loading the software on the remote machine in the first example but have it store itself on the shared drive, in the same directory that the shared drives software is located. You risk losing it on the shared drive machine, but it could work fine from either machine. Just use it on one machine at a time. This might violate your license.)

Just remember in all of the above possibilities, the machine that shares the drive or desktop must remain on. Otherwise the remote machine will not be able to run the software shortcut installed there.

Rich