Displaying 4 results from an estimated 4 matches for "point&print".
2004 Oct 06
3
Point&print problem: printer names show the ip, not the server name.
...(3.0.7-2.FC1). Everything was working before
the upgrade, but i immediately started noticing some peculiarities after restoring the samba
files (/etc/samba, /var/cache/samba) and starting samba. The problem manifests by the
following:
- when i double click on a workstation printer created using point&print, the header of the
window shows the ip number of the server instead of the server name. The printer
description on the local printers&faxes folder is right, though: ex: "laser on jimmy".
- creating a new printer using point&print, the new printer gets a description as...
2004 Oct 20
0
Point&Print adding NT/2K drivers issue
Hi all,
Samba 3.0.7 and using CUPS printing. I am logged in as root to an XP Pro
system, I have used the APW to install the XP drivers to all of my printers.
I went to Shared and clicked "Additional Drivers" and checkmarked both 9x and
NT/2K boxes. Using drivers straight from the HP website, the 9x driver
installs fine, but it seems like I can't get any NT/2K drivers to
2010 Feb 05
1
using RPCS printer driver for a P&P printer
...any error/denied or similar messages (or simply smth that
would stand out of the usual) in the log files (loglevel 3). I can
install the drivers on the
WS by hand and use samba just for the printer queue fine (per-machine
printer). But since i will have to install more printers i wanted to use
the point&print method since it saves a lot of hassle.
The printer is a NRG DSc424 and im using Windows XP. The same thing
works fine with the official PCL6 drivers and i might have to settle for
that in the end but the RPCS drivers give a better quality.
It's not a permission problem either, using...
2010 Feb 05
0
samba Digest, Vol 86, Issue 6
...ny attempt
> to read this file will fail with an "access denied" error.
>
> The problem occurs as Samba allows clients using the UNIX
> extensions (which are also turned on by default) to create
> symlinks on remotely mounted shares on which they have write
> access that point to any path on the file system.
>
> This is by design, as applications running on UNIX clients
> may have good reasons to create symlinks anywhere on the
> filesystem they have write access that point to local files
> (such as /etc/passwd).
>
> UNIX clients will resolve these l...