[computers] Re: [Samba] XP Home and Samba problem

[Gary Dale]

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: /xxxxx/ 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.
>>>>
>>>
>>
>