telnet: connect to address 127.0.0.1: Connection refused
phh...@gmail.com
>From searching the archives, I got this:
«Go to /etc/xinetd.d/telnet
and edit the line which says **disable = yes** so it reads
**disable = no** (ignore the **)
After that change restart xinetd with the command
service xinetd restart»
that I have followed, but still getting:
$ telnet localhost 9734
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused
telnet: Unable to connect to remote host: Connection refused
$
I am running Fedora Core 6 and I have the telnet-server package
installed.
Any further ideas?
Thanks in advance,
Paul
David Schwartz
phh...@gmail.com wrote:
> $ telnet localhost 9734
> Trying 127.0.0.1...
> telnet: connect to address 127.0.0.1: Connection refused
> telnet: Unable to connect to remote host: Connection refused
> $
>
> I am running Fedora Core 6 and I have the telnet-server package
> installed.
Where did '9734' come from?
DS
phh...@gmail.com
I am trying to use the Ryacas package and from its site I get the
following:
«2. Telnet problems. If you are unable to get a connection at all try
to connect to yacas manually using:
telnet localhost 9734
and if that fails there is likely a configuration problem with telnet
on your machine.»
Ryacas is a package of R and its site is at
http://code.google.com/p/ryacas/
Paul
C.J. Steele
`lsof -i:<port>` (where "<port>" is the port-number identified by
netstat) to identify what service is listening on said port. Once
you've verified what port you're connecting to, show us a listing of
your ipchains (`iptables -nL`) rules.
If `netstat` and `lsof` are foreign to you, use `nmap -p 1-65535
localhost` to see what services you've got open...
-C
On Nov 19, 8:43 am, phh...@gmail.com wrote:
> David Schwartz wrote:
> > > $ telnet localhost 9734
> > > Trying 127.0.0.1...
> > > telnet: connect to address 127.0.0.1: Connection refused
> > > telnet: Unable to connect to remote host: Connection refused
> > > $
>
> > > I am running Fedora Core 6 and I have the telnet-server package
> > > installed.
>
> > Where did '9734' come from?I am trying to use the Ryacas package and from its site I get the
phh...@gmail.com
> Use `netstat -nl | grep -- ^tcp` to identify listening services and
> `lsof -i:<port>` (where "<port>" is the port-number identified by
> netstat) to identify what service is listening on said port. Once
> you've verified what port you're connecting to, show us a listing of
> your ipchains (`iptables -nL`) rules.
>
> If `netstat` and `lsof` are foreign to you, use `nmap -p 1-65535
> localhost` to see what services you've got open...
I get this:
# nmap -p 1-65535 localhost
Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2006-11-19
15:21 WET
Interesting ports on localhost.localdomain (127.0.0.1):
Not shown: 65522 closed ports
PORT STATE SERVICE
22/tcp open ssh
23/tcp open telnet
25/tcp open smtp
111/tcp open rpcbind
139/tcp open netbios-ssn
445/tcp open microsoft-ds
631/tcp open ipp
885/tcp open unknown
904/tcp open unknown
2207/tcp open unknown
2208/tcp open unknown
8000/tcp open http-alt
10000/tcp open snet-sensor-mgmt
Nmap finished: 1 IP address (1 host up) scanned in 3.442 seconds
#
Paul
C.J. Steele
why you're getting a connection refused when you try to telnet to
9734... there's nothing running on 9734.
I bet you don't have any trouble connecting to the standard telnet
port, so what happens when you just `telnet localhost`?
Cheers,
-C
On Nov 19, 9:23 am, phh...@gmail.com wrote:
> C.J. Steele wrote:
> > Use `netstat -nl | grep -- ^tcp` to identify listening services and
> > `lsof -i:<port>` (where "<port>" is the port-number identified by
> > netstat) to identify what service is listening on said port. Once
> > you've verified what port you're connecting to, show us a listing of
> > your ipchains (`iptables -nL`) rules.
>
> > If `netstat` and `lsof` are foreign to you, use `nmap -p 1-65535
> > localhost` to see what services you've got open...I get this:
>
> # nmap -p 1-65535 localhost
>
> Starting Nmap 4.11 (http://www.insecure.org/nmap/) at 2006-11-19
David Schwartz
phh...@gmail.com wrote:
> I am trying to use the Ryacas package and from its site I get the
> following:
>
> «2. Telnet problems. If you are unable to get a connection at all try
> to connect to yacas manually using:
> telnet localhost 9734
> and if that fails there is likely a configuration problem with telnet
> on your machine.»
>
> Ryacas is a package of R and its site is at
>
> http://code.google.com/p/ryacas/
Okay, you have some massive confusion. A 'telnet server' is used to
provide the telnet service and has nothing to do with some other
services, such as Ryacas. The confusion comes from the fact that you
are using the telnet *client* to connect to a Ryacas server. Whether or
not you have a telnet server won't make any difference, since that's
not what you're trying to connect to.
The steps that you took to get your telnet server running aren't going
to help you at all. You need to get Ryacas running, and then you can
connect to it with any client you want.
DS
phh...@gmail.com
> > I am trying to use the Ryacas package and from its site I get the
> > following:
>
> > «2. Telnet problems. If you are unable to get a connection at all try
> > to connect to yacas manually using:
> > telnet localhost 9734
> > and if that fails there is likely a configuration problem with telnet
> > on your machine.»
>
> > Ryacas is a package of R and its site is at
>
> provide the telnet service and has nothing to do with some other
> services, such as Ryacas. The confusion comes from the fact that you
> are using the telnet *client* to connect to a Ryacas server. Whether or
> not you have a telnet server won't make any difference, since that's
> not what you're trying to connect to.
>
> The steps that you took to get your telnet server running aren't going
> to help you at all. You need to get Ryacas running, and then you can
> connect to it with any client you want.
Thanks to all. The problem is solved and the solution is at
http://marc.theaimsgroup.com/?l=r-help&m=116397290826793&w=2
Paul
Paul