FreeBSD as Samba Server and Windows as Client

[Mehmet Erol Sanliturk]

On Tue, Apr 16, 2013 at 2:40 PM, Joshua Isom <jrisom at gmail.com> wrote:

> On 4/16/2013 2:20 PM, Mehmet Erol Sanliturk wrote:
>
>> Dear All ,
>>
>> I could be able to connect a FreeBSD 9.1 amd64 computer as client to a
>> Windows XP ( 32 bits ) by
>> using information supplied by the mail
>>
>> http://lists.freebsd.org/**pipermail/freebsd-questions/**
>> 2013-April/250500.html<http://lists.freebsd.org/pipermail/freebsd-questions/2013-April/250500.html>
>>
>> and I sent a mail
>>
>> http://lists.freebsd.org/**pipermail/freebsd-doc/2013-**April/021857.html<http://lists.freebsd.org/pipermail/freebsd-doc/2013-April/021857.html>
>>
>> to share my findings .
>>
>>
>> Previously , I tried to make a FreeBSD 9.1 amd64 as Samba server and
>> connect a Windows XP as a client computer .
>>
>> By using The FreeBSD Handbook , many documents from www.samba.org and
>> Internet ,
>> I could not be able to access to the FreeBSD Samba server from Windows XP
>> :
>>
>> Continuously I have received "Access denied" error message in Windows XP
>> although in the server the related directory and files have mode
>> rwx-rwx-rwx .
>>
>> The same message is produced even for Linux Samba Server .
>>
>> The examples given in the documents are partial statements without
>> actually
>> used
>> files / statements in such a setting , and sometimes inconsistent or
>> contradictory
>> with each other because they are mostly written manually .
>>
>>
>> If a working , applicable set of files / statements are supplied , it will
>> be appreciated very much .
>>
>> After a successful implementation , I will send an e-mail about this set
>> up
>> as an example for
>> the FreeBSD Handbook to share our information with other people in need .
>>
>>
>> Thank you very much .
>>
>> Mehmet Erol Sanliturk
>>
>
> My guess is your firewall.  Samba uses tcp and udp, you have to allow udp
> on ports 137 and 138.  Turn off your firewall and try again.  It's
> frustrated me a couple times when I've first set it up.  Either that, or
> add `guest ok = Yes` lines to the shares.  If you have a second non-windows
> computer available, I'd try with that.  Windows makes some assumptions
> about what to remember, and sort of assumes the server's working properly
> from the beginning.  Using another computer will make testing faster.
>


In Windows , Firewall is OFF .
There is no any other firewall in the network .
>From a Linux computer , it is possible to connect .
Guest is allowed .

In Windows , in its menus , during my settings , I could not see any
mention of "Ports" .
Therefore , it is necessary to know how to set such ports .

It seems that , some values are not set in Windows .

In documents , sometimes their writers , are not mentioning some points .
These points may be not important for them but may be critical for a newly
starter
person .

Documentation write-ups are full of such missing "expertise" information .

Thank you very much .

Mehmet Erol Sanliturk