Welcome to WebmasterWorld Guest from 54.159.112.92

Forum Moderators: bill

Message Too Old, No Replies

Remote Virtual Terminal

     
5:22 pm on Feb 28, 2005 (gmt 0)

Senior Member

WebmasterWorld Senior Member 10+ Year Member

joined:Sept 7, 2003
posts:1404
votes: 0


On a LAN, is it possible to connect remotely to one machine from another within the network and access files and applications - while allowing the (connected to) machine to still operate independently from the remote and vice versa?

In other words, the capability of something like PCAnywhere, but with virtual terminals.

6:25 pm on Feb 28, 2005 (gmt 0)

Administrator

WebmasterWorld Administrator coopster is a WebmasterWorld Top Contributor of All Time 10+ Year Member

joined:July 31, 2003
posts:12541
votes: 1


Are you using Windows XP Professional? Search your help for "Remote Desktop Connection".
5:38 am on Mar 1, 2005 (gmt 0)

Senior Member

WebmasterWorld Senior Member 10+ Year Member

joined:Sept 7, 2003
posts:1404
votes: 0


Thanks coopster. I'm looking at that solution and it may not work. The host system is running W2KPro, the client is a laptop with XP Home. I'm digging deeper into the documentation - lest I spoke to soon.

We want the client to connect to the host, without interrupting the host. OK, I know this probably isn't normal, at least from the perspective of using a PCanywhere type solution - where the host would be sitting idle in a darkened office after hours. Our host is rarely idle and the office lights rarely out.

10:03 am on Mar 1, 2005 (gmt 0)

Administrator from JP 

WebmasterWorld Administrator bill is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Oct 12, 2000
posts:14658
votes: 65


Any solution that uses a VNC type connection like Remote Desktop Connection, GoToMyPC, PCAnywhere, RealVNC, TightVNC, Ultr@VNC, etc. is going to interrupt the host somewhat. All of these solutions let you work on the remote machine in the same way as if you were at the terminal itself. If someone else is using that terminal at the time it will be noticeable on the remote screen to some extent. I guess it really depends on how you define interrupt.
11:50 am on Mar 1, 2005 (gmt 0)

Senior Member

WebmasterWorld Senior Member 10+ Year Member

joined:Sept 7, 2003
posts:1404
votes: 0


Interrupt needs no further definition. Ideally, the remote session would operate as a virtual terminal, leaving the host terminal free from any interference.

This is leading back to my original assesment of what we should be doing over here - pretty much what everyone else in the world does.. Set up a network server with net-aware applications and let the various net nodes access the applications thru the network.

The man just won't listen! :O

<aside>
I wonder if I would have more credibility if I

  • cut my hair, and shaved
  • wore a suit, a tie, and had shiny shoes
  • charged him 85K - 155K/yr for my expertise
    </aside>
  • 12:42 pm on Mar 1, 2005 (gmt 0)

    Senior Member

    WebmasterWorld Senior Member 10+ Year Member

    joined:Jan 29, 2002
    posts:980
    votes: 0


    Microsoft Terminal Services [microsoft.com] appears to do what you want, Citrix Metaframe does something similar, though both AFAIK require setting up a terminal server box.