Jump to content

Talk:Samba (software)

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Samba origins dispute[edit]

I edited the Microsoft rewriting of history , Samba is a re-implementation of SMB/CIFS :


As the front page at samba.org says, "Samba is an Open Source/Free Software suite that provides seamless file and print services to SMB/CIFS clients." Samba is freely available, unlike other SMB/CIFS implementations, and allows for interoperability between Linux/Unix servers and Windows-based clients.


Because of the importance of the SMB protocol in interacting with the dominant Microsoft Windows platform, coupled with the heavily modified nature of the SMB implementation present in that platform, the Samba project was created to provide a free implementation of a compatible SMB client and server for use with non-Microsoft operating systems.

It probably needs more language editing and validation of historical facts.

PDC and BDC are both part of active directory. A Samba server can act as a BDC/PDC in a network with and without Microsoft BDC/PDC systems. —The preceding unsigned comment was added by GerardM (talkcontribs) 11:31, 27 January 2004 (UTC)

lkcl: wrong. PDC and BDC are part of NT 3.5 / NT 4.0 Domains. the rest of the sentence is correct.

Samba, at the present time _cannot_ be an Active Directory Domain Controller: only XAD (http://padl.com) which is a proprietary product based on Free Software components, can do that. —The preceding unsigned comment was added by Lkcl (talkcontribs) 21:36, 13 September 2005 (UTC)

clarify, please[edit]

The following sentence is hard to understand for me. Could anyone explain it / write it in a clearer way, please?

<< The list goes on, and is frequently lumped in people's heads as only the one protocol - usually NetBIOS or SMB (which is a bit like blaming DHCP for the problem of Email "Spam" because when a DHCP server gives you an IP address you get lots of unsolicited email). >> —The preceding unsigned comment was added by (talk 14:06, 12 September 2005 (UTC)

lkcl: okay. basically, people go "i want a windows file server" and they get an implementation of the following protocols: TCP/IP, NETBEUI, NetBIOS, SMB, LANMAN, Network Neighbourhood, MSRPC, and the following services _on_ those protocols: an SMB server, a WINS server, a set of services comprising the Network Neighbourhood, a NETLOGON server, a SPOOLSS server, a SAM database server, an LSA server - the list goes on and frigging on.

now imagine the confusion that would result if a manager talked to an experienced unix sysadmin saying "i want you to switch off our dhcp server NOW because if you give out TCP/IP addresses, everyone gets "SPAM" email".

the parallel is this: when sysadmins think "bloody windows" they think "ports 135, 137, 138, 139 and 445".

but they haven't got a CLUE what's on those ports. —The preceding unsigned comment was added by Lkcl (talkcontribs) 21:36, 13 September 2005 (UTC)

Samba and FAT[edit]

For people who reads zdnet or other media, the story about the relation between samba and FAT is completely false. Samba does not use FAT Filesystem. —The preceding unsigned comment was added by (talk 22:28, 26 October 2005 (UTC)

Article name[edit]

Shouldn't it be "Samba (software)" instead of "Samba software"? The article is about software called "Samba". 12:21, 17 January 2006 (UTC)[reply]

On Portal:Free software, Samba is currently the selected article[edit]

Just to let you know. The purpose of selecting an article is both to point readers to the article and to highlight it to potential contributors. It will remain on the portal for a week or so. The previous selected article was FreeBSD. Gronky 22:25, 1 June 2006 (UTC)[reply]

Article name[edit]

Wouldnt the correct name of the article be 'Samba (software)' instead of 'Samba software' ? -- Frap 12:13, 7 June 2006 (UTC)[reply]


Are the screenshots really appropriate here? None of them are screenshots of Samba itself. Wouldn't these screenshots be more appropriate on the pages of the applications they show?

 --ctrlsoft 18:00, 19 February 2007 (UTC)[reply]
More to the point, exactly what are those screenshots showing? It's not explained. I'm removing them now, for the record, they were these:
--SKopp 19:36, 19 February 2007 (UTC)[reply]

remove samba "how-to" link?[edit]

the samba "how-to" linked on the bottom of the page contains a lot of incorrect information. For example, the explanation of the parameters "bind interfaces only" and "domain master" is just plain wrong. It also advices to set various parameters that are intended for performance tuning and should never be touched by novice uses.

I'm upstream for Samba so I don't feel comfortable removing the link.

--ctrlsoft 19:59, 2 December 2007 (UTC)[reply]


smbclient send message to windows operating system from linux use following command : - 1) smbclient -M hostname

2) echo hi|smbclient -M hostname

if we want to send a file content through smbclient

3) cat filename| smbclient -M hostname

from Vishal Jain Sr. S/W Eng. http://ubitechsolutions.com [[1]] [vjcyber@gmail.com] —Preceding unsigned comment added by (talk) 07:23, 25 January 2008 (UTC)[reply]

Microsoft documentation[edit]

How come this article makes no mention of the Microsoft documentation the Samba engineers received? http://samba.org/samba/PFIF/ Altonbr (talk) 15:04, 4 August 2008 (UTC)[reply]

cross-OS file name issues[edit]

This article seems much too short. It seems that Samba inter-connects Linux to Windows file systems. But the rules for naming files in those two worlds are quite different (Windows FAT files have both a long name and a legacy 8.3 name, case is sort of not significant in Windows file names etc.) Such issues should be mentioned, with reference to sources of complete details. - (talk) 03:28, 6 January 2009 (UTC)[reply]

Its modifiable. In SMB.conf you can modify it e.g. there are options such as "short preserve case" "mangle case" etc.... which you can tweak to best suit your needs (as e.g. those great for DOS arent the best for recent versions of windows) (talk) 05:44, 20 January 2010 (UTC)[reply]

The issue is not only a case issue, but a character encoding issue. The fact that some configuration keys might exist does not change the need for such issues should be mentioned in the article.
Other related interoperability issues include: supported character set (always unicode?), forbidden characters, out of the band bytes sequences (illformed/not valid in utf-8), NFC/NFD normalisation and unicode equivalence, linux character agnosticism. — Preceding unsigned comment added by (talk) 21:40, 5 November 2012 (UTC)[reply]

Random, ironic, useless, and completely un{relat,need}ed trivia[edit]

At the mention of how the Samba name was introduced I checked that I had /usr/share/dict/words on my Arch Linux ([2]) system, and upon discovering that I did, tried the grep command noted, and was met with a rather odd result: my system didn't have "Samba" or "samba" in the list. Doubting the regex, I changed the lowercase 's' to an 'S', which produced the same result. My system is quite recent (well, I do need to update (a bit) - Arch uses a rolling release system), which only makes this all the more amusing. I don't know if this should go into the actual article, and I'd have no idea how to insert it if it was considered a good idea.

-- dav7 (talk) 09:14, 28 January 2009 (UTC)[reply]

Samba 4 - Active Directory[edit]

Should we have something in here about the new developments in Samba 4, and what they have so far managed to achieve in relation to implmenting Active Directory?
I know going into a howto here would be a bit much... But I think some of the information is maybe a bit outdated as to what they are now heading towards?

Thanks guys...
Iamacarpetlicker (talk) 10:14, 24 March 2009 (UTC)[reply]

Redirected smbclient to this page[edit]

Since the article on smbclient contained no information that couldn't be found in either this article or the Samba manual, I redirected it here. Regeseane (talk) 02:37, 18 March 2012 (UTC)[reply]