Samba Woes

[Gazoo]

Heyaz,

Linuxnewbie cadet first line of idiocy-squad reporting... Well ok - maybe I'm not a complete idiot, but I am a complete newbie when it comes to Linux, seeing as I've only been toying around with it for about 2 weeks now, and I've been having some troubles getting Samba to work. :confused:

My tale goes as follows. At first I tried using the NHF on this site concerning samba to get it up and running on my Red Hat 7.1 installation. Going through the first few steps and realizing I failed miserably as SWAT wouldn't respond when trying to connect to the Linux computer I decided to go straight to the Red Hat 7.1 Docu. I managed to get the Server to show itself in the network but accessing it always fails.

So I'm asking if someone could either direct me to a "HOW TO" which they found extremely useful, or if someone could hint me in the direction where the mound of errors could lie?

Already greateful,

Gazoo...

[jaygee432]

Win 9x/me? This did it for me: http://www.linuxjunior.org/cgi-bin/pet/pet.cgi?SUBMIT=Display&id=6

[ferg]

Gazoo, where exactly are you failing. Did you set up the shares?

[Gazoo]

Thanks for the link, but I'm running Windows 2000 aswell as also win98 on the network... The problem is I don't know where things are failing but even the slightest thing doesn't seem to work. I can't even connect to SWAT even after I looked that the right entries were in the conf file and also entered some stuff into the xinetd.conf... :(

This is very depressing...

Gazoo...

[ferg]

Are you seeing the Samba server in your Win2K and Win98 Network Neighbourhood?

If you are, the samba is working but your samba shares are probably not correctly defined.

Let me know

[Gazoo]

Hey,

Unfortunately not, at first I thought it was but later I found out that was our 5th computer with the same name :P. I'm running it on RedHat Linux 7.1 and the SMB service isn't started on boot. Even though I start it manually from the console nothing shows up in the network :(

Gazoo

[ferg]

OK. Let's back up and go step by step.
Can you ping the Linux computer on your network?

Even if Samba does not start at boot up, that's ok. test your smb.conf file by running testparm.

If that's ok. run samba start, if not go back and edit yor smb.conf file and repeat until ok.

Also make sure your shares are setup ok.

[Gazoo]

Well - At the moment it looks like this. Everything seems to be set up right (A friend came over who uses Suse and did all he had done at home) - We even added SWAT and SAMBA to start in the boot sequence and both are started... Yet whenever I try accessing the computer over port 901 then nothing happens... The only thing that SAMBA seems to be doing is to show itself in the Windows Network. When trying to access the computer however it returns an error... Can someone tell me what could possibly be wrong?

Ah we just noticed - SWAT can be accessed from the localhost (the computer itself), but not from the outside... What could be causing this?

Gazoo...

[Bokkenka]

Hey, Great Gazoo...

Let us see your /etc/smb.conf so we can help you better.

Check Newbie Samba Question (http://www.linuxnewbie.org/cgi-bin/ubbcgi/ultimatebb.cgi?ubb=get_topic&f=13&t=005357) to see a basic Samba primer.

Editted to fix the link.

[ 09 October 2001: Message edited by: Bokkenka ]

[Gazoo]

Hey,

We got much further in the issue now that SWAT works on the local machine - we got sharing up aswell as functioning printer-services - however we are still clue-less as to why SWAT doesn't respond on the 901 port to others...

Heres my smb.conf:

# Samba config file created using SWAT
# from Server101 (127.0.0.1)
# Date: 2001/10/09 23:17:31

# Global parameters
[global]
workgroup = LAN
server string = Web/Print Server
security = SHARE
encrypt passwords = Yes
null passwords = Yes
ssl CA certFile = /usr/share/ssl/certs/ca-bundle.crt
log file = /var/log/samba/%m.log
max log size = 0
announce version = 1.337
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
domain admin group = smb
domain guest group = smb
domain admin users = smbuser
domain guest users = smbuser
preferred master = Yes
dns proxy = No
wins support = Yes
guest account = smbuser
valid users = smbuser
admin users = smbuser
create mask = 0644
hosts allow = 192.168.0. 127.0.0.1
printing = lprng
hide dot files = No
map hidden = Yes

[homes]
comment = Home Directories
writeable = Yes
browseable = No

[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No

[test]
path = /
writeable = Yes
guest ok = Yes

[laserjet4l]
path = /var/spool/samba
writeable = Yes
guest ok = Yes
printable = Yes
printer = laserjet4l
oplocks = No
share modes = No

:)

Gazoo...

[zenfir]

Check to see if ipchains or iptables is running in services. If so, stop them and see if you can access from outside local machine. If you can, then you have a firewall problem. This gave me fits for a little bit.

[michaelk]

Since swat is a web browser administrator tool for configuring the smb.conf. I would think for security reasons you wouldn't want to be able to use it on other then the local machine.

I prefer editing the smb.conf file by hand and don't use swat but check to see if you have a xinetd config for swat and comment out the only_from line. it might work assuming no other firewall issues etc.

## /etc/xinetd.d/swat
service swat
{
port = 901
socket_type = stream
wait = no
only_from = localhost
user = root
server = /usr/local/samba/bin/swat
log_on_failure += USERID
disable = No
}