Why is Samba needed? Why not just use TCP/IP?

fadeone · 03-02-2006, 09:24 PM

Hello,

This question has been bugging me today.

Why is Samba needed to network between MS and Linux workstations? Why not just configure them both to use TCP/IP, I know I'm missing or not understanding something here I just can't figure it out.

Also,

Is it possible to have a Linux server control MS workstations? For example 1 Linux Server - 60 Windows XP, 40 Windows 2000 Workstations.

Can you configure the users and stuff on the linux server? This question was also 'bothering' me.

Thanks.

Matir · 03-02-2006, 09:51 PM

Samba is a protocol that sits on top of TCP/IP, just like HTTP (web), SMTP (outbound email), or SSH. Samba is the protocol that handles file and print sharing. If you don't want to do any of that, you don't need Samba.

fadeone · 03-02-2006, 09:53 PM

Quote:

Originally Posted by Matir

Samba is a protocol that sits on top of TCP/IP, just like HTTP (web), SMTP (outbound email), or SSH. Samba is the protocol that handles file and print sharing. If you don't want to do any of that, you don't need Samba.

But still, without Samba I won't be able to share files from MS machine to Linux machine, even though they both use TCP/IP, why is this?

Please look at my second question also.

soulestream · 03-02-2006, 09:57 PM

TCP/IP cant transfer files. You need an protocol to handle the process. Think of FTP, HTTP, etc. they all basically do the same job differently. TCP/IP builds the connnection. Think of it as building train tracks across a river. You still need the train to move the cargo.

As for your second part, yes. Windows Active Directory is nothing more than M$ version of LDAP. You can run OpenLDAP, Samba, and a few other apps and do everything and more that a windows server can do.

soule

fadeone · 03-02-2006, 10:15 PM

Quote:

Originally Posted by soulestream

TCP/IP cant transfer files. You need an protocol to handle the process. Think of FTP, HTTP, etc. they all basically do the same job differently. TCP/IP builds the connnection. Think of it as building train tracks across a river. You still need the train to move the cargo.

As for your second part, yes. Windows Active Directory is nothing more than M$ version of LDAP. You can run OpenLDAP, Samba, and a few other apps and do everything and more that a windows server can do.

soule

So why do you need to use Samba?

I always thought MS nativly uses TCP/IP to transfer if that's not it then what is the protocol that does the transfer between 2 MS machines?

What is the the protocol that does the transfer between 2 linux machines?

Thanks for clearing up the second question

utanja · 03-02-2006, 10:59 PM

Quote:

Originally Posted by fadeone

So why do you need to use Samba?

I always thought MS nativly uses TCP/IP to transfer if that's not it then what is the protocol that does the transfer between 2 MS machines?

What is the the protocol that does the transfer between 2 linux machines?

Thanks for clearing up the second question

nfs (network file system) is the system used between linux machines...

blinkey · 03-02-2006, 11:47 PM

Look at this page on the Samba site for a detailed over view.

us2.samba.org/samba/docs/SambaIntro.html

Samba talks SMB and NetBIOS. These are protocls that windows (and others) used before TCP/IP ruled.

cs-cam · 03-03-2006, 12:32 AM

Quote:

So why do you need to use Samba?

The train tracks was a very good analogy, but it's clearly not made it through through.

TCP/IP is not a way of sending files, it's a way to manage a socket. Read this, it'll explain in detail what TCP is. Now read this, it'll explain what SMB is. Should clear some things up for you.