From owner-freebsd-questions Tue Jul 1 00:48:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA16373 for questions-outgoing; Tue, 1 Jul 1997 00:48:18 -0700 (PDT) Received: from andrsn.stanford.edu (root@andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA16366 for ; Tue, 1 Jul 1997 00:48:16 -0700 (PDT) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.8.5/8.6.12) with SMTP id AAA00419; Tue, 1 Jul 1997 00:48:11 -0700 (PDT) Date: Tue, 1 Jul 1997 00:48:10 -0700 (PDT) From: Annelise Anderson To: Marco Molteni cc: freebsd-questions@FreeBSD.ORG Subject: Re: How to "telnet" to a DOS pc ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 30 Jun 1997, Marco Molteni wrote: > Hi all > > Although a bit off-topic, here you are my question: > > I'd like to be able to control (ie: executing programs on it) a > DOS + win3.1 box (let's call it A) via another machine > (running FreeBSD or DOS, let's call it B). Trying to do this--talk to my office computer from home, when it was running dos/win3.1--was a major factor in my decision to try FreeBSD. There are a number of software packages generally designed to be run on both the host and the remote--PCAnywhere, LapLink, Close-UP, and ProComm Plus ("be a host pc") are four of them. Generally, the 3.1 box you want to reach (the remote) has to be running the software, usually from Windows. Since 3.1 is such a poor multi-tasker, it often gets hung up; and even a program with a feature to "always reboot on disconnect" (PCAnywhere has this) will not always work. You need to be able to do a hard reboot (power interrupt) remotely (I never established this capability; it was fairly expensive when I looked into it). It is a nightmare. Windows 95 has much better capabilities for doing this sort of thing, especially from NT, but I've not tried it. Annelise > The connection beetween A and B can be ethernet or a more complex one, > ie: A - ethernet - gateway - telephone line - B (but I don't think this > can be a problem since one can use tcp and netbios over tcp). > > In Unix terms, the DOS pc should allow a sort of rlogin or telnet. > > This is because it happens often that I have to troubleshoot box A, > which is at the other end of the building or at the other end of the town. > > Thanks > > Marco Molteni > Computer Science student at the Universita' di Milano, Italy. > "The time has come", the Walrus said, "to talk of many things". > > > >