Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello,
Running FC5 on PC with samba.
Have 2 win XP boxes connected via router - XP pro.
Can see and get access to XP boxes from FC5 and also between XP boxes but cant get access to FC5 from either XP box.
Have tried searches and amending samba.conf based on other posts and set up users but XP box keep saying it doesn't have the rights to the workgroup - God I hate windows wizards.
Could you give more info on the samba config you have (you could post the contents of the file in this thread). I think people are going to need more info before they can help.
I think this time the culprid is FC5's extreme level of protection.
In system-config-securitylevel, in Firewall options tab, make sure Samba has a tick, and in SELinux tab, try to put SELinux in permissive mode.
If works, go back SELinux to Enforcing mode, and click on Modify SELinux policy. Check all Samba entries. If it still working, keep enabled only the 2 Allow entries. This is the most secure and still working setting AFAIK.
By the way SeLinux is turned OFF and smb has access rights - I have had problems with Se Linux b4.
# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0.1)
# Date: 2006/08/02 19:50:03
[global]
workgroup = buttling
server string = BUTTLING
encrypt passwords = no
guest account = bill
username map = /etc/samba/smbusers
log file = /var/log/samba/%m.log
max log size = 50
server signing = auto
socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192
printcap name = /etc/printcap
preferred master = No
domain master = No
dns proxy = No
ldap ssl = no
guest ok = yes
cups options = raw
; security = user
[homes]
comment = Home Directories
writeable = yes
browseable = No
[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No
[Documents OK]
path = /home/bill/Data/Documents OK
valid users = bill
[cups]
path = /tmp
printable = Yes
Oh and by the way I have tried to change printcap name to "cups" to enable cups printing - as suggested elsewhere - and testparm faults and smb wont start or run.
with the xp boxes set up a workgroup of myworkgroup (use your own name). Then in the config file of samba, set the workgroup setting to the same. Also, I see that you have a ';' before security=user in the last line of the global section. Its been a while since the last time I set up a samba config file with a text editor, but I don't think its supposed to be there. In the homes section browseable=No will make it so once your xp boxes do see the samba server, they won't be able to see the stuff in that share (same with printers). As far as the printer stuff goes, I don't mess with printers much, so can't help you there. That is all I can think of now with the quick glance I had at your config settings. Try this stuff, and tell me if any of it works.
OK, have spent the best part of the day playing with smb.conf via SWAT and editors but still the XP box throws a wobbly.
The workgroup is set the same but press on "view workgroup computers" and sometimes it will show the linux box and sometimes none of the workgroup - message saying you dont have authorisation etc.
When it shows the linux box it then asks for a password to get access to the shared files but will not accept the user/password set up in samba.
However if I use the "run" command \\10.0.0.1\ then I get access to the linux shared directories.
This seems a windows problem I suppose but I am really frustrated by the fact that the XP is not consistent when you try to access the network - sometimes it recognises the workgroup and sometimes no !!!!
For any one interested her is the smb.conf as I still cant get the printing sorted out.
# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0.1)
# Date: 2006/08/12 18:24:48
[global]
workgroup = BUTTLING
server string = BUTTLING
security = SHARE
auth methods = guest
encrypt passwords = No
guest account = bill
log file = /var/log/samba/%m.log
max log size = 50
server signing = auto
socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192
printcap name = etc/printcap
preferred master = No
domain master = No
dns proxy = No
ldap ssl = no
guest ok = Yes
cups options = raw
[Documents OK]
comment = Bills Files
path = /home/bill/Data/Documents OK
valid users = bill
I have read in several places that to get printing to cups I should change the line "printcap name = etc/printcap" to "printcap name = cups"
Doing this immediately hangs SWAT and smbd wont start, so that seems to be a false trail.
Have got around printing problem by using http printing directly to cups from the XP box, that will have to do for now. There seems to be a lot of unresolved posts about printing through Samba and solutions seem to be distro dependant to a certain extent.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.