Problem with SWAT (SAMBA)

Hmm right you have a lot of stuff there which I don't think you need, some of it I don't know exactly what it does. One thing that does strike me is that you have path = /home/public in your globals section, and I don't think it should go there. Does you config file pass "testparm"?

In your [Test] you may want either "writable = yes" or "read only = no".

Another thing is do your windows clients have unix profiles? If your using "security = USER" the client must have A) a samba profile (use add user on the last tab in swat) and B) They must have a unix profile i.e that they must have a home directory. If the windows client login name is different to the unix profile name you must create a username mapping file.

Finally if you make any changes you have to save and restart smbd for the changes to occur. I found that sometime you may also have to logout and login on the windows machine, I think it's something to do with windows caching files.
 
Last edited:
Yeah I think you might have a point there shak. The more I think about the more I think [home] is a "magic" definition that refers to someones "home dir" ... Haven't tried it but I reckon If you call it something else you won't be able to log into a home dir.

TBH nut_case I think your smb.conf is foobared. You seem to a mishmash of allsorts of stuff in there. Tell us what you want to be able to do. Do you want windows clients to have a unix share, so that when that specific client logs in they will and only them have access to their share? Or do you want a generic share? ... or even both if you like. But a Public share will require you to specify a path to the directory on the linux machine you want to share.
 
I agree, tell us whats needed and we'll hack one together.

Mpemba: AFAICS if you dont have either [public] or [homes] then there is nothing to share, and in the above config there is never a path defined to the share!

Shak
 
lol, ok, been to the pub for a while so maybe not so coherent :)

All I want is a totally generic share. I just weant a whole ton (as in about a terrabyte eventually) of files to be available over my LAN. I've had this thing working before, and I'm pretty sure that it's anetowrk problem, rather than a share problem. I checked the DHCP table on my router earlier, and the server ain't showing up :( It is however showing up in the workgroup on the computers on the LAN. TBH me and networking = uh oh :) I used to be fairly ok when BBC's whre teh game, but PC's and networking = noob. But because I can get to the share locally (i.e. on the linux machine) I think it;s a network problem. Maybe cos I have dynamically (DHCP) allocated IP's or something the host file is knackered. I dunno :( None of the help files with samba or on samba.org have covered my problem, some are close, but I don't get teh same symptoms.

As I say above, I've had it working before, which is teh most annoying part!!!
 
here is a very simple smb.conf file for u, has one share folder called shared and a user called guest ppl can use to brows the server with out the need of an account on it.

[global]
workgroup = netowrk name here
netbios name = server name here
os level = 32
server string = Samba %V
guest account = smbguest
security = user
socket options = TCP_NODELAY IPTOS_LOWDELAY
encrypt passwords = yes


[shared]
comment = shared space; for everyone
path = path_to_share_folder
force group = public
read only = no
force create mode =0440
force directory mode = 0775
guest ok = yes



thats it
this wil give u a simple samba share i might haave missed somethink out consideriting its 1:00am.

Kudos
 
I don't think you'll need "guest account = smbguest" it defaults to "nobody" which is actually a unix profile. If you want smbguest as the guest you'll need to create a unix profile for it, but you'll create one without a home. Which is simple enough. Apart from that Kudos share should work fine. Remember the specify a path and make sure that directory has permissions for rwx of everybody. Do this by chmod 777 dir.
 
If you are using the SMB box as you PDC and your XP box won't see the workgroups you need to:
1) log into the XP box
2) fire up regedt32
3) go hkey_local_machine/software/microsoft/mslanmanager (I think)
4) find the requiresignorseal key = it will have a value of 1
5) set that to 0
6) reboot the XP box.
7) Bob's your uncle.

HTH

Phil
 
Right, I'm beginning to get somewhere! The Win98 laptop got an enter password box earlier with IP$ or something as the username. Now I saw that mentioned in one of the samba problems files I've nosed at over the last couple of days. Will look at that tommorow. However...

I'm logged into the share with my XP machine :D


Here's the smb.conf:

Code: 
# Samba config file created using SWAT
# from 0.0.0.0 (0.0.0.0)
# Date: 2002/10/25 22:12:35

# Global parameters
[global]
	netbios name = SERVER
	server string = Samba %V
	encrypt passwords = Yes
	socket options = TCP_NODELAY IPTOS_LOWDELAY
	os level = 33
	preferred master = True
	default service = shared
	remote announce = 192.168.0.1
	guest account = smbguest

[shared]
	comment = shared space; for everyone
	path = /home/public
	force group = public
	read only = No
	force create mode = 0440
	force directory mode = 0775
	guest ok = Yes

The remote announce line is ther cos I'm still trying to get the thing to show in the DHCP table on my router. No joy tho (but I'm not that bothered!). Just tried it and I have read and write permissions. I do believe I'm getting there.

Cheers for your help guys. I'm now back to where I was about 6 weeks ago when I last had a play. Hmm. Noobs :D

I still think it had a lot to do with either: NetBIOS configuration on the XP machine (which I've been tinkereing with a fair bit, and I can now view the comps in WORKGROUP nice and quick :)); Master browsing configuration on the samba machine; me being a muppet.
 
You must log in or register to reply here.
Back
Top Bottom