Add Comment

You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.

To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.

This is the comment you were replying to, attached to the article Debian, CUPS, Samba... Days of grief:


Re: Debian, CUPS, Samba... Days of grief
Posted by Eirik (129.177.xx.xx) on Tue 29 Nov 2005 at 15:12
Part of the problem is that nowhere have I found a source that gives me a simple overview, a clear step-by-step procedure, and diagnostics to zero in on the problems. Every source seems to say something different.

I'm not surprised -- while setting this up in a hetrogenous environement can seem simple, the truth of the matter is rather complex, and can still be daunting, even when you've done it several times before

Here's what I'm trying to do:

You have one windows computer (Windows A)running ms 2000 server. Is it set up as an active domain controller ? Normally this is how you would set it up -- either explicitly or by installing Microsoft Small Buisiness Server. I'll assume you're using workgroup security, then I'll revisit domain security later.

You have two Debian/Sarge systems (LinuxA and LinuxB) and want to share a HP PhotoSmart P1100 printer, connected to LinuxA.

You currently want the user Lloyd to have access to the printer from all 3 computers, and to have access to fileshares on all 3 machines.

In order for this to work, you need to:

  • Set up the printer on LinuxA, and verify that local printing is working. Remember that CUPS comes with a web-configuration, accessible locally as http://localhost:631.
  • Allow access to the printer to other computers -- the easiest would be to use the ipp-protocol -- this can be done using cups only, and is not dependant on Samba. Share the printer via ipp in CUPS, and connect to it via CUPS/ipp from LinuxB and ipp from WindowsA. Have a look at http://www.owlfish.com/thoughts/winipp-cups-2003-07-20.html.
  • Allow access to some folder on LinuxA via Samba. Use security=user, and follow samba docs. Verify that you can access the files from the Windowscomputer
  • Setup will be identical on LinuxB
  • Allow access to a fileshare on the Windows 2000 server. How to do this is dependent on your setup -- if you've previously used workgroup security this should be straight forward. In order to access these files from Linux you need to mount them with eg:mkdir /mnt/win
    mount //windowsA/share -tsmbfs -oUsername=Lloyd,Workgroup=MyWorkGroup,rw /mnt/win

If you have set up your windows server as a Active Domain master, you'll be better off joining the Linux-computers to the domain, and using the Windows-machine to authenticate against. This has it's own complexities, but basically you need to install samba on both machines, and then issue the command net ads join as root. It's a little more to it than that -- see documentation the at www.samba.org.

Note that Samba isn't designed to be used for ad-hoc filesharing. Usually you'll want to have one server with user files, that can be backed up easily.

Hope this gets you a little further.


Username:Anonymous
Title:
Your Comment:

Posting Format:

 

Inappropriate comments will be removed.

Some help on entry formatting is available

User Login

Username:

Password:

[ Advanced Login ]

Register Account

Quick Site Search