[wellylug] Samba shares not accessible

[Hong Chyr]

Thanks guys for the tips. Its a combo of smbpasswd and firewall which 
caused the problem.

So now I'll have to RTFM from scratch for samba and iptables.

Cheers
Hong

Pete Black wrote:

> Make sure the XP box is set to the same workgroup as the samba server, 
> and try mapping a drive with a valid user/pass (e.g setup a samba user 
> on linux with (as root) 'smbpasswd -a <username> ') - Then try and 
> connect using a mapped drive on the XP side- which will prompt you for 
> the credentials to use to connect.
>
> Many of the problems I have seen with XP and samba relate to its 
> policy of always trying to send the logged-in users name rather than 
> attempt anonymous logins. Mapping a drive at least gives you some 
> control over what Windows is sending.
>
> smbpasswd -n -a <username> (where username is the same as your XP 
> username) should create a user account with no password, which may 
> work ok for 'network neighbourhood' access.
>
> I have also found a few options that help out a lot with Windows 
> access in the share sections of smb.conf, especially 'guest only=yes' 
> which skips most of the authentication samba does, especially if you 
> havent set up smb accounts. This should in theory work to let XP 
> connect with its 'network neighbourhood'
>
> Let me know if you still have problems after that
>
> -Pete
>
>
> On 4/08/2005, at 10:17 PM, Mark Robinson wrote:
>
>> Hong Chyr wrote:
>>
>>> Hi all
>>> I've been trying to set up a simple print and file server using 
>>> samba, which will serve several windows XP clients:
>>> Server is running FC3/Samba 3.0.10. Configured a simple share drive 
>>> using
>>> [Global]
>>>    workgroup = workgroup
>>>    netbios name = samba_server
>>> [shared]
>>>    path=/tmp
>>>    guest ok = yes
>>>    browseable = yes
>>> I have tried to connect to the shares using smbclient without any 
>>> problems. The server "samba_server" also appears in the "Network 
>>> Neighbourhood", but  windows kept denying access to the share drive. 
>>> I can't even browse the available resourses on the "samba_server" 
>>> server.
>>> Any ideas?
>>> Thanks
>>> Hong
>>
>>
>> In the old days at least things worked better if you used the samba 
>> nmbd rather than let the windows machine try and be the master.
>>
>>
>>         domain master = yes
>>         wins support = yes
>>         netbios name = foo
>>         local master = yes
>>         workgroup = workgroup
>>         socket address = 10.0.7.3
>>         preferred master = yes
>>
>> That lot may not be perfect, it comes from a slightly broken system.
>>
>> Naturally you need to configure the windows machines to look at the 
>> samba machine for netbios name resolution.
>>
>> Also make sure that none of the relevant ports are being caught up in 
>> firewalls, 135 to 139 and 445 have caused me niggles.
>>
>> You'll likely also need to use smbpasswd.
>>
>>
>>
>> -- 
>> Wellington Linux Users Group Mailing List: 
>> wellylug at lists.wellylug.org.nz
>> To Leave:  http://lists.wellylug.org.nz/mailman/listinfo/wellylug
>
>
>


-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.10.1/64 - Release Date: 4/08/2005


		
___________________________________________________________ 
To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com