by d.. » Fri, 30 Aug 1996 04:00:00
Hi!
Our rapidly growing Internet software development company is in the process of
creating a Telnet Daemon for Windows. We would like to obtain a general level
of interest in a Telnet Daemon for Windows from the Internet community.
Thank You
by Birger Wathn » Sat, 31 Aug 1996 04:00:00
Finally?
Sun's PC/NFS package includes both telnet and ftp daemons.
It's a very nice thing to have, as I can telnet into remote PC's
and edit their config.sys and autoexec.bat files. Don't try to use
edit, as you can't get Alt keys over telnet. Install elvis
(a good vi clone) instead.
Birger
> Hi!
> Our rapidly growing Internet software development company is in the process of
> creating a Telnet Daemon for Windows. We would like to obtain a general level
> of interest in a Telnet Daemon for Windows from the Internet community.
> Thank You
by Dan Norri » Sat, 31 Aug 1996 04:00:00
How much will it cost? NCSA telnet provides at least an ftp daemon and
probably telnet (it's been a while since I've messed with them) too.
Since that's free software (at last check), how can you compete?
Dan
1. Linux Telnet Daemon security setup problem with a Windows client
A funny little question for you all....
I have a little LAN set up at home: a Linux client (Mandrake 7.0), a
Win98 client and a linux box acting as a dial on demand, masquarading
router for the other two (redhat 6.2).
Everything appears to work fine on the ping side but I'm having problems
with telnet connections from the windows box to the router box and
security set via the /etc/hosts.allow file.
A few more details:
The local subnet is 192.168.1.0 - the linux router is 192.168.1.1, the
linux client is 192.168.1.10 and the windows box is 192.168.1.11 (all
masks are 255.255.255.0)
The linux router has an /etc/hosts file of:
127.0.0.1 localhost localhost.privatedomain
192.168.1.1 modemrouter.privatedomain modemrouter
192.168.1.10 linuxclient.privatedomain linuxclient
192.168.1.11 win.privatedomain win
It also runs as a caching nameserver.
The /etc/hosts.deny file on the router denies all, the /etc/hosts.allow
is:
in.telnetd: LOCAL, .privatedomain
in.rshd: LOCAL, .privatedomain
Now. if I telent in from the linux clinet (192.168.1.10) then all is
fine. However, if I telnet in from the windows box, it gets connection
refused and the /var/log/secure log contains:
May 21 06:26:28 modemrouter in.telnetd[472]: warning: /etc/hosts.allow,
line 6: can't verify hostname: gethostbyname(win.privatedomain) failed
May 21 06:26:28 modemrouter in.telnetd[472]: refused connect from
192.168.1.11
Note: line 6 of hosts.allow is the above line for telnetd.
The win box is set up with the static IP of 192.168.1.11 (and can ping
nicely thankyou)
It uses dns, hostmane: win, domain privatedomain, dns server 192.168.1.1
It has a gateway set as 192.168.1.1
Any ideas more than welcome....
Cheers
Steve
Sent via Deja.com http://www.deja.com/
Before you buy.
2. MPROTECT
3. Advice - finally migrating, Windows to Linux
4. cyrus imapd
5. Windows 2000 is finally stable....
7. set up daemons for telnet, etc
8. vi option
9. Can't telnet to Imap daemon ports
10. Source for telnet daemon/client w. RFC1408/1409 ?
11. Telnet Daemon