Samba only way to connect Linux server to other workstations?

[Jugernot]

I'm very new this linux thing and got a server setup with Redhat 7.3. I've been looking over file sharing and it looks like Samba is only way to link Linux with Windows machines? Isn't there a way to make Linux appear as a workstation rather than making it a quasi NT domain controller?

I guess I'm asking if there is a easier way to let my windows machines connect with the linux server without making it a domain controller?

Thanks guys!

Jugs

btw: Can anyone tell me how to activate the ftp server that redhat installed by default? As it is right now, I can't access the server through ftp.

I have been using WinSCP to do files transfers, but would much rather use ftp.

 

[Nothinman]

Samba is a SMB client/server for unix, it doesn't mean it's a domain controller although that's one of it's possible functions.

 

[Jugernot]

Ok, all of the install docs I've found only tell you how to make it a domain controller. Anyone know a good install page for it?

 

[Workin']

Samba Documentation

Some more stuff

 

[manly]

A bit dated, but good book from ORA:

Using Samba.

 

[Jugernot]

Heh, what a coincedence, I was just reading over the linuxnewbie article. I'm able to view the workgroup that I set for Samba, but no clients are showing inside. Just the workgroup, which isn't writeable alone.

 

[FUBAR]

For the ftp server, go to /etc/xinet.d/ and edit the file that has ftp in the name (can't remember which it is since I never use RH's server) Look for the line in that file that says disable = yes and either delete or change it to no. then do a /etc/init.d/xinetd reload or you can HUP the process, I think it's kill -1 or kill -HUP. That should do it.

 

[n0cmonkey]

If you have to use FTP make sure you use the latest version of the ftpd. If I remember correctly, RH uses wu-ftp...

I think there may be something on SAMBA in the Linux FAQ thread in the OS forum.

 

[Mucman]

heck ya! Making Samba a domain controller is tough!

How is your smb.conf like?

Here's what I setup to test connectivity etc...

[globals]
workgroup = MUC
server string = Samba Server
hosts allow = 192.168.1.
guest account = nobody
log file = /var/log/log.%m
max log size = 500
security = share
socket options = TCP_NODELAY
local master = yes
[temp]
browseable = yes
writeable = yes
path = /usr/local/export/samba/temp
public = yes

and give ownership to that dir to nobody and you can read and write to that share to your hearts content! It's not secure or anything, but
if you want to get started, this will allow a win98 machine to connect...

 

[Jugernot]

Ok, well I'm much closer now! I have a share that is showing under Windows and I'm able to login from 3 out the 4 windows machines accept my main workstation. I get a "Duplicate name exists" error, so I change the computer name to no avail. What's going on? Since this works from the other machines, what makes my machine different?

Here is my smb.conf:

[globals]
workgroup = Linux
server string = Samba Server
hosts allow = 192.168.2.
guest account = nobody
log file = /var/log/log.%m
max log size = 500
security = share
socket options = TCP_NODELAY
local master = yes
encrypt passwords = no
smb passwd file = /etc/samba/smbpasswd
interfaces = 192.168.2.101 127.0.0.1

[homes]
comment = Home Directories
browseable = no
writable = yes

[file-store]
comment = Comment
path = /pub
read only = no
public = yes

Thanks guys, you've been a whole lot of help and I do appreciate you taking the time to help a n00b out!

EDIT: Here is a little bit more info:

[root@localhost samba]# smbclient //joe/documents -U joe1
added interface ip=192.168.2.101 bcast=192.168.2.255 nmask=255.255.255.0
added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
session request to JOE failed (Called name not present)
Password:
Domain=[WORKGROUP] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
tree connect failed: NT_STATUS_DUPLICATE_NAME

 

[L3Guy]

Just a side note. At one point, there was a PC NFS client. That way, you ran NFS on the server, and the PC's could attach natively.
I ran it at ACN while I was there, and later ran it on a LAW net in downtown Chicago.
IMHO, Samba is rather ?bss ackwards?. However, if it works...

Doug

 

[Jugernot]

NFS? Forgive me, but what does this abbreviation stand for?

I did a search on google.com, but couldn't turn up anything to do with netowrking linux with Windows. Perhaps you can be a little more specific?

Thanks

 

[Nothinman]

NFS stands for Network File System, and is normally Unix to Unix but there are NFS clients for Windows. It's actually a worse protocol and less secure than SMB.

 

[spidey07]

I thought that was what FTP is for.

 

[L3Guy]

I thought that was what FTP is for

LOL! Its the difference between "net use" and "net copy". In other words NFS allows a unix machine to mount another unix machine volume over the net.

It's actually a worse protocol and less secure than SMB.

NFS does have issues. The two biggest are its use of UDP as a transport and its use of RPC (remote procedure calls) to impliment it.
Udp has the potential to corrupt files, and access to RPC on a machine opens the door to some interesting security quandras.
However, NFS is simple, fast, and has been around a long time. I tend to want the server run in native mode, and let the clients adapt, unless there is a reason to do otherwise. Just my personal prefrence.

JMHO

Doug