Re: [computers] Re: [Samba] XP Home and Samba problem
You do, of course, have valid smb accounts and passwords created on borzo for each XP client where the XP account (username) and the XP account (password) are identical and match the Linux user account (username) and the smb (password) created with the smbpasswd -a command, right? Yes, I know that is not a strict requirement, but unless you're doing UID and GID mapping, it never hurts! -- David C. Rankin, J.D., P.E. 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com -- - Original Message - From: SG [EMAIL PROTECTED] Cc: samba samba@lists.samba.org Sent: Wednesday, July 11, 2007 6:30 AM Subject: Re: [computers] Re: [Samba] XP Home and Samba problem Problem resolved!, I created a XP user test123 with a null password, logged in and everything worked fine then I logged back to borzo and everything went back to normal. I must say this is the weirdest case i ever had and i stll don't understand what happened. Anyway, thanks for all the help :) SG SG pisze: I Tried XP restarts, and tried removing hosts allow/deny, and I still have the same problem, enforced guest login. I am starting to wonder if this might be somehow related to the fact that I changed the XP's name, except that it shouldn't be a problem as I see the new XP name and shares correctly from Linux. I Will try to add a new user to XP and add that to samba, login with the new user and see if it works then. Gary Dale pisze: You should also try removing your global hosts allow and hosts deny lines. If they aren't done properly, they can cause you to be unable to connect. Gary Dale wrote: Is your borzo password on Unix the same as your borzo password on Windows? And have you tried rebooting your Windows box between attempts to connect? SG wrote: After a couple of minutes of inactivity I tried to access the samba share again and I got the error message I wrote about previously: * Error Message: /x/ is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permission * . The share is accessible locally and so is the XP share from Linux. Gary Dale pisze: You said, I believe, that you are running XP/Home. Are you logged on as borzo (and not Borzo, BORZO or some other variant)? Also, take it back to just including the path, restart samba, and let us know the exact error message Windows gives you. SG wrote: From [global] I have removed valid users At first in [MyFiles] I left only the path, which didn't work at all ( I was presented with an error on XP ), here's what I'm left with: [MyFiles] path = /home/samba/ force user = borzo force group = borzo create mask = 0644 directory mask = 755 but this didn't change the situation, I am still presented by the grayedout login prompt, and by the way the share is accessible through samba locally, aswell as the XP shares. The share's permissions are set to 0777, user and group are set to borzo and borzo is added and enabled with smbpasswd. thanks so far, SG Gary Dale pisze: simo wrote: On Tue, 2007-07-10 at 18:02 +0200, SG wrote: Here's my smb.conf [global] workgroup = GINVEST netbios name = LINACER interfaces = ath0, eth0 bind interfaces only = Yes null passwords = Yes passdb backend = tdbsam username map = /etc/samba/smbusers log level = 3 log file = /var/log/samba/log.%m announce version = 5.0 name resolve order = host wins bcast socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = CUPS os level = 32 wins support = Yes invalid users = root valid users = borzo --^^ you really _don't_ want to put this in the global section, or the only user allowed is borzo everywhere, and guest connections will always be denied. [..] Simo. Yes, but that probably isn't his problem as he also has borzo as the only valid user for his MyFiles share. My concern is that he has so much other unnecessary entries in his share definition. My advice to him would be to clear out all the unnecessary stuff until he can get a working share. Start with just the path and see if that works. If it doesn't then your problem lies elsewhere. What are the Unix directory permissions for the share? Try setting them to allow everyone read-write-execute access. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [computers] Re: [Samba] XP Home and Samba problem
I Tried XP restarts, and tried removing hosts allow/deny, and I still have the same problem, enforced guest login. I am starting to wonder if this might be somehow related to the fact that I changed the XP's name, except that it shouldn't be a problem as I see the new XP name and shares correctly from Linux. I Will try to add a new user to XP and add that to samba, login with the new user and see if it works then. Gary Dale pisze: You should also try removing your global hosts allow and hosts deny lines. If they aren't done properly, they can cause you to be unable to connect. Gary Dale wrote: Is your borzo password on Unix the same as your borzo password on Windows? And have you tried rebooting your Windows box between attempts to connect? SG wrote: After a couple of minutes of inactivity I tried to access the samba share again and I got the error message I wrote about previously: * Error Message: /x/ is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permission * . The share is accessible locally and so is the XP share from Linux. Gary Dale pisze: You said, I believe, that you are running XP/Home. Are you logged on as borzo (and not Borzo, BORZO or some other variant)? Also, take it back to just including the path, restart samba, and let us know the exact error message Windows gives you. SG wrote: From [global] I have removed valid users At first in [MyFiles] I left only the path, which didn't work at all ( I was presented with an error on XP ), here's what I'm left with: [MyFiles] path = /home/samba/ force user = borzo force group = borzo create mask = 0644 directory mask = 755 but this didn't change the situation, I am still presented by the grayedout login prompt, and by the way the share is accessible through samba locally, aswell as the XP shares. The share's permissions are set to 0777, user and group are set to borzo and borzo is added and enabled with smbpasswd. thanks so far, SG Gary Dale pisze: simo wrote: On Tue, 2007-07-10 at 18:02 +0200, SG wrote: Here's my smb.conf [global] workgroup = GINVEST netbios name = LINACER interfaces = ath0, eth0 bind interfaces only = Yes null passwords = Yes passdb backend = tdbsam username map = /etc/samba/smbusers log level = 3 log file = /var/log/samba/log.%m announce version = 5.0 name resolve order = host wins bcast socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = CUPS os level = 32 wins support = Yes invalid users = root valid users = borzo --^^ you really _don't_ want to put this in the global section, or the only user allowed is borzo everywhere, and guest connections will always be denied. [..] Simo. Yes, but that probably isn't his problem as he also has borzo as the only valid user for his MyFiles share. My concern is that he has so much other unnecessary entries in his share definition. My advice to him would be to clear out all the unnecessary stuff until he can get a working share. Start with just the path and see if that works. If it doesn't then your problem lies elsewhere. What are the Unix directory permissions for the share? Try setting them to allow everyone read-write-execute access. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [computers] Re: [Samba] XP Home and Samba problem
Problem resolved!, I created a XP user test123 with a null password, logged in and everything worked fine then I logged back to borzo and everything went back to normal. I must say this is the weirdest case i ever had and i stll don't understand what happened. Anyway, thanks for all the help :) SG SG pisze: I Tried XP restarts, and tried removing hosts allow/deny, and I still have the same problem, enforced guest login. I am starting to wonder if this might be somehow related to the fact that I changed the XP's name, except that it shouldn't be a problem as I see the new XP name and shares correctly from Linux. I Will try to add a new user to XP and add that to samba, login with the new user and see if it works then. Gary Dale pisze: You should also try removing your global hosts allow and hosts deny lines. If they aren't done properly, they can cause you to be unable to connect. Gary Dale wrote: Is your borzo password on Unix the same as your borzo password on Windows? And have you tried rebooting your Windows box between attempts to connect? SG wrote: After a couple of minutes of inactivity I tried to access the samba share again and I got the error message I wrote about previously: * Error Message: /x/ is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permission * . The share is accessible locally and so is the XP share from Linux. Gary Dale pisze: You said, I believe, that you are running XP/Home. Are you logged on as borzo (and not Borzo, BORZO or some other variant)? Also, take it back to just including the path, restart samba, and let us know the exact error message Windows gives you. SG wrote: From [global] I have removed valid users At first in [MyFiles] I left only the path, which didn't work at all ( I was presented with an error on XP ), here's what I'm left with: [MyFiles] path = /home/samba/ force user = borzo force group = borzo create mask = 0644 directory mask = 755 but this didn't change the situation, I am still presented by the grayedout login prompt, and by the way the share is accessible through samba locally, aswell as the XP shares. The share's permissions are set to 0777, user and group are set to borzo and borzo is added and enabled with smbpasswd. thanks so far, SG Gary Dale pisze: simo wrote: On Tue, 2007-07-10 at 18:02 +0200, SG wrote: Here's my smb.conf [global] workgroup = GINVEST netbios name = LINACER interfaces = ath0, eth0 bind interfaces only = Yes null passwords = Yes passdb backend = tdbsam username map = /etc/samba/smbusers log level = 3 log file = /var/log/samba/log.%m announce version = 5.0 name resolve order = host wins bcast socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = CUPS os level = 32 wins support = Yes invalid users = root valid users = borzo --^^ you really _don't_ want to put this in the global section, or the only user allowed is borzo everywhere, and guest connections will always be denied. [..] Simo. Yes, but that probably isn't his problem as he also has borzo as the only valid user for his MyFiles share. My concern is that he has so much other unnecessary entries in his share definition. My advice to him would be to clear out all the unnecessary stuff until he can get a working share. Start with just the path and see if that works. If it doesn't then your problem lies elsewhere. What are the Unix directory permissions for the share? Try setting them to allow everyone read-write-execute access. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [computers] Re: [Samba] XP Home and Samba problem
Here's my smb.conf [global] workgroup = GINVEST netbios name = LINACER interfaces = ath0, eth0 bind interfaces only = Yes null passwords = Yes passdb backend = tdbsam username map = /etc/samba/smbusers log level = 3 log file = /var/log/samba/log.%m announce version = 5.0 name resolve order = host wins bcast socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = CUPS os level = 32 wins support = Yes invalid users = root valid users = borzo hosts allow = 127.0.0.1, 127.0.0.2, 192.168.2.1, 192.168.2.2, 192.168.2.3 hosts deny = 0.0.0.0/0 printing = cups lpq command = %p [print$] path = /var/lib/samba/printers write list = root create mask = 0664 directory mask = 0775 guest ok = Yes [printers] path = /tmp guest ok = Yes printable = Yes browseable = No [MyFiles] path = /home/samba/ valid users = borzo force user = borzo force group = borzo read only = No create mask = 0644 directory mask = 755 browsable = yes read only = no guest ok = no Dave Ewart pisze: On Tuesday, 10.07.2007 at 16:19 +0200, SG wrote: I am unable to connect to my Linux samba shares from XP Home, I always get a grayed out login field with guest selected. I googled around for solutions but none helped. XP Home cannot connect, IIRC, to a Samba server which is acting as a domain controller... XP Pro is required for that. I'd suggest posting your smb.conf if you need additional help. Dave. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [computers] Re: [Samba] XP Home and Samba problem
On Tue, 2007-07-10 at 18:02 +0200, SG wrote: Here's my smb.conf [global] workgroup = GINVEST netbios name = LINACER interfaces = ath0, eth0 bind interfaces only = Yes null passwords = Yes passdb backend = tdbsam username map = /etc/samba/smbusers log level = 3 log file = /var/log/samba/log.%m announce version = 5.0 name resolve order = host wins bcast socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = CUPS os level = 32 wins support = Yes invalid users = root valid users = borzo --^^ you really _don't_ want to put this in the global section, or the only user allowed is borzo everywhere, and guest connections will always be denied. [..] Simo. -- Simo Sorce Samba Team GPL Compliance Officer email: [EMAIL PROTECTED] http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [computers] Re: [Samba] XP Home and Samba problem
simo wrote: On Tue, 2007-07-10 at 18:02 +0200, SG wrote: Here's my smb.conf [global] workgroup = GINVEST netbios name = LINACER interfaces = ath0, eth0 bind interfaces only = Yes null passwords = Yes passdb backend = tdbsam username map = /etc/samba/smbusers log level = 3 log file = /var/log/samba/log.%m announce version = 5.0 name resolve order = host wins bcast socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = CUPS os level = 32 wins support = Yes invalid users = root valid users = borzo --^^ you really _don't_ want to put this in the global section, or the only user allowed is borzo everywhere, and guest connections will always be denied. [..] Simo. Yes, but that probably isn't his problem as he also has borzo as the only valid user for his MyFiles share. My concern is that he has so much other unnecessary entries in his share definition. My advice to him would be to clear out all the unnecessary stuff until he can get a working share. Start with just the path and see if that works. If it doesn't then your problem lies elsewhere. What are the Unix directory permissions for the share? Try setting them to allow everyone read-write-execute access. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [computers] Re: [Samba] XP Home and Samba problem
From [global] I have removed valid users At first in [MyFiles] I left only the path, which didn't work at all ( I was presented with an error on XP ), here's what I'm left with: [MyFiles] path = /home/samba/ force user = borzo force group = borzo create mask = 0644 directory mask = 755 but this didn't change the situation, I am still presented by the grayedout login prompt, and by the way the share is accessible through samba locally, aswell as the XP shares. The share's permissions are set to 0777, user and group are set to borzo and borzo is added and enabled with smbpasswd. thanks so far, SG Gary Dale pisze: simo wrote: On Tue, 2007-07-10 at 18:02 +0200, SG wrote: Here's my smb.conf [global] workgroup = GINVEST netbios name = LINACER interfaces = ath0, eth0 bind interfaces only = Yes null passwords = Yes passdb backend = tdbsam username map = /etc/samba/smbusers log level = 3 log file = /var/log/samba/log.%m announce version = 5.0 name resolve order = host wins bcast socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = CUPS os level = 32 wins support = Yes invalid users = root valid users = borzo --^^ you really _don't_ want to put this in the global section, or the only user allowed is borzo everywhere, and guest connections will always be denied. [..] Simo. Yes, but that probably isn't his problem as he also has borzo as the only valid user for his MyFiles share. My concern is that he has so much other unnecessary entries in his share definition. My advice to him would be to clear out all the unnecessary stuff until he can get a working share. Start with just the path and see if that works. If it doesn't then your problem lies elsewhere. What are the Unix directory permissions for the share? Try setting them to allow everyone read-write-execute access. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [computers] Re: [Samba] XP Home and Samba problem
You said, I believe, that you are running XP/Home. Are you logged on as borzo (and not Borzo, BORZO or some other variant)? Also, take it back to just including the path, restart samba, and let us know the exact error message Windows gives you. SG wrote: From [global] I have removed valid users At first in [MyFiles] I left only the path, which didn't work at all ( I was presented with an error on XP ), here's what I'm left with: [MyFiles] path = /home/samba/ force user = borzo force group = borzo create mask = 0644 directory mask = 755 but this didn't change the situation, I am still presented by the grayedout login prompt, and by the way the share is accessible through samba locally, aswell as the XP shares. The share's permissions are set to 0777, user and group are set to borzo and borzo is added and enabled with smbpasswd. thanks so far, SG Gary Dale pisze: simo wrote: On Tue, 2007-07-10 at 18:02 +0200, SG wrote: Here's my smb.conf [global] workgroup = GINVEST netbios name = LINACER interfaces = ath0, eth0 bind interfaces only = Yes null passwords = Yes passdb backend = tdbsam username map = /etc/samba/smbusers log level = 3 log file = /var/log/samba/log.%m announce version = 5.0 name resolve order = host wins bcast socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = CUPS os level = 32 wins support = Yes invalid users = root valid users = borzo --^^ you really _don't_ want to put this in the global section, or the only user allowed is borzo everywhere, and guest connections will always be denied. [..] Simo. Yes, but that probably isn't his problem as he also has borzo as the only valid user for his MyFiles share. My concern is that he has so much other unnecessary entries in his share definition. My advice to him would be to clear out all the unnecessary stuff until he can get a working share. Start with just the path and see if that works. If it doesn't then your problem lies elsewhere. What are the Unix directory permissions for the share? Try setting them to allow everyone read-write-execute access. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [computers] Re: [Samba] XP Home and Samba problem
Ok, I don't know what's going on, I left only the path and this time I didn't get that error, just the grayed out login prompt. Maybe I checked it too quickly after restarting samba last time thus the error? The user is exatly borzo everywhere. Gary Dale pisze: You said, I believe, that you are running XP/Home. Are you logged on as borzo (and not Borzo, BORZO or some other variant)? Also, take it back to just including the path, restart samba, and let us know the exact error message Windows gives you. SG wrote: From [global] I have removed valid users At first in [MyFiles] I left only the path, which didn't work at all ( I was presented with an error on XP ), here's what I'm left with: [MyFiles] path = /home/samba/ force user = borzo force group = borzo create mask = 0644 directory mask = 755 but this didn't change the situation, I am still presented by the grayedout login prompt, and by the way the share is accessible through samba locally, aswell as the XP shares. The share's permissions are set to 0777, user and group are set to borzo and borzo is added and enabled with smbpasswd. thanks so far, SG Gary Dale pisze: simo wrote: On Tue, 2007-07-10 at 18:02 +0200, SG wrote: Here's my smb.conf [global] workgroup = GINVEST netbios name = LINACER interfaces = ath0, eth0 bind interfaces only = Yes null passwords = Yes passdb backend = tdbsam username map = /etc/samba/smbusers log level = 3 log file = /var/log/samba/log.%m announce version = 5.0 name resolve order = host wins bcast socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = CUPS os level = 32 wins support = Yes invalid users = root valid users = borzo --^^ you really _don't_ want to put this in the global section, or the only user allowed is borzo everywhere, and guest connections will always be denied. [..] Simo. Yes, but that probably isn't his problem as he also has borzo as the only valid user for his MyFiles share. My concern is that he has so much other unnecessary entries in his share definition. My advice to him would be to clear out all the unnecessary stuff until he can get a working share. Start with just the path and see if that works. If it doesn't then your problem lies elsewhere. What are the Unix directory permissions for the share? Try setting them to allow everyone read-write-execute access. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [computers] Re: [Samba] XP Home and Samba problem
After a couple of minutes of inactivity I tried to access the samba share again and I got the error message I wrote about previously: * Error Message: /x/ is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permission * . The share is accessible locally and so is the XP share from Linux. Gary Dale pisze: You said, I believe, that you are running XP/Home. Are you logged on as borzo (and not Borzo, BORZO or some other variant)? Also, take it back to just including the path, restart samba, and let us know the exact error message Windows gives you. SG wrote: From [global] I have removed valid users At first in [MyFiles] I left only the path, which didn't work at all ( I was presented with an error on XP ), here's what I'm left with: [MyFiles] path = /home/samba/ force user = borzo force group = borzo create mask = 0644 directory mask = 755 but this didn't change the situation, I am still presented by the grayedout login prompt, and by the way the share is accessible through samba locally, aswell as the XP shares. The share's permissions are set to 0777, user and group are set to borzo and borzo is added and enabled with smbpasswd. thanks so far, SG Gary Dale pisze: simo wrote: On Tue, 2007-07-10 at 18:02 +0200, SG wrote: Here's my smb.conf [global] workgroup = GINVEST netbios name = LINACER interfaces = ath0, eth0 bind interfaces only = Yes null passwords = Yes passdb backend = tdbsam username map = /etc/samba/smbusers log level = 3 log file = /var/log/samba/log.%m announce version = 5.0 name resolve order = host wins bcast socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = CUPS os level = 32 wins support = Yes invalid users = root valid users = borzo --^^ you really _don't_ want to put this in the global section, or the only user allowed is borzo everywhere, and guest connections will always be denied. [..] Simo. Yes, but that probably isn't his problem as he also has borzo as the only valid user for his MyFiles share. My concern is that he has so much other unnecessary entries in his share definition. My advice to him would be to clear out all the unnecessary stuff until he can get a working share. Start with just the path and see if that works. If it doesn't then your problem lies elsewhere. What are the Unix directory permissions for the share? Try setting them to allow everyone read-write-execute access. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [computers] Re: [Samba] XP Home and Samba problem
Is your borzo password on Unix the same as your borzo password on Windows? And have you tried rebooting your Windows box between attempts to connect? SG wrote: After a couple of minutes of inactivity I tried to access the samba share again and I got the error message I wrote about previously: * Error Message: /x/ is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permission * . The share is accessible locally and so is the XP share from Linux. Gary Dale pisze: You said, I believe, that you are running XP/Home. Are you logged on as borzo (and not Borzo, BORZO or some other variant)? Also, take it back to just including the path, restart samba, and let us know the exact error message Windows gives you. SG wrote: From [global] I have removed valid users At first in [MyFiles] I left only the path, which didn't work at all ( I was presented with an error on XP ), here's what I'm left with: [MyFiles] path = /home/samba/ force user = borzo force group = borzo create mask = 0644 directory mask = 755 but this didn't change the situation, I am still presented by the grayedout login prompt, and by the way the share is accessible through samba locally, aswell as the XP shares. The share's permissions are set to 0777, user and group are set to borzo and borzo is added and enabled with smbpasswd. thanks so far, SG Gary Dale pisze: simo wrote: On Tue, 2007-07-10 at 18:02 +0200, SG wrote: Here's my smb.conf [global] workgroup = GINVEST netbios name = LINACER interfaces = ath0, eth0 bind interfaces only = Yes null passwords = Yes passdb backend = tdbsam username map = /etc/samba/smbusers log level = 3 log file = /var/log/samba/log.%m announce version = 5.0 name resolve order = host wins bcast socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = CUPS os level = 32 wins support = Yes invalid users = root valid users = borzo --^^ you really _don't_ want to put this in the global section, or the only user allowed is borzo everywhere, and guest connections will always be denied. [..] Simo. Yes, but that probably isn't his problem as he also has borzo as the only valid user for his MyFiles share. My concern is that he has so much other unnecessary entries in his share definition. My advice to him would be to clear out all the unnecessary stuff until he can get a working share. Start with just the path and see if that works. If it doesn't then your problem lies elsewhere. What are the Unix directory permissions for the share? Try setting them to allow everyone read-write-execute access. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [computers] Re: [Samba] XP Home and Samba problem
You should also try removing your global hosts allow and hosts deny lines. If they aren't done properly, they can cause you to be unable to connect. Gary Dale wrote: Is your borzo password on Unix the same as your borzo password on Windows? And have you tried rebooting your Windows box between attempts to connect? SG wrote: After a couple of minutes of inactivity I tried to access the samba share again and I got the error message I wrote about previously: * Error Message: /x/ is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permission * . The share is accessible locally and so is the XP share from Linux. Gary Dale pisze: You said, I believe, that you are running XP/Home. Are you logged on as borzo (and not Borzo, BORZO or some other variant)? Also, take it back to just including the path, restart samba, and let us know the exact error message Windows gives you. SG wrote: From [global] I have removed valid users At first in [MyFiles] I left only the path, which didn't work at all ( I was presented with an error on XP ), here's what I'm left with: [MyFiles] path = /home/samba/ force user = borzo force group = borzo create mask = 0644 directory mask = 755 but this didn't change the situation, I am still presented by the grayedout login prompt, and by the way the share is accessible through samba locally, aswell as the XP shares. The share's permissions are set to 0777, user and group are set to borzo and borzo is added and enabled with smbpasswd. thanks so far, SG Gary Dale pisze: simo wrote: On Tue, 2007-07-10 at 18:02 +0200, SG wrote: Here's my smb.conf [global] workgroup = GINVEST netbios name = LINACER interfaces = ath0, eth0 bind interfaces only = Yes null passwords = Yes passdb backend = tdbsam username map = /etc/samba/smbusers log level = 3 log file = /var/log/samba/log.%m announce version = 5.0 name resolve order = host wins bcast socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = CUPS os level = 32 wins support = Yes invalid users = root valid users = borzo --^^ you really _don't_ want to put this in the global section, or the only user allowed is borzo everywhere, and guest connections will always be denied. [..] Simo. Yes, but that probably isn't his problem as he also has borzo as the only valid user for his MyFiles share. My concern is that he has so much other unnecessary entries in his share definition. My advice to him would be to clear out all the unnecessary stuff until he can get a working share. Start with just the path and see if that works. If it doesn't then your problem lies elsewhere. What are the Unix directory permissions for the share? Try setting them to allow everyone read-write-execute access. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
