newbie: COL2.2 - FTP/telnet refuse connection

newbie: COL2.2 - FTP/telnet refuse connection

Post by FiatX/1 » Fri, 26 Nov 1999 04:00:00



Greetings!

I'm trying to set up my first Linux system using Caldera OpenLinux 2.2,
which I want to use as a http server on a stand-alone network for web
development.  I've assigned 192.168.1.2 to the Linux box, and
192.168.1.10 to a Win95 box.

Using the Win95 node on the network, I've confirmed that the ethernet
connection is alive, and I can ping either machine from the other
successfully.

But, when I attempt to FTP, or telnet, from the Win95 box with the
IPaddress of the Linux box I get a momentary 'connected to remote host'
message and then immediately get a 'Remote host closed connection'
message using either FTP or telnet.

When I enter 'ftp 192.168.1.2' at a virtual terminal prompt on the Linux
box, I again get a 'connected to 192.168.1.2' message after which I
immediately get a '421 Service not available, remote server has closed
connection' message.

In neither case do I get a login prompt at all.

Obviously, I haven't got everything properly enabled, though I have
checked in the inetd.conf file and see ftp listed there okay (not
commented), but I don't see any ftp* files in the etc/ directory
(someone mentioned these in another thread, but I'm a newbie and don't
know what I'm looking for).  Also, I've done a 'netstat -a' and see that
both ftp and telnet are 'listening'.  In fact, when I attempt to do the
remote ftp from the Win95 box, and at the same time run netstat, I see
that there is a connection made between the appropriate IPaddresses, on
some port number (variable from run to run), and then the port goes into
a FIN-WAIT2 state and stays that way until I terminate the ftp app on
the Win95 box.

Any thoughts?

 
 
 

newbie: COL2.2 - FTP/telnet refuse connection

Post by patrick.them.. » Sat, 27 Nov 1999 04:00:00




Quote:

> Greetings!

> I'm trying to set up my first Linux system using Caldera OpenLinux
2.2,
> which I want to use as a http server on a stand-alone network for web
> development.  I've assigned 192.168.1.2 to the Linux box, and
> 192.168.1.10 to a Win95 box.

> Using the Win95 node on the network, I've confirmed that the ethernet
> connection is alive, and I can ping either machine from the other
> successfully.

> But, when I attempt to FTP, or telnet, from the Win95 box with the
> IPaddress of the Linux box I get a momentary 'connected to remote
host'
> message and then immediately get a 'Remote host closed connection'
> message using either FTP or telnet.

> When I enter 'ftp 192.168.1.2' at a virtual terminal prompt on the
Linux
> box, I again get a 'connected to 192.168.1.2' message after which I
> immediately get a '421 Service not available, remote server has closed
> connection' message.

> In neither case do I get a login prompt at all.

> Obviously, I haven't got everything properly enabled, though I have
> checked in the inetd.conf file and see ftp listed there okay (not
> commented), but I don't see any ftp* files in the etc/ directory
> (someone mentioned these in another thread, but I'm a newbie and don't
> know what I'm looking for).  Also, I've done a 'netstat -a' and see
that
> both ftp and telnet are 'listening'.  In fact, when I attempt to do
the
> remote ftp from the Win95 box, and at the same time run netstat, I see
> that there is a connection made between the appropriate IPaddresses,
on
> some port number (variable from run to run), and then the port goes
into
> a FIN-WAIT2 state and stays that way until I terminate the ftp app on
> the Win95 box.

> Any thoughts?

look in /var/log/messages(or warnings) for any messages

most probably you have to edit /etc/hosts.allow
(see the man-pages)

Sent via Deja.com http://www.deja.com/
Before you buy.

 
 
 

newbie: COL2.2 - FTP/telnet refuse connection

Post by FiatX/1 » Sun, 28 Nov 1999 04:00:00



> > Any thoughts?

> look in /var/log/messages(or warnings) for any messages

> most probably you have to edit /etc/hosts.allow
> (see the man-pages)

> Sent via Deja.com http://www.deja.com/
> Before you buy.

Okay, I checked ftpaccess, ftpusers and found nothing amiss.  I eventually
reinstalled to whole kit and kaboodle...a clean, fresh server.  What do you
know, it all works now.  I don't know why it wouldn't before, but thanks for
the response.

JRB

 
 
 

1. Reconfiguring network card - was Telnet/FTP refuse connection

This intended as a followup & re-direct to the posting I did previously
related to reconfiguring a Solaris 2.5.1 (x86) box onto a network.  The
previous title was identified as telnet & ftp refuse connections after
reconfig onto the network.

Somewhat embarassed, but a duplicate IP address for the newly installed box
was found,  hence the symptoms.

Now, the "real" problem seems to be:
(1) I'm using a 3COM 3C503 card that supports BNC, AUI & TP connections.
It's ugly I know, but considering the supported cards & the locations where
I bought it -- it was my only choice (suggestions welcome).

(2) I initially configured the machine on a Linksys TP hub & later
reconfigured it (tried) at an ISP that cabled up a BNC (different port)
connection.

(3) When the machine boots, it believes the ethernet I/F is elx0 --
shouldn't this be elx ??

Do I:
(a) Get an external BNC transceiver & an AUI cable?
(b) Get a small hub with a BNC port?
(c) Try to modify the /platform/i86pc/kernel/drv/elx.conf to support the
BNC?

If I try (c) what do I need to do???????  Are there ifconfig flags to set
IRQ/DMA addresses??  Are there release notes for this card that I'm not
aware of??

Any and all suggestions are appreciated,

TIA,
Larry

2. Caching only nameserver

3. telnet and ftp connection refused

4. ezonics EZ cam II

5. Connection refused -- how to telnet(ftp,rlogin, etc) my own machine?

6. Changing login prompt (NOT motd or shell prompt)

7. ftp & telnet,connection refused

8. Best Window Manager for Linux Laptop?

9. Connection refused error by incoming ftp and telnet

10. ftp and telnet: connection refused

11. NFS, ftp, telnet Connection refused

12. Connection Refused Message when trying to TELNET or FTP

13. HELP: Connection refused Telnet/FTP