[NBLUG/talk] Samba solutions

[Chris White]

For what it's worth:

I haven't been following this thread all that closely, but I just wanted to say that I've been using Samba at work and at home, in heterogeneous environments (Linux/Windows/Mac OS X), without any problems.  My smbusers file is set for unixname = winname, just like the doc, and it works fine.  No Samba server is the Domain Controller, however.  That is reserved for a corporate box running Win2K.  My Samba config file defines the password server as my Win2K Domain Controller (real names/IP addresses replaced with {phoney} ones):


security = server
password server = {my_server_name}

No Domain Controller is specified.  My Samba servers are also set up with these settings:

local master = no
os level = 0
domain master = no
preferred master = no
wins support = no
wins server = {insert IP address of Domain Controller, same as my_server_name, above}

Mappings between Windows names and Linux names (which are different) just works.  The doc hasn't been wrong as far as I can tell -- but I haven't used any 9.x clients in years.

BTW, I'm running Red Hat 9.0, samba-client-2.2.7a-8.9.0, samba-2.2.7a-8.9.0, samba-common-2.2.7a-8.9.0.

Regards,

--Chris


> -----Original Message-----
> From: Warren Raquel [mailto:wraquel at jacobmarlie.com]
> Sent: Tuesday, November 18, 2003 2:15 PM
> To: talk at nblug.org
> Subject: Re: [NBLUG/talk] Samba solutions
> 
> 
> That's odd. I have users who have different Unix logins than windows 
> logins and I only use mapping in those situations. Otherwise there 
> shouldn't be a need for it.
> 
> Bob Blick wrote:
> 
> >Fixed. Two problems:
> >
> >1) Username mapping is not unixuser = winuser. It is 
> unixuser = winmachine.
> >
> >I had to change the entry in smbusers to read:
> >bob = ASTG300 instead of bob = bob
> >
> >Documentation contradicts this! I seem to recall being 
> bitten by this one
> >before.
> >
> >At this point I could use shares if I knew they existed and 
> called them by
> >IP address. Still no listing in Explorer or LinNeighborhood though.
> >
> >2) Netmask was 255.255.0.0 on the new linux machine, instead of
> >255.255.255.0 like the rest of the network.
> >
> >This is the first time I've ever had a problem with netmasks breaking
> >something in this way.
> >
> >Fixing that made shares show in Explorer and machine names work.
> >
> >Cheerful regards,
> >
> >Bob
> >
> >
> >
> >
> >_______________________________________________
> >talk mailing list
> >talk at nblug.org
> >http://nblug.org/mailman/listinfo/talk
> >  
> >
> 
> 
> _______________________________________________
> talk mailing list
> talk at nblug.org
> http://nblug.org/mailman/listinfo/talk
>