🚀 go-pugleaf

In article <1992Aug30.032200.7309@msuinfo.cl.msu.edu> chena@crs.cl.msu.edu (Antony Chen) writes:
>From: chena@crs.cl.msu.edu (Antony Chen)
>Subject: Re: Unix to PC communications
>Date: 30 Aug 92 03:22:00 GMT
>achel@ctp.com (Alex Chelminsky) writes:
>
>>I'm looking for a program that runs under Unix and can drive a PC
>>over a TCP/IP network. That is, a program that would run on a 
>>window on a workstation and trigger a program that's listening
>>on the PC (something like an asynch comm program that is in
>>"listen" mode); when I call that IP address, the window will take
>>over the PC, and the keystrokes on the workstation will be interpreted
>>on the PC.
>>There is an equivalent program for asynch communications called
>>PC-anywhere by Symantec, but it works over the serial ports
>>between two PCs.
>
>>Any suggestions?
>
>This may be a wild goose chase, but I saw some TCP/IP freeware on
>wuarchive...check it out...

	There is a program on sunee.waterloo.edu (129.97.50.50) in 
	pub/wattcp. It is called telnetd and it runs on a PC with an 
	Ethernet card and a packet driver interface to the card. Basically
	the program runs on a PC "listening" to the Ethernet port. One 
	can telnet from a remote machine (I tried from a Sun 3/60 and it
	works) to the PC that is running telnetd. Once connection is 
	established then whatever is typed on the remote computer is echoed
	on the PC and the output is also sent to the remote machine. When
	I tried it from the Sun I started a telnet session in a window
	(under X windows) and telnetted to the PC (which was already running
	telnetd) and after connection was established I had the DOS prompt
	in a window on the Sun !

	Couple of points to be mentioned here:
	- Security is extremely weak in telnetd. The only security is in
	the form of a password that is [optionally] required of any user
	attempting to connect to the PC. The password is stored in an 
	non-crypted form in the config file on the PC. The online documen-
	tation makes a note of the weak security.
	- When the remote machine closes the telnet session it reboots the 
	PC
	- I have not yet tried running the telnetd program under Windows 3.1
	I shall try it out sometime today.
	- The telnetd program takes over the PC when waiting for incoming
	telnet requests i.e. the PC can't be used for anything else
	- I am not sure if multiple incoming telnet requests can be 
	handled (I have not read the manual completely yet).

	Venkat