Forum Home
Press F1
 
Thread ID: 66758 2006-03-06 16:10:00 Samba Problems hamstar (4) Press F1
Post ID Timestamp Content User
436015 2006-03-06 16:10:00 Hey linux guys...

I'm trying to connect my opensuse 10 box to my win2k box.

I got it sort of working, and then screwed it.

I found and clicked my opensuse box (shavo) in WORKGROUP in My Network Places. It popped up the box to type in teh password etc. I tried to type the account I had added to the smbpasswd command, but it wouldn't work. So I typed root, and hit enter by accident and it got in! I thort that was weird.

From here it showed me folders but not files. So I went to have a tweak and added directory mask = 0775 to each share. Then stuff started going wrong. I couldn't access it anymore in windows.

When i tried to connect using smbclient to either localhost or serj (win2k box) it said NT_STATUS_ACCESS_FAILED or something along those lines. So I thort since it was a modifed version of the suse conf file that was there I should delete the printer lines.

Then I started to get NT_BAD_NETWORK_NAME for both localhost (!!!) and serj. So I deleted all teh stuff that had to do with homes, profiles, and logon drives because I didn't think I had implemented any of that anyway.

Now it just says protocol negotiation failed from the smbclient end (when trying to get to win2k) and A specified authentication package is unknown when trying to refresh the workgroup from teh windows end.

Very confused.

Heres the file I am using:


[global]
netbios name = SHAVO
map to guest = Bad User

[littlebill]
comment = 200GB SATA
path = /mnt/littlebill
directory mask = 0775
guest ok = Yes

[samuel]
comment = 40GB SATA
path = /mnt/samuel
directory mask = 0775
guest ok = Yes


Oh, and testparm reckons its fine.

Hope y'all can help...

Cheers in advance..

damn i feel like a hot chocolate from bp cafe right now...
hamstar (4)
436016 2006-03-07 02:31:00 Playing with permission bits is always dangerous. Sometimes you lose all security, sometimes you just stop things working.

Masks are "masks", not "settings" . That mask would give unusual permissions. The mask is used to turn bits off, not on Perhaps that's why you got access errors. ;)
Graham L (2)
436017 2006-03-07 12:17:00 hmmm... ok. how do you think I could make it so I can see all the files? hamstar (4)
436018 2006-03-07 23:46:00 Oh got it... all the permissions on the folders were set to 700. Sweet now. Will be back to ask about the access issues tho.

Cheers
hamstar (4)
436019 2006-03-09 01:39:00 Yess!!!

Got it all going well now! Just the odd hiccup here and there but it seems to be working fine..

touch wood... lol...

I'll post my smb.conf here for anyone who wants to use a working smb.conf that works with 2k/xp machines :D
hamstar (4)
436020 2006-03-09 04:24:00 So from a mask of 0775 it used only the first three (octal) digits to give 700. I wondered if it might use all four digits, with the first "0" setting the suid and sticky bits. ;) Graham L (2)
436021 2006-03-09 11:58:00 Oh well, actually I turned the masking off... that was just the normal permissions on teh folders...

Tho I could have used a mask of 0000 to give everyone all access couldn't I ?

smb.conf


[global]
workgroup = WORKGROUP
netbios name = shavo
encrypt passwords = yes
smb passwd file = /etc/smbpasswd
map to guest = Bad User
include = /etc/samba/dhcp.conf
logon path = \\%L\profiles\.msprofile
logon home = \\%L\%U\.9xprofile
logon drive = P:
[littlebill]
comment = 200GB SATA
path = /mnt/littlebill
public = yes
browseable = yes
writable = yes
[samuel]
comment = 40GB SATA
path = /mnt/samuel
public = yes
browseable = yes
writeable = yes
[hamstar]
comment = Hamstar's Home
path = /home/hamstar
public = yes
browseable = yes
writeable = yes


Unsure if I need all that logon drive crap.. will explore later - no need to fix something that isn't broken right now ;)

Hope this helps someone else.. :D

keywords: working samba configuration file, smb, samba, smb.conf, opensuse,
hamstar (4)
1