| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 68456 | 2006-04-29 01:23:00 | Samba problem | Greven (91) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 450365 | 2006-04-29 01:23:00 | I've just downloaded & installed the latest stable release of Ubuntu Linux, and I'm having a bit of trouble setting up SAMBA. The network share won't let me log into it - it asks for authentication & won't accept any username/password. I want to share the /home/share folder, so I gave it permissions of 777. I then ran the GUI shared folders tool & added the directory. I didn't make it read only & I ticked "Allow browsing folder" How do I make it accessable from my windows machine without a password? |
Greven (91) | ||
| 450366 | 2006-04-29 01:53:00 | Do you have a user in the smbpasswd file - probably in /etc/samba. If you don't type smbpasswd -a <username> |
gcarmich (10068) | ||
| 450367 | 2006-04-29 03:23:00 | . . . want to share the /home/share folder, so I gave it permissions of 777 . WAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAH :rolleyes: :horrified :( . The permissions are almost always set up correctly, so changing them usually doesn't fix any access problem . . 777 is never a Good Idea . What controls the access to the directories in Samba is the configuration file . It's a long time since I've set one up, but the comments in the file will help you get it right . There is a GUI setup too, for those who like that sort of thing . You do need a smbpasswords file for account/password access control, but you can also have open access . But don't use 777 to try to do that . Samba can access the files, what is stopping you is the access to Samba, which is controlled by smb . conf . |
Graham L (2) | ||
| 450368 | 2006-04-29 06:17:00 | Here is an example from part of one of my /etc/samba/smb.conf files: #Setup for LIBRARY folder [LIBRARY] comment = Shared directory for LIBRARY (sharable) data path = /home/shares/library valid users = user1 user2 user3 public = no writable = yes ;browseable = yes create mask = 0770 force group = staff |
johnd (85) | ||
| 450369 | 2006-04-29 06:24:00 | I tried to set it all up using the GUI to start with. I've just looked through the logs & it gives the following error: [2006/04/29 17:14:07, 0] printing/pcap.c:pcap_cache_reload(149) Unable to open printcap file /etc/printcap for read! Any ideas on why it is trying to print? I commented out the printers part of the smb.conf file & it still does the same thing. |
Greven (91) | ||
| 450370 | 2006-04-29 09:25:00 | i suggest to all people running linux that they should try this app out for their system. http://www.webmin.com/ This lets you take control over your entire system in a nice easy gui through your browser and lets you control everything in nice easy steps and setup everything just they you want and need it. Also its a excellent way of accessing your *nix box and starting and stoping services should you need by remote. Check it out you would be far from disappointed from installing it. |
presso (10113) | ||
| 450371 | 2006-04-29 09:45:00 | I agree that Webmin is a great tool - but it does have a limitation - you learn much more about how systems work if you edit the plain text configuration files directly. These files are usually fill of handy hints and examples - Webmin will from memory wipe these and replace them only with the features you requested via the GUI. Not everybody's cup of tea. | johnd (85) | ||
| 450372 | 2006-04-30 03:20:00 | It's a very good idea to make copies of the configuration files before webmin gets its hands on them. :D "printcap" will be a "printer capabilities" file ... that will be set up by the printer setup configuration. Samba will be looking at that in case you want to use it to share a printer as well as files. I am guessing, but Samba is probably still running even after writing that entry to the log file. You should be able to just set the access to public for the directories you want. |
Graham L (2) | ||
| 450373 | 2006-04-30 03:21:00 | It's a very good idea to make copies of the configuration files before webmin gets its hands on them. :D "printcap" will be a "printer capabilities" file ... that will be set up by the printer setup configuration. Samba will be looking at that in case you want to use it to share a printer as well as files. I am guessing, but Samba is probably still running even after writing that entry to the log file. ;) That wouldn't crash it, and it won't affect the file handling. You should be able to just set the access to public for the directories you want. |
Graham L (2) | ||
| 1 | |||||