samba: windows to linux
I'm having trouble configuring samba. I have a windows xp pro box and a FC3 box. Linux can already see the shared files in windows. But windows can't see files in linux. I get this message everytime windows tries to access shares in linux:
\\192 is not accessible. You might not have permission to use this network resource. Contact the network administrator of this server to find out if you have access permissions. The network path was not found. I get this message everytime I double click on the Samba Server icon in network neighborhood>>workgroup in windows. here's my smb.conf Code:
# This is the main Samba configuration file. You should read the Code:
# Unix_name = SMB_name1 SMB_name2 ... |
Looks like you only have the printer available.
Try uncommenting this bit ;[public] ; comment = Public Stuff ; path = /home/samba ; public = yes ; read only = yes and see if that works From a barely knowledgable samba user |
I uncommented that part yet still can't view my linux shares from windows. Why is it that in the error message, it says that it cannot access \\192? Shouldn't it say \\192.168.0.3 which is the full ip address of my linux box?
|
Re: samba: windows to linux
Hi There,
In ur Home share u had not given any path for sharing ur home directories. Give path for sharing home direcoty. Ex => path = /home/paul Also give ur public ok = yes for public access. and restart ur samba server and then access using Windows XP . now it will be able to access ur shares . Hope this helps u. Ur's Utsav Handa # Learning Linux |
I can't find any share named home. But there is one named homes. I modified it to look like this:
[homes] comment = Home Directories path = /home/paulr1984 browseable = yes writeable = yes public ok = yes now smbd won't start. It doesn't even give an error message. But it works fine if I remove the modifications. |
I'll ask the obvious question does /home/paulr1984 exist on your Linux box?
Other check the various log files in /var/log Can you ping each box from the other, I'm thinking firewall problem. |
yes /home/paulr1984 exists. And I can ping the windows box from the linux box as well as the other way around. There are no messages in the /var/log/messages or even dmesg which concerns samba.
I still can't access linux shares from windows. =( |
Quote:
it may give you an idea about how it all works. Note this was setup for me by a couple ofmore knowledgable guys and it was a while back. You'll have to massage this a bit a samba has moved on from when it was first written smb.conf: ; The global setting for a RedHat default install ; Make sure you tes the config with testparm before restarting ; Make sure and restart the server after making changes to this file, ex: ; /etc/init.d/samba stop ; /etc/init.d/samba start [global] workgroup = House volume = Boxen log file = /var/log/samba/log.%m max log size = 500 ; lock directory = /var/lock/samba share modes = yes dont descend = /proc,/dev server string = %h's Samba server: V%v ; comment = %h server (Samba %v) syslog only = no syslog = 1 ; bind interfaces only = yes ; interfaces = 192.168.69.0/24 10.1.100.0/24 ; File name mangling options short preserve case = yes preserve case = yes ; name service setup name resolve order = lmhosts host wins bcast dns proxy = yes ; network configuration include=/etc/samba/logon.conf ; user - password configuration include=/etc/samba/passwd.conf ; printer configuration include=/etc/samba/printing.conf [netlogon] path = /etc/samba/netlogon ; writeable = no read only = yes guest ok = no [homes] comment = Home Directories public = no browseable = no read only = no ; writeable = yes create mode = 0770 directory mask = 0770 [tmp] comment = Temporary file space path = /var/windows/tmp read only = no public = yes ; A publicly accessible directory, but read only, except for people in ; the staff group [public] comment = Public Stuff path = /home/ftp public = yes ; writable = no read only = yes printable = no write list = @staff [personal-ftp] comment = Users Public Stuff path = /home/ftp/users/%u force user = %u public = no browseable = yes read only = yes write list = %u printable = no create mode = 0765 [data] path = /var/windows/data public = yes only guest = yes ; writable = yes read only = no printable = no ; create mask = 0765 [programs] path = /var/windows/programs public = yes only guest = yes ; writable = yes read only = no printable = no ; create mask = 0765 logon.conf: os level = 50 domain master = yes local master = yes domain logons = yes preferred master = yes wins support = yes ; hosts allow = 192.168. logon drive = p: logon home = \\%N\%u ; logon path = \\%N\%u\winfiles ; logon script = winfiles\winstart.bat logon script = %g\UserStart.bat ; logon script = UserStart.bat now the batch file was stored 2 levels down in 2 seperate directories thus netlogon/guest netlogon/users Note BOX is the name of samba server UserStart.bat: NET TIME \\BOX /SET /YES NET USE N: \\BOX\DATA NET USE S: \\BOX\TMP NET USE Y: \\BOX\PROGRAMS NET USE P: \\BOX\HOMES call p:\winfiles\winstart.bat |
Yours acts like it could be a firewall issue. Make sure a firewall on your FC3 box is not blacking the SMB traffic.
You do not need to list a directory in the [homes] share. That is a built in share with Samba that will automatically share the user's home directory when they connect. |
Hi -
Just went through the Samba rounds myself. First off, if you want to solve this problem, take it a piece at a time. Lot's of good advice, however, you need to zero in on one issue at a time. First -- a great reference: http://www.faqs.org/docs/samba/ch00.html Helped me a lot. Next - turn on debugging. You only have one part of this done: In the [globals] section, you have the log file denoted by: log file = /var/log/samba/%m.log but no log level. Add: log level = 2 In the same section. Restart the smb server (I use my rc scripts). On SuSE, it's: /etc/rc.d/rc5.d/S15smb restart Check where you specified. Ok - you should start to "see" what's going on. Next, you should start testing the 'smd' server from your Linux system FIRST - after all, you want to be sure it's actually listening! First off - is the smb daemon being started? I don't know what you're using to kick start the process (inetd, xinetd, manual, whatever), so, let's assume it's runing. If you use your rc scripts like I mentioned above, you'll be on your way to knowing if there's a startup problem. Next - try using the local 'smbclient' program to list what "shares" the Samba server will dish up. On my SuSE install, it's located at /usr/bin/smbclient: # /usr/bin/smbclient -U% -L localhost You should get info telling you network interface info, and the shares the server knows about. IF YOU DON'T SEE THIS STUFF, YOUR SMB SERVER IS NOT UP! Now, this is probably where things are getting out of whack. How about trying this out and coming back to the forum with more poop on how far this gets you, ok? good luck! |
The reference looks good. I maust admit I never really understood how samba worked I simply modified a working config to suit my needs
|
i might be wron but do try this
hi,
i have samba configured at home and it is working fine... at the moment atleast. From what i can see (with my limited knowlege) it could be that the linux system is refusing connections to all external machines.. please have a look at /etc/host.allow /etc/host.deny files. also, try enabling the line allow hosts = (list of some ips separated by space) in the global section of smb.cong file. regards do tell if it works Edit By the way the file locations i am mentioning are for redhat , they may be different on your distribution. But i think the concept would still apply. |
All times are GMT -5. The time now is 09:12 PM. |