Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Originally posted by baldy3105 I played with this for quite a while and I found that you MUST have a password. It appears that Samba's idea of a blank password is not the same as Windows idea of a blank password. Create a new user "printer" with a password of "printer" and use these in the printer config box i.e
this was the only way I could get around the NT Access denied message. You can stop this new user appearing in the log in screen on XP, in the control panel somewhere.
In fact there is an security option in XP that by default disallows logging in remotely without a password.
You can change that by opening mmc, adding group policy then computer settings\windows settings\policy options\security options\Accounts: Allow local use of blank passwords only.
I have no idea how to get my printer to work either. I read this post and it just does not make sense as I don't understand command line that much. I have SuSE Pro 9.0 and I have my printer shared on my Windows XP machine. My windows machines can print fine to the printer. How can my SuSE machine print to the printer on the Windows XP machine? I do see the printing wizard in KDE/Yast but I never see the printer. There has to be an easy way since Windows was ever so simple and works. I would like to change over to SuSE because I have heard it is great, but if I can't even have my machine print to my windows printer, then why bother. Thanks in advance for the step by step help!!!
The easiest way is by using the KDE Printing Manager, you should be able to get it by clicking the KDE Menu -> settings -> Control Panel, then click on peripherals -> printers.
Next you click on the button which says 'administrator mode', fill in your root password and click ok.
Make sure the combo box at your right side is set on 'CUPS (Common UNIX Printing System'), then click on the first icon in the toolbar above. This should bring up a wizard.
From here you should be able to manage to configure the printer. If there are questions, just ask.
I am able to see the shares and printer on my Server 2003 box:
Domain=[LOCAL] OS=[Windows Server 2003 3790] Server=[Windows Server 2003 5.2]
Sharename Type Comment
--------- ---- -------
faxclient Disk Microsoft Shared Fax Clients
clients Disk Windows Small Business Server Client Setup
IPC$ IPC Remote IPC
D$ Disk Default share
print$ Disk Printer Drivers
Resources$ Disk "Event logging files"
NETLOGON Disk Logon server share
HPDeskJe Printer HP DeskJet 880C
Users Disk Users Shared Folders
ClientApps Disk Windows Small Business Server Client Applications
F$ Disk Default share
ADMIN$ Disk Remote Admin
SYSVOL Disk Logon server share
FxsSrvCp$ Disk Common Fax Cover Pages Folder
VPLOGON Disk Symantec AntiVirus
C$ Disk Default share
VPHOME Disk Symantec AntiVirus
Address Disk "Access to address objects"
Domain=[ORLINET] OS=[Windows Server 2003 3790] Server=[Windows Server 2003 5.2]
but receive the following error when I execute this command:
Yipee, I finally got my local Mandrake 10 box printing to my HP Deskjet attached to my Windows XP box.
A painful process that doesn't appear to be overly well documented. Along the way I encountered lot of NT_STATUS_ACCESS_DENIED problems, basically windows telling CUPS to piss off because it didn't have adequate permissions.
Key Changes I made to get my printer working:
a) On Windows XP, enable the Guest User account from control panel
b) On Windows XP, create a share name for the printer as hpdeskjet
c) On KDE Printing Manager (a neat interface for CUPS), firstly set the Configuration Owner to be ROOT
d) On KDE Printing Manager, created new printer with User Identification set to Guest,
e) On KDE Printing Manager, set Domain = MSHOME, server=myXPboxname, printer=hpdeskjet all of which generated a URI of smb://MSHOME/myXPboxname/hpdeskjet
A bit of messing around with password dialogues but I have been able to replicate the process.
Internally, the various elements that print on SMB printers in Linux (CUPS, lprNG) use a command called
which is a part of samba. This is the formal interface from samba to the world of windows printing - that is, this is the package that printer spoolers are supposed to use to get your data to the windows box. This package does nothing about getting the data into the right format for your system. That is handled by other programs. smbspool is just a transport pprogram.
This command takes a printer location in the form of a "URL"
Where the workgroup is optional, as is the userid and password. Details are on the smbspool man page. I have indicated optional parts by enclosinbg them in square braces, and the square braces are not actually entered.
I believe that there is a bug (which Redhat knows about, there is a bug opened in Bugzilla) I posted a workaround for. Seems that he smbspool command has a bug - when your printer is open for all comers to print on, (and maybe when the printer is defined on XP) the smbspool can't connect to it.
But if you specify a userid, any userid, even one that does not exist, smbspool does not have trouble connecting.
Thus, you can specify the userid guest, even if the guest userid is not defined on the windows system or the Linux system, and it will work.
If you defined the printer directly to CUPS, then edit the printer and access the screen whereupon the url was defined.
guest@ to the url right after the double slash so that it looks like:
By using smbspool directly, you can determine if you have solved the access problem at least.
smbspool smb://SYSTEM/queue 1 user title '' 1 /path/to/small/file
smbspool smb://WORKGROUP/SYSTEM/queue 1 user title '' 1 /path/to/small/file
smbspool smb://guest@WORKGROUP/SYSTEM/queue 1 user title '' 1 /path/to/small/file
Where you should substitute your real workgroup name and system name for the ones that are in the example command lines above.
If you defined the printer using redhat-config-printers then edit the printer using that same program and use the "queue type" tab to add a username.
I have a Windows 2000 system which I have locked down - it denies access to the browse list for example, and to print to that system I must specify a real userid, as must I also for accessin a printer on the system. Part of the lockdown was disabling the guest account.
However, XP applies a different semantic to the whole filesharing/device sharing issue. And it is my belief that Samba has not yet been changed to deal with it. For example, to access open shares on XP I have to specify a userid.
There may well be multiple issues at work here, but the access issues should be fixable by specifying a bogus userid, or a real one wirh a password.