Unable to connect to 192.168.2.3 on port 631

Rüdiger Eisele eisele at softeiscons.de
Wed Dec 27 04:25:57 PST 2006


> >   This message is in MIME format.  The first part should be readable text,
> >   while the remaining parts are likely unreadable without MIME-aware tools.
> >
> > --168428555-1368032789-1166695173=:1395
> > Content-Type: TEXT/PLAIN; charset=ISO-8859-1
> > Content-Transfer-Encoding: QUOTED-PRINTABLE
> >
> >
> > Hello,
> >
> > On Dec 20 13:09 R=C3=BCdiger Eisele wrote (shortened):
> > > As you can see in the /var/log/cups/error_log
> > > the client reads the information of the server, but when it
> > > wants to connect to the server it cannot do so and a timeout arises.
> > >=20
> > > Here is an excerpt of the error:log from the client site.
> > >=20
> > > ... Added remote printer "Brezn_Drucker"...
> > > ... [cups-polld 192.168.2.3:631] Unable to connect to 192.168.2.3 on
> > >                                  port 631: Connection timed out
> >
> > You mix up different clients and the direction of the data flow.
> >
> > The "Added remote printer" is because the cupsd on the server machine
> > sends CUPS browsing information (via UDP) to the cupsd on the client
> > machine and the cupsd on the client machine accepts it.
> >
> > See for example
> > http://en.opensuse.org/SDB:CUPS_in_a_Nutshell
> > regarding "CUPS browsing",
> >
> > It is the opposite direction of the data flow when on the client
> > machine the cups-polld sends a request (via TCP) to the cupsd
> > on the server machine but the cupsd on the server machine does
> > not respond (e.g. because the request never reaches the cupsd
> > on the server machine because of wrong network setup or a firewall
> > or because the cupsd on the server machine does not accept the
> > request) and therefore the connection times out for the cups-polld
> > on the client machine.
> >
> > To let the cupsd on the server machine accept request from client
> > machines, note in particular the sections about "CUPS Server and
> > Firewall" and "Generalized Functionality for BrowseAllow and BrowseDeny"
> > in our documentation.
> >
> > On the client machine you can use for example
> > netcat -w 1 -z 192.168.2.3 631 && echo ok || echo failed
> > to test whether the cupsd on the server machine 192.168.2.3
> > accepts TCP connections and
> > netcat -w 1 -u -z 192.168.2.3 631 && echo ok || echo failed
> > for UDP.
> >
> > To test whether it can work at all (or whether e.g. a firewall
> > may block it at all), run on the server machine
> > netcat -l -p 1234 ; netcat -l -p 1234
> > and test on the client machine with
> > netcat -w 1 -z 192.168.2.3 1234 && echo ok || echo failed
> > echo hello | netcat -w 1 192.168.2.3 1234
> > and for UDP run on the server machine
> > netcat -u -l -p 1234
> > and test on the client machine with
> > netcat -w 1 -u -z 192.168.2.3 1234 && echo ok || echo failed
> > echo hello | netcat -w 1 -u 192.168.2.3 1234
> >
> >
> > Kind Regards
> > Johannes Meixner
> > --=20
> > SUSE LINUX Products GmbH, Maxfeldstrasse 5      Mail: jsmeix at suse.de
> > 90409 Nuernberg, Germany                    WWW: http://www.suse.de/
> > --168428555-1368032789-1166695173=:1395--
> >
>
>
> Hi,
>
> thanks for the reply.
>
> Here is the output from the client:
>
> kuchen:~ # echo "The Client"
> The Client
> kuchen:~ # netcat -w 1 -z 192.168.2.3 631 && echo ok || echo failed for UDP
> ok
> kuchen:~ # netcat -w 1 -z 192.168.2.3 631 1234 && echo ok || echo failed echo he llo | netcat -w 1 -u 192.168.2.3 1234
> ok
> kuchen:~ #
>
>
> Here is the output from the  Server
>
>
> Eisele at brezn:~/CUPS_Test> netcat -l -p 1234 ; netcat -l -p 1234
>  punt!  <- nothing happend, until I hit ctrl-c
>  punt!
> Eisele at brezn:~/CUPS_Test>
>
>
> on the server site I get
>
> D [21/Dec/2006:15:36:32 +0100] AcceptClient(): Refused connection from from 192.168.2.2; please check BrowseAllow/BrowseDeny settings
> D [21/Dec/2006:15:36:32 +0100] AcceptClient(): Refused connection from from 192.168.2.2; please check BrowseAllow/BrowseDeny settings
>
> cups.conf (Server)
> <Location />
> Encryption IfRequested
> Satisfy All
> Order Deny,Allow
> Deny From All
> Allow From 127.0.0.1
> Allow From 127.0.0.2
> Allow @LOCAL
> </Location>
> <Location /admin>
> Require group sys
> Encryption IfRequested
> Satisfy All
> Order deny,allow
> Deny From All
> Allow From 127.0.0.1
> Allow From 127.0.0.2
> Allow From @LOCAL
> </Location>
>
>
> BrowseAllow @LOCAL
> BrowseDeny All
> BrowseAddress kuchen
>
> It still does not work.
>
> Regards,
>
> Rüdiger
>
>


Hi
 I am still trying to get my remoteprinter to work.

 I deleted the printer with YAST and re-configured it only with the CUPS-Webinterface, as soon as I submit a testprintpage, the Status which is shown is "Unable to get printer status (client-error-forbidden)

In the CUPS-Documentation (SAM.HTML), I found in the client-configuration the follwing sentence:
Automatic Configuration of Print Queues

CUPS supports automatic client configuration of printers on the same subnet. To configure printers on the same subnet, do nothing. Each client should see the available printers within 30 seconds automatically. The printer and class lists are updated automatically as printers and servers are added or removed.

Is anybody able and willing to give me a pointer where I can find a cupsd.conf for the server and the client, which works?

It would really be a great help for me !

Thanks in advance.

Rüdiger








More information about the cups mailing list