[Samba] Printer not accessible! Plea

Robert Adkins raa at impelind.com
Wed Jan 15 15:07:00 GMT 2003


	Having the Domain name in the workgroup would do the trick. I did that   
because the end-user typically works on a Windows 2000 Workstation, with   
some different software then is installed on the laptop. The roaming   
profiles I have configured end up wreaking havoc between the laptop and   
the workstation.

	Since I didn't have the time to dig deeper and didn't wish to create two   
logons for that user, having the laptop working as if connected to a   
workgroup was and currently is the best option.

Robert Adkins II
IT Manager/Buyer
Impel Industries, Inc.
Ph. 586-254-5800
Fx. 586-254-5804

 -----Original Message-----
From: Martin Peter Hanke [mailto:mphanke at web.de]
Sent: Wednesday, January 15, 2003 3:53 PM
To: Robert Adkins
Subject: Re: [Samba] Printer not accessible! Plea



thanks just ordered the O'Reilly book, guess it will be helpfull, by the
way you are joining the laptop to the domain with the name of the domain
in the workgroup setting? Is this right? I have the problem we will have
up to 8 notebooks which will not be joined to the domain but have to
access the data on the server.

Is this the way to go?

Robert Adkins wrote:

>	There is a great deal more that needs to be done other then the   
>of a smb.conf file for setting up a PDC for any Windows workstations.
>	Unfortunately, I only have experience with setting up a PDC for a mixed   

>bag of Windows 9x, Windows NT 4.0 and Win2K systems. The only WinXP
>machine we utilize is one laptop, which is rarely ever attached to the   

>corporate network. So, that machine is just setup for to see our domain   

>as a workgroup.
>	I do know that some of the things that you need for a Samba PDC include   

>setting up machine accounts in both your normal UNIX environment and   
>in the smbpasswd file. You also need a netlogon directory and a profiles   

>directory, if you are using roaming profiles.
>	Unfortunately, I don't have enough time available to go over all the
>configurations with you, since I am a one-man IT Department with many
>projects currently in the works... What I can do is send you some links   

>and provide some guidance towards some information that helped me
>	One thing I recommend is to pick up a copy of the O'Reilly book, "Using   

>Samba". While it is slightly dated these days, the book was immeasurably   

>helpful as it explained quite a bit about how SMB (In Windows) works and   

>gave some great background information for configuring a Samba PDC.
>	Another wonderful resource is the built-in Swat HTML help files. If you   

>haven't taken a look at Swat yet, definitely do so. It should have been   

>part of your installation process for the version of Samba that you are   

>using. One thing to consider before using Swat, is that Swat will   
>your configuration file. This is important, because Samba rereads that   

>file about every 20 to 30 seconds. This rewrite streamlines the file and   

>allows Samba to turn up the speed considerably, especially if you have   

>many shares. What it does is remove ALL of the comments and in-file
>	Another tool that I used to configure my Samba install is webmin. It   
>be found at www.webmin.com. This tool is awesome for remotely
>administrating a UNIX Server, if you want to use a GUI tool. (Sometimes   
>really enjoy using such a tool, even though I am comfortable with CLI
>configurations.) Webmin will display everything at once in an easy to
>read format. The only thing it currently doesn't support configuring is   
>Samba PDC.
>	Here are a few links to some helpful Samba PDC setups:
>	http://www.linuxnetmag.com/en/issue6/m6samba1.html
>	http://www.siliconvalleyccie.com/index.htm - There is a link titled
>"Samba File/Print Sharing" which should prove helpful as it has a   
>dedicated to Samba PDC.
>	The final thing that I can recommend is to use the latest release of
>Samba. I have read of a number of issues with older releases of Samba
>with Windows XP and Windows 2000 with Service Pack 3 (but not SP1 or SP2   

>of Windows 2000.) I didn't have the time to really dig into those issues   

>and I wouldn't be able to reproduce them here since I haven|t quite the   

>same configurations of OSs. So, I can only imagine that MS made some
>"minor" changes to the way those client Operating Systems talk via the   

>SMB protocol.
>	I hope that has been helpful. Good luck with yor network!
>Robert Adkins II
>IT Manager/Buyer
>Impel Industries, Inc.
>Ph. 586-254-5800
>Fx. 586-254-5804
> -----Original Message-----
>From: Martin Peter Hanke [mailto:mphanke at web.de]
>Sent: Wednesday, January 15, 2003 12:48 PM
>To: samba at lists.samba.org; Robert Adkins
>Subject: [Samba] Printer not accessible! Please review my conf on leaks
>I'm having problems with my printer, I can't access the printer not even
>as root! Please review my smb.conf and give me some hints on what I
>messed up. If you have some enhancements for me please add comments.
>Thanks for your efforts,
> --
>I. Thessalonians 4:16
>        Thanks, Dad, for just letting me be a nerd.
>We don't stop playing because we grow older,
>We grow older because we stop playing.
>Being paranoid does not mean they are not out to get you.
>Important Information:
>This is best viewed with Netscape Explorer 21.5,
>at 3200x1800 pixels with 8xFSAA, 48bit color,
>27" TFT (16x9), and a nail in the knee.

I. Thessalonians 4:16
        Thanks, Dad, for just letting me be a nerd.

We don't stop playing because we grow older,
We grow older because we stop playing.

Being paranoid does not mean they are not out to get you.

Important Information:
This is best viewed with Netscape Explorer 21.5,
at 3200x1800 pixels with 8xFSAA, 48bit color,
27" TFT (16x9), and a nail in the knee.

More information about the samba mailing list