<br>
<br><tt><font size=2>Vivek <vivek@visolve.com> wrote on 19/10/2009
13:01:55:<br>
<br>
> Hello Chris,<br>
> <br>
> >>On the SERVER . .<br>
> >>Find which port the tunnel is using netstat -napt|grep agent<br>
> <br>
> 0.0.0.0:4026<br>
> 127.0.0.1:6026<br>
</font></tt>
<br><tt><font size=2>Yup</font></tt>
<br>
<br><tt><font size=2>> <br>
> >>Look in /home/vivek/.nx/C-sesssion-id/cups/printers.conf<br>
> >>for the line which looks like <br>
> <br>
> In the /home/vivek/.nx/C-tsrv-co-2025-<br>
> EF5FDA64DC13661E79A2390848AB2287/cups/printers.conf file,<br>
> <br>
> DeviceURI nxipp://vivek:185a7123bb248d5e@127.0.0.1:<br>
> 12025/printers/LaserJet_P2015<br>
> <br>
There you go . . </font></tt>
<br>
<br><tt><font size=2>> and in the /home/vivek/.nx/C-tsrv-co-2025-<br>
> EF5FDA64DC13661E79A2390848AB2287/cups/cupsd.conf<br>
> Listen localhost:11026<br>
> </font></tt>
<br>
<br><tt><font size=2>This is because of a patch which to allow you to connect
to the server userspace cupsd.</font></tt>
<br>
<br><tt><font size=2>Sometimes it tries 10025 and bumps into postfix instead</font></tt>
<br>
<br><tt><font size=2><br>
> #netstat -nap | grep cups<br>
> 127.0.0.1:11026<br>
> ::1:11026<br>
> <br>
> In the nxsession, I pointed the browser,<br>
> <br>
> </font></tt><a href=http://localhost:4026/><tt><font size=2>http://localhost:4026</font></tt></a><tt><font size=2><br>
> <br>
> I gave the username/pwd - vivek/185a7123bb248d5e But only homepage<br>
> came, i am unable to access other pages like<br>
> <br>
</font></tt>
<br><tt><font size=2>If you mean the cups home page, then at least you
are connecting to cups.</font></tt>
<br>
<br>
<br><tt><font size=2>> </font></tt><a href=http://localhost:4026/admin><tt><font size=2>http://localhost:4026/admin</font></tt></a><tt><font size=2>
or </font></tt><a href=http://localhost:4026/admin/><tt><font size=2>http://localhost:4026/admin/</font></tt></a><tt><font size=2>
or <br>
> printers page...<br>
> <br>
> At the same time, ON THE CLIENT SIDE,<br>
> <br>
</font></tt>
<br><tt><font size=2>Hmmmm</font></tt>
<br>
<br><tt><font size=2>> In the /home/vivek/.nx/cups/error_log file, I
saw a line..<br>
> <br>
> cupsdSendError: 15 code=401 (Unauthorized)<br>
> <br>
> If we try to print, same error in the /home/vivek/.nx/C-tsrv-<br>
> co-2025-EF5FDA64DC13661E79A2390848AB2287/cups/log/error_log,<br>
> <br>
> " recoverable: Network host '127.0.0.1' is busy; will retry in
30 seconds... "<br>
> <br>
</font></tt>
<br><tt><font size=2>OK</font></tt>
<br>
<br><tt><font size=2>Now try conecting to the client userland cupsd directly
on THE CLIENT.</font></tt>
<br>
<br><tt><font size=2>It normally listens on 20000 or so.</font></tt>
<br>
<br><tt><font size=2>You can find it by ps -ef |egrep "cupsd.*nx/cups/cups.conf"</font></tt>
<br>
<br><tt><font size=2>It will have a -c path-to-its-cups.conf file as part
of its command line</font></tt>
<br>
<br><tt><font size=2>You need to get the password from THE SERVER as before
in</font></tt>
<br>
<br><tt><font size=2>/home/vivek/.nx/C-tsrv-co-2025-EF5FDA64DC13661E79A2390848AB2287/cups/printers.conf</font></tt>
<br>
<br><tt><font size=2>If you don't get to see the admin page by connecting
on THE CLIENT,</font></tt>
<br><tt><font size=2>then you need to check out what the relevant cups.conf
file says regarding authority.</font></tt>
<br>
<br><tt><font size=2>You can edit it and restart the cupsd . . .</font></tt>
<br>
<br><tt><font size=2>with /usr/sbin/cupsd -c /home/vivek/.nx/path-to-cupsd.conf</font></tt>
<br>
<br><tt><font size=2>I can't see why it would stop you printing, because
it normally just has require user and allow from 127.0.0.1.</font></tt>
<br>
<br><tt><font size=2>My cupsd.conf(s) look like this :-</font></tt>
<br>
<br><tt><font size=2>
TempDir /home/vivek/.nx/cups/spool/tmp</font></tt>
<br><tt><font size=2>
StateDir /home/vivek/.nx/cups/certs</font></tt>
<br><tt><font size=2>
CacheDir /home/vivek/.nx/cups/cache</font></tt>
<br><tt><font size=2>
RequestRoot /home/vivek/.nx/cups/spool</font></tt>
<br><tt><font size=2>
ServerRoot /home/vivek/.nx/cups</font></tt>
<br><tt><font size=2>
ErrorLog /home/vivek/.nx/cups/error_log</font></tt>
<br><tt><font size=2>
LogLevel debug</font></tt>
<br><tt><font size=2>
Port 20000</font></tt>
<br><tt><font size=2>
Browsing Off</font></tt>
<br><tt><font size=2>
ServerName localhost</font></tt>
<br>
<br><tt><font size=2>
<Location /></font></tt>
<br><tt><font size=2>
Order Deny,Allow</font></tt>
<br><tt><font size=2>
Deny From All</font></tt>
<br><tt><font size=2>
Require user vivek</font></tt>
<br><tt><font size=2>
AuthType Digest</font></tt>
<br><tt><font size=2>
Allow from 127.0.0.1</font></tt>
<br><tt><font size=2>
</Location></font></tt>
<br><tt><font size=2>
StateDir /home/vivek/.nx/cups/certs</font></tt>
<br><tt><font size=2>CacheDir /home/vivek/.nx/cups/cache</font></tt>
<br>
<br>
<br><tt><font size=2>Did you rename the account to vivek from something
else ??</font></tt>
<br>
<br>
<br><tt><font size=2>Has anything arrived into the SPOOL directory recently
???</font></tt>
<br>
<br>
<br><tt><font size=2>If /home/vivek/.nx/cups/printers.conf has a printer
set up in it, then you could</font></tt>
<br>
<br><tt><font size=2>try putting : -</font></tt>
<br>
<br><tt><font size=2>
ServerName localhost:20000 ( or whatever the
port is )</font></tt>
<br>
<br><tt><font size=2>into /home/vivek/.cups/client.conf </font></tt>
<br>
<br><tt><font size=2>then restarting oowriter or something and seeing if
you can spool.</font></tt>
<br><tt><font size=2>Dont forget to delete /home/vivek/.cups/client.conf
afterwards !!</font></tt>
<br>
<br>
<br><tt><font size=2>> <br>
> Thanks<br>
> Vivek<br>
> <br>
</font></tt>
<br><tt><font size=2>> <br>
> ________________________________________________________________<br>
> Were you helped on this list with your FreeNX
problem?<br>
> Then please write up the solution in the FreeNX Wiki/FAQ:<br>
> <br>
> </font></tt><a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ"><tt><font size=2>http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</font></tt></a><tt><font size=2><br>
> <br>
> Don't forget to check the NX Knowledge
Base:<br>
> </font></tt><a href=http://www.nomachine.com/kb/><tt><font size=2>http://www.nomachine.com/kb/</font></tt></a><tt><font size=2>
<br>
> <br>
> ________________________________________________________________<br>
> FreeNX-kNX mailing list --- FreeNX-kNX@kde.org<br>
> </font></tt><a href="https://mail.kde.org/mailman/listinfo/freenx-knx"><tt><font size=2>https://mail.kde.org/mailman/listinfo/freenx-knx</font></tt></a><tt><font size=2><br>
> ________________________________________________________________<br>
> ________________________________________________________________<br>
> Were you helped on this list with your FreeNX
problem?<br>
> Then please write up the solution in the FreeNX Wiki/FAQ:<br>
> <br>
> </font></tt><a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ"><tt><font size=2>http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</font></tt></a><tt><font size=2><br>
> <br>
> Don't forget to check the NX Knowledge
Base:<br>
> </font></tt><a href=http://www.nomachine.com/kb/><tt><font size=2>http://www.nomachine.com/kb/</font></tt></a><tt><font size=2>
<br>
> <br>
> ________________________________________________________________<br>
> FreeNX-kNX mailing list --- FreeNX-kNX@kde.org<br>
> </font></tt><a href="https://mail.kde.org/mailman/listinfo/freenx-knx"><tt><font size=2>https://mail.kde.org/mailman/listinfo/freenx-knx</font></tt></a><tt><font size=2><br>
> ________________________________________________________________</font></tt>