Joining a Windows 2003 Domain with an Ubuntu Workstation: How?
UbuntuThis forum is for the discussion of Ubuntu Linux.
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.
The link's fine, just click it. The Samba stuff is crucial - it's a metapackage you'll find easily using Synaptic.
This link will be useful when I am ready to join with my workgroup here at home. At work, I am technology coordinator at a high school, where I also teach math and computing topics, all under Windows XP. So if I am successful with my Ubuntu effort, I am positioned to share the joys of Linux with others. Joining the Ubuntu workstations to the Windows 2003 domain will be an important. So, not wanting to be a pest newbie, I'm trying to get a handle on the meta-concepts before I get buried in the minutae.
Humor me, please, with one basic Samba question: Does Samba run on the Linux workstation to allow it to play with Windows, or on the server so it can accept a Linux workstation, or both?
I'm sorry if I seemed a bit curt - but it appeared to me that the basics were well covered (if a bit scattered) in the threads I pointed to; maybe they weren't. I certainly didn't mean to offend you - it's just very common that people who ask such questions didn't search for information first, and that's pretty offending in itself. My first question may have been a bit direct, but I wanted to cover for that first (I don't like information vampires much, something you, regarding your profession, will certainly agree with).
The meta-concept, with a bit of background (I'm not the most suited to write about this, but so be it): The GNU/Linux and the Win world aren't meant to share a lot of things, something for which, considering the circumstances, not the GNU/Linux people are mainly responsible. They need to re-engineer technologies that provide them and their users with sufficient compatibility with the Win world time and again, and MS doesn't do anything noticeable to help those efforts. Win file sharing with non-Win boxes is something that, though it's essential, isn't sought after by MS. Luckily, and this is one of the few "positive" effects of this abominable monopoly, no-one can do without it, so the efforts to provide the functionality are numerous and - out of utter need - pretty effective. Samba (and the usage of MS file systems in general, through matching drivers) is (or are, respectively) a fruit of those efforts.
Samba provides your Ubuntu workstation with the protocols needed to join in on Win file sharing - through the server, you can create Win-aware shares on the Ubuntu box, with the client, you can use existing shares on other boxes/servers. That's why you should install the whole meta-package (providing you with both parts of the whole affair). After that, using the recipe the link points to, you should be able to join the Win workgroup as described. If it doesn't work, something's amiss, and someone here'll hopefully be able to help you further.
No apologies necessary. I appreciate your -- and others' -- assistance.
So, here's my project list, in approximate order:
+ Install Ubuntu 8.10 on a dedicated box here at home.
+ Join that box with my Windows workgroup here at home.
+ Image a similar box at school and join it to the Windows domain there.
+ Work on a *buntu image that will bring a few obsolescent boxes at school back to life and place them in classrooms and/or give them away to students (we have a challenged socioeconomic demographic).
+ Construct a Linux file server to contain all of the files related to the yearbook class that I teach. This is currently about a 20 gb block of files.
If I had a real job, I wouldn't have time to think up crazy schemes like this one.
The questions I've been asking on LQ are aimed at helping me know where to study, so I'm not taking blind shots in the dark. I've got a 5th Edition copy of Linux in a Nutshell on the way (I've had good luck with O'Reilly titles) and it looks like a similar book on Samba will be a worthwhile read as well.
That's a great plan! I wish I was allowed to do something similar in our school, but sadly, our whole infrastructure is in the hands of MS slaves (read: MS certified admins and coordinators); I am explicitly *forbidden* to even attempt to join the network with anything that's not the official Win image. Nice, is it not?
I hope you'll succeed. Having forgone MS for years, I'm not an expert on interoperability. I'll try to help as far as I can.