Path: utzoo!utgpu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!reich From: reich@magnus.acs.ohio-state.edu (A Minor Diety) Newsgroups: alt.sources.wanted Subject: Re: Telnet into a PC Summary: I finally found it Keywords: telnet, TCP, IP, PC Message-ID: <1991Jun23.115136.12280@magnus.acs.ohio-state.edu> Date: 23 Jun 91 11:51:36 GMT References: <995@utsmips.csd.uts.EDU.AU> <2437@ccadfa.adfa.oz.au> <1991Jun22.034930.4543@jack.sns.com> Sender: news@magnus.acs.ohio-state.edu Organization: The Ohio State University - Academic Computing Service Lines: 112 Nntp-Posting-Host: bottom.magnus.acs.ohio-state.edu I figured if I looked long enough I would find something. I did. Anonymous FTP to wuarchive.wustl.edu in the directory pub/MSDOS-INCOMING The file is telnetd.zip. I am within 99% sure that this is what you want. It looks like it needs the Waterloo TCP programs, I know nothing about Waterloo, I use Clarkson drivers for everything. Anyway here is a piece of the document that accompanies it. ___________________________________________________________________________ The WATTCP Experimental TELNET Server This program is not perfected, but it does show what is possible as far as telnet service on a pc! I will post to comp.protocols.tcp-ip.ibmpc when I feel the program is more usable. Sorry about these notes being so brief, I hope someone will organize the information to make it a little more useful. Installation TELNETD.EXE uses the Waterloo TCP kernal to do all the network i/o. Installing the program can be simply performed by editing the ASCII configuration file named WATTCP.CFG. Try creating such a file with information like the following. my_ip=129.97.128.254 # substitute the PC's ip number netmask=255.255.254.0 # substitute your local net mask gateway=129.97.176.1 # substitute your local gateway Full installation instructions for installing Waterloo TCP based programs including information on how to use BOOTP and multiple gateways is available from sunee.uwaterloo.ca [129.97.128.196] in pub/wattcp/apps.zip. If you end up having no success with TELNETD, download that zip file, it will prove very useful. Once you have created the WATTCP.CFG file, copy it to the subdirectory of TELNETD.EXE. Load (and configure) an Ethernet packet driver, then run TELNETD. The screen should clear and a message will appear, indicating TELNETD is waiting for a caller. Using TELNETD Go to a second PC. Using Clarkson University (CUTCP) TELNET, telnet to the first PC. I haven't tried other TELNETs yet. When you TELNET to TELNETD, you will be given some information while TELNETD becomes a TSR. Almost immediately you will be at the DOS prompt. Yeah, you can do things now. Anything you type on the remote PC will appear to be typed on the TELNETD PC. LIST.COM, BORLAND C++, WordPerfect and many other programs are compatible (check out the character translation). There will be slight periodic delays. Using a 386 to run TELNETD will improve your performance. Remember that the remote PC is running VT 100 emulation and some keystrokes have to be remapped. I have written support for VT100 and VT220 terminals, but not everything has been tested yet. [Keymapping removed by me, Dick. See the manual when you get the package] Limitations: I *DID* mention that this is still experimental. Here are the current problems that come to mind: 1. screen updates are sporatic - hey, don't be picky 2. screen updates are inaccurate - I will improve my algorithms and the VT 100 (ANSI) escape sequences I use 3. PINGing the TELNETD PC will crash it. It runs into difficulties when it tries to ARP the remote PC. This can be fixed. Other ICMP packets may also cause problems. UDP/IP/TCP packets do not present problems. 4. Second or later attempts to TELNET to the PC do not return any useful message - this can be fixed I'm still glad 2nd and later attempts don't crash the pc! 5. When the user logs out, I just print a message to the screen. In the future I will probably reboot or something. Neat things you can do: 1. Install MARK, Packet Driver and TELNETD. The user can then TELNET in and run a batch file which includes the command RELEASE. This lets you start a job and disconnect your TELNET session (without rebooting or crashing) while the job complete!. The batch file could even reload the packet driver and TELNETD once it is ready to let you log in again! 2. Write your own password protection program. Future Enhancements TELNETD and the underlying kernel were all written by me. You can guess I've been pretty busy. I tried to design the kernel so oddball applications like TELNETD could be written in 'C' and without looking like some of the nastier UNIX or Bible sequences. Admittedly, this is the first version of TELNETD which works well enough to show some real promise, but I think it is pretty close to being usable. I'll post to comp.protocols.tcp-ip.ibmpc when most of the above bugs are fixed. In case you are interested in TCP applications programming, you may like to look at some of the other applications available. FTP to sunee.uwaterloo.ca [129.97.128.196] and get pub/wattcp/src.zip Erick -- DDDDDD k | reich@magnus.acs.ohio-state.edu D D ` cccc k kk (^8 | Dick C. Reichenbach D D i c kkk | "Quoth the raven 'Eat My Shorts'" and DDDDDD i cccc k kk WAS HERE | "Later Grizzley Dudes" - Bart Simpson