running a program on another machine without terminal services

[Chrissirhc]

Hello,

How do I run a program on my lan. I have two computers "A" and "B". I'm on "B" and I want to run a program on "A" for "A".

Thanks

Chris

PS can I use the terminal services on windows 2000. I have a windows server disk.

 

[Dmasch]

You could use pcanywhere or VNC.
Only win2k server can you do terminal sessions not on the workstation.

 

[Bthibo]

Use VNC its a great remote program and free.

 

[Chrissirhc]

Okay I'll have a look at VNC. Where can I get it from?

By the time you reply I'll have probably found it.

What are the security implications from using when you are on the internet? (I have zonealarm installed).

Chris

 

[Chrissirhc]

All I get is "failed to connect to host/server" when I select a computer to connect to. I don't know what the user name is meant to be in this though. Maybe I have set that up incorrectly.

 

[Stiddy]

Try the NT or WIn2K resource kit....Look into (rcmdsvc.exe for the client, computer B) and (rcmd.exe from computerA)

ex: on computerA:

rcmd \\computerA c:\somebatch.bat

where rcmd is the executable to call
\\computerA is the client
c:\somebatch.bat is the program to call on computerA

 

[Chrissirhc]

Can't get VNC to work can anyone help. How does it log onto computers does it use normal authentication or does it have its own. Doesn't seem easy to use. Unless zonealarm is the culprit once again!!

 

[pbxman]

Hehehe..VNC is ok - as long as you also install Java Virtual Machine on every PC you want to use VNC with. To me - the added risk of leaving a network vulnerable to VNC using Java security (or lack thereof) scares the pants off me. We used to use VNC until i found out how easy it was to hack.

Better program..faster, easier, and uses NT security as well as regular password security is Remote Administrator by famatech.

Http://www.famatech.com

It's not free, but the trial is 30 days and once you go RAdmin..you'll scoff at VNC's horrible speed and poor visuals with refresh and screendraw problems..ugh..its a mess. Plus - its only $30 for a license.

Anyway - thats my 2¢..but Stiddy's on the right track..use rcmd if you can possibly do it. Adding software to solve software-related issues isn't always the best case. Especially if you're connecting to a server..stay away from having to install Virtual Machine! pbxman
Systems Administrator

Please let Tek-Tips members know their posts were helpful.

 

[hn4810]

Try NetMeeting Or Remote Desktop Connection. You can download them from Microsoft.

 

[Chrissirhc]

This software package will install the client portion of Remote Desktop on any of the following operating systems: Windows 95, Windows 98 and 98 Second Edition, Windows Me, Windows NT® 4.0, or Windows 2000. When run, this software allows older Windows platforms to remotely connect to a computer running Windows XP Professional with Remote Desktop enabled.

The above seems to say that winxp is needed does it work without? Netmeeting I found quite bad. Sorry if that sounds rude its unintentional. Thanks for your post. Have you any other information on these products?


This program pbxman is quite good. Although there is one problem. A user shouldn't be able to connect to my computer if an administrator is logged on. (Although I understand this is a remote administrator program) I'd like normal users to connect to another computer but not have administrative rights. This is fine when no one is logged into the "client" machine because the user will be limited to using their log on user name and password. But when I'm already logged on and say I've gone to the toilet without locking my computer they will get full access to the computer. Perhaps I can set it up so that they can only have user rights even thought they are remotely accessing the terminal when admin rights are on. I doubt this is the case though. Have you any ideas. PS Thanks for your post.

 

[Chrissirhc]

Really people only need to connect to computer "A" to do one thing. Load and then logon to AOL. Perhaps I could write somesort of special script that will do that through radmin. That would partly solve the problem. I'd still like administrators to connect to computer "A" whenever they like. How could I do this?

Thanks

Chris

 

[pbxman]

That is correct - this program (as well as all others) are designed to solely give you control of a remote PC's session. Thats it.

On top of that come all the features like built-in NT security, password protection for logging in, etc. This is where Terminal Services breaks away. Terminal services actually creates sessions for an authenticated user to use his/her NT permissions to run programs. Remote-Control software isn't designed to do that.

What i would suggest is that if using RADMIN, you assign NT permissions for only those users who are supposed to connect, and get in the habit of logging off if more users are going to be attaching to this PC, or creating a logoff script on the desktop that you run before disconnecting. Maybe even a screensaver that triggers a .vbs script to auto-logoff if idle for 2 min of inactivity? (heh - just brainstorming here..)

Keep in mind that it is not what remote-control software was designed for..terminal services was designed for the purpose of many users running their own programs.

I just wanted to offer advice on what i thought the easiest, fastest, and best remote-control software (non-trojan-based!) was.
pbxman
Systems Administrator

Please let Tek-Tips members know their posts were helpful.

 

[pbxman]

shoot - ya responded while i was still typing.

Anyway - it really sounds like terminal services is your best bet here. Are you saying that these users will connect to aol, and then disconnect...THEN another user will logon, connect, then disconnect..then an admin will logon and either watch, or work on something on the pc?

Whoever is connected will "control the pc". Anyone else who connects will see what the other person is doing, and they will fight over who's controlling it unless they choose "view mode".

If i was not able to use terminal services in your case - i would opt to use a logoff script, and make people use it when they complete their connection. Then, enforce (or try anyway) that nobody can connect to the machine while it is in use by another - the only time they are permitted to use it is when they see the ctrl+alt+del screen..and they can then logon as themselves.

Its definitely messy.. pbxman
Systems Administrator

Please let Tek-Tips members know their posts were helpful.

 

[Chrissirhc]

Funny you mentioned the trojan. A friend mentioned that when I sent him to the website.

Anyway..

Yeah basically you are right. I need a user from another computer just to load aol so they can have internet access via a proxy. Thats all.

But I've grown to like this remote access. I'd like to as an administrator have access fully no matter if I'm logged on the main computer.

The enforce idea is exactly what I need unless of course the person is logging on as administrator, which will be only me .

You see I have selected the option that the user has to wait thirty seconds timeout before they have remote access,

Is this something possible with radmin. Or is terminal services the only way?? and Remote Desktop Connection is that terminal services? Have you ever used it?


Is the only difference between remote access and terminal services the user rights?

thanks

Chris

 

[pbxman]

Remote Desktop is a feature of Windows XP only. You can download a client that will allow Windows 2000, 98, 95, NT to connect to an XP computer - however that target machine MUST be Windows XP.

With that said - Remote Desktop is kind of a mix between Remote Control and Terminal Services. It's controlled in a per-session basis (like Terminal services), requires an authenticated logon (like terminal services), and allows you to work as an admin using your desktop, have someone else logged in seeing their own desktop (not yours), and work completely separate from you.

The problem with that is having 5 users connected at the same time..all unaware of what others are doing..and trying to use AOL (only one modem).

For this reason only I would have to say terminal services or Remote desktop is not your best bet. If the PC were connected to the internet via high-speed (maybe it is?) then Remote Desktop would be a viable option..not quite as feature-packed as terminal services, but it uses sessions as Remote Admin/Remote Control software does not.

If you're sharing a dial-up AOL account, you only want one person at a time connected to the machine. If you're on high-speed, then many users can browse the internet at the same time in their own Terminal services or Remote Desktop environments. Note - using terminal services or remote desktop does NOT allow you to view their sessions either...kinda scary. But - they will only have the permissions you assign them as users on that PC - not local admin rights unless you assign them as admins on that pc.

It's a toss-up. Really up to how you want to manage it, how secure you want it to be, and what resources you have available to work on this. You'd need Windows XP to use Remote access, and you'd still have the modem-sharing issue with dial-up. Remote Administrator/Remote Control is the best option if single-sessions are the goal otherwise what's to keep people from logging off of their terminal session/Remote Desktop session?...they probably would stay connected all day.

Sorry for the long posts..but these are all technologies that are fairly hard to explain. I've used all methods (including remote desktop), and switched back to Remote Administrator. You just cant beat the simplicity and security. You'd just have to lock the user procedures down more with RAdmin.

Hope that helps. pbxman
Systems Administrator

Please let Tek-Tips members know their posts were helpful.