[SOLVED] Connection refused

levencp · 02-11-2011, 01:54 PM

I am in the process of setting up a remote printer on a Red Hat server from an AIX server and cannot connect to the queue. I have gone so far as to disable the firewall - still no good. It also refuses a telnet from the AIX host even when the firewall is disabled.
telnet clt0ds33
Trying...
telnet: connect: A remote host refused an attempted connect operation.

SSH does work however.

I am new to linux and I am sure this is a simple security issue. Thanks in advance.

corp769 · 02-11-2011, 01:59 PM

Do you have telnet even running?

unixfool · 02-11-2011, 02:08 PM

Hrmm...

I'd sniff the traffic to see what's going on. And maybe use nmap to scan the printer to see what services are running.

corp769 · 02-11-2011, 02:15 PM

Quote:

Originally Posted by unixfool

Hrmm...

I'd sniff the traffic to see what's going on. And maybe use nmap to scan the printer to see what services are running.

And at least to see what ports are accepting connections...

wpeckham · 02-12-2011, 08:57 PM

Why would you expect telnet to work?
The use of telnet has been depreciated, and it is not installed or enabled by default in any current version of Linux.
On another topic: what does telnet have to do with setting up a printer?
I have printed from AIX queues to Linux queues, (and the reverse case) without problems. Can you provide more information?

Reuti · 02-13-2011, 03:44 AM

Quote:

Originally Posted by levencp

telnet clt0ds33
Trying...
telnet: connect: A remote host refused an attempted connect operation.

Did you use a plain telnet, or did you also specify the port 515 during your test?

Reuti · 02-13-2011, 03:46 AM

Quote:

Originally Posted by wpeckham

Why would you expect telnet to work?
The use of telnet has been depreciated, and it is not installed or enabled by default in any current version of Linux.
On another topic: what does telnet have to do with setting up a printer?
I have printed from AIX queues to Linux queues, (and the reverse case) without problems. Can you provide more information?

Telnet can be used in certain situation as a debugging tool. In this case: can I connect to port 515 of printer server at all?

wpeckham · 02-14-2011, 10:39 AM

I see, you did not EXPECT a telnet connection, only that telnet would show that the port was active.

It sounds as if you may need to check:
1. are there software or hardware firewalls between? Something may be blocking.
2. is the printer service LISTENING? Cups can be configured to listen for IPP but not for traditional LPR (different ports), and all print server can be set to listen ONLY for local jobs (from localhost) and not listen for connections from the network.

Please let us know what you find!

trickykid · 02-18-2011, 10:24 AM

telnet <hostname> <port>

If you don't specify the port, it's going to use the default telnet port and if that's not running, will give you connection refused or hang on you.

If the service you have running is listening on the port specified in your telnet, it should connect. If it doesn't, either there's something blocking it or the service isn't running.

levencp · 02-28-2011, 07:26 AM

None of the suggestions helped but the answer was the deamon cups_lprd was not running.

unixfool · 02-28-2011, 10:08 AM

Actually, most of those suggestions were asking you to use telnet/nmap/tcpdump to test to see if that service was running.

What took you so long to determine this and why are you saying that none of the suggestions helped?

Some of the suggestions that steered you in the right direction:

Quote:

Originally Posted by corp769

And at least to see what ports are accepting connections...

Quote:

Originally Posted by Reuti

Did you use a plain telnet, or did you also specify the port 515 during your test?

Quote:

Originally Posted by Reuti

Telnet can be used in certain situation as a debugging tool. In this case: can I connect to port 515 of printer server at all?

Quote:

Originally Posted by wpeckham

I see, you did not EXPECT a telnet connection, only that telnet would show that the port was active.

It sounds as if you may need to check:
1. are there software or hardware firewalls between? Something may be blocking.
2. is the printer service LISTENING? Cups can be configured to listen for IPP but not for traditional LPR (different ports), and all print server can be set to listen ONLY for local jobs (from localhost) and not listen for connections from the network.

Please let us know what you find!

Quote:

Originally Posted by trickykid

telnet <hostname> <port>

If you don't specify the port, it's going to use the default telnet port and if that's not running, will give you connection refused or hang on you.

If the service you have running is listening on the port specified in your telnet, it should connect. If it doesn't, either there's something blocking it or the service isn't running.

So, you had 5 answers that were pretty much all spot-on and you say that none of the solutions were correct. The last one was definitely correct. Then it took you 10 days to come back and say "none of the suggestions helped".