Message Board -  Archive

[ Login ] [ Create Account ]
[ Board List ] [ View Board ] [ Post Reply ]
  Author  Subject: Re: telnet and ftp to Linux server on NT LAN
Archive  

Posted on 07-20-2000 02:14 a.m. ET  reply

Original Poster: Mark Krentel

> "Winsock error: host refuses connection".

If this error message is accurate (maybe yes, maybe no), it's saying
that the request got through but was denied. But before we try that,
let's check some basic networking things to narrow the problem.

First, can you ping from NT to Linux? Win 95/98 has a builtin ping
that you can run from a DOS command window, so probably NT does too.

I haven't used "Reflection X". Win 95/98 has a no-frills telnet and
ftp available from the DOS command window. Try that to see if the
error is different (or if it works). Or try it from another Unix
machine (if you have one).

Since this is a new install, you could double-check that your DNS name
server is giving the right answer. You can check that in Linux with
nslookup.

But if Linux really is refusing the connection, here are some things
to try. First, is there a firewall (ipchains) on the Linux machine?
"ipchains -L" will list the rules.

Check that inetd is running, "ps aux | grep inetd" will tell you.
Check that the telnet/ftp entries in /etc/inetd.conf are there and not
commented out. And see if they're run through tcpd (probably yes).
Mine has:

ftp stream tcp nowait root /usr/sbin/tcpd in.ftpd -l -a
telnet stream tcp nowait root /usr/sbin/tcpd in.telnetd

Try "telnet localhost" on the Linux machine (to itself) to check that
the daemon is there.

What is in the hosts.allow and hosts.deny files? Try disabling the
access control (temporarily). You can do this by: (1) mv both files
to new names (so there is no hosts.allow or hosts.deny files), or (2)
put "ALL: ALL" as the first line in the allow file. If that makes any
difference, then it's probably a tcpd issue.

And remember that you need to send "kill -HUP <inetd pid>" to tell
inetd of any changes to inetd.conf (or reboot). That shouldn't be
necessary for changes to hosts.allow or deny, but it can't hurt.

And check /var/log/messages for clues. Usually when a server denies a
request, it puts a message there saying so.

I'm guessing it's probably ipchains that's blocking the request.
Either that or tcpd (controlled by allow/deny files).

--Mark

< Previous 1 Next >

Site Contents