*sigh*...samba
Aight, I've pounded google and linuxquestions.org threads for a few days now cause I didn't wanna be a bother with more samba woes. Anyways..heres the dilly. Ive got a RedHat 9.0 machine running as a samba server. Ive got an XPHome machine running as a client. Ive got the username "eric" setup on the linux machine (ie useradd eric) with my password 1234 . I have done smbpasswd -a eric and set it as the same, 1234. On the XP machine it logs in automatically to with the username eric, no password. (both machines are behind a physical firewall by the way. heh) When i browse to the server thru network neighborhood on the client i see the server, i click on it, i see the share name (media) but when i click on that i get a "\\server is not accessiable you may not have permission to acces this recource" error. I have tried setting up the windows username with the 1234 password, but still nothing. (It should prompt me for a password anyways, shouldnt it?)
more info: -Both machines have the firewalls turned off -I can ping from each machine via ip and netbios name -the server serves out NFS shares fine (and with 10 minute setup time - I love Linux!) -I have a headache. -I love anyone that helps me -Heck, here is my smb.conf file: [global] workgroup = ecj server string = Samba Server encrypt passwords = Yes map to guest = Bad Password root directory = / password level = 8 username level = 10 log file = /var/log/samba/%m.log max log size = 0 socket options = TCP_NODELAY SO RCVBUF=8192 SO_SNDBUF=8192 domain logons = Yes wins proxy = Yes wins support = Yes hosts allow = 192.168.0.0/255.255.255.0 127.0.0.1 hosts deny = none printing = lprng preserve case = No short preserve case = No smb passwd file = /etc/samba/smbpasswd # [printers] # comment = All Printers # path = /var/spool/samba # browseable = no # guest ok = no # writable = no # printable = yes # create mode = 0700 [media] path = /mnt/media/audio/audio writable = yes valid users = eric create mode = 775 directory mode = 775 write list = eric read list = eric |
Possibly a silly answer, but when you are logging on via network neighbourhood, are you saying connect as a different user, or just logging on. Normally, windows will assume current user and provide the username and password as what you have logged onto XP with, but if you log on as different user it allows you specify username and password, which ensures the correct info given to samba server. It will at least tell you if the problem is user name and password, which is what the samba server message seems to be indicating.
(Another other option to try might be to blank out the 2 wins references. I came on as the moment I put wins on in redhat 9, the server stops serving in certain instances, and starts behaving weird. Just check you haven't got the same problem) Rob |
did you chmod 777 the shared directory in question? You have to have the following to get access:
1) user account in the smbpasswd file 2) a matching account in the linux password file 3) permissions to the file(s) being shared 4) permissions to the share |
yeah, if u want to save the hassle of samba and trying to get it to work which seems to be a consistent problem. Get a really good ssh client (some of them even look like ws_ftp so it is easy to transfer files) and say screw samba!
This is what i did and guess what no more problems oh yeah and my linux box is more secure because of it......don't have to worry about people crashing samba to get root access!!! |
Just noticed you got the line
Quote:
|
Did you say "domain logons = Yes" is for Vendow$ domains only??
If this is so then that might explain my problem- it keep thinking that w2k box is a DC and vice versa--- hmm gonna try that just for kicks.... Got nothing to lose here. |
I tried that and guess what.... it causes a DNS look up problem...
Which tells me that if you have this set to no that tells stupid Vendow$ there is no Domain to log on too.. Insanity may be next... |
dns proxy = yes
|
Quote:
Quote:
Quote:
Quote:
-thanks for the help so far. Anyone that could push me along with the chmod question would be rad. Thanks! eric. |
samba with XPhome
XP home as a samba client has limitations:
XPhome (aka My Fisher Price Plastic Look) DOES NOT SUPPORT DOMAIN LOGON it ONLY supports "share" access which is back to wfwg era. Its crippled compared to (say) win9x in this respect and we all know why. (XPpro vs XPho) Anyway, to save messing up a working smb.conf file that supports 9x,NT,2K domain logns, roaming and whatnot, theres a useful hack you can use to read in an alternative config file just for xphome hosts. example configs: XPhome host: "paintcan" samba host: "penguin" XPhome usernames: Tom, Dick, Harry unix usernames: tom, dick, harry I'm assuming that tom, dick and harry have their unix accounts and homedirs set up, and smbpasswd -a [username] [sambapasswd] has been run for each. put this line FIRST in smb.conf [global] # if XPh machine "paintcan" connects, then use its cf file instead. # otherwise continue with smb.conf config file = /etc/samba/smb.conf.%m config file: "smb.conf.paintcan" (an example, tailor to fit) [global] # logging log level = 2 ;log level = 3 log file = /var/log/samba.log.%m # Networking configuration options # samba will default to eth0 unless told otherwise interfaces = 192.168.1.254/255.255.255.0 # Server configuration parameters netbios name = PENGUIN workgroup = SMBLOCAL server string = Samba %v on %L username map = /etc/samba/private/smbusers encrypt passwords = yes smb passwd file = /etc/samba/private/smbpasswd # master browser settings (network neighbourhood) wins support = yes local master = yes preferred master = yes os level = 65 ######## SECURITY, access, blocked files, users. ############# # invalid users # this stops the [homes] share matching on a unix username # and creating a share it shouldent invalid users = adm bin cgi daemon ftp games gopher halt \ lp root mail news operator rpm shutdown sync uucp # nb if "nobody" is in the above list, clients wont be able to browse # the network n'hood # if "root" is missing, you wont be able to connect as the samba # administrator (probably a good thing) # Files that have their Linux permissions set to prevent # access shouldn't even appear # dotfiles (.cshrc) can be concealed; revealed by filemgr "show hidden" hide unreadable = yes hide dotfiles = yes # File Blocking # Useful for preventing the spread of virus infections on your server # should a Windows connected client become infected. # The last match bit prevents accessing files with a CLSID in its file extension # the second set is even more strict (see Microsoft KB 290497) ;veto files = /*.exe/*.dll/*.com/*.vbs/*.{*}/ veto files = /*.scr/*.scf/*.sct/*.pif/*.exe/*.bas/*.bat/*.com/*.ade/*.adp/*.asp/*.asx/*.chm/*.cmd/*./ ##### End Security section #### # Printers # Windows clients preprocess the print job # thus the samba printer is set as a raw queue (K6500) # next param stops samba grabbing everything in /etc/printcap load printers = no #=== Share Definitions ============== [homes] comment = %u's Home Directory browsable = no read only = no map archive = no username = tom, dick, harry only user = yes [Laser1] browsable = no printable = yes printing = lprng printer = K6500 print command = /usr/bin/lpr -b -P%p -r %s path = /var/spool/samba min print space = 2000 use client driver = yes Incidentally, setting up samba host as a wins server cuts down on netbios bcast traffic (put the samba host ip into the wins dialog box on the xphome host). Or, (better) set up the samba host as dns host for the windows clients as thats the way MS is going with server 2003 and wins is slated to fade away. |
All times are GMT -5. The time now is 04:22 AM. |