[Samba] Windows 8.1 client not able to see and connect to samba server

[Rowland Penny]

On 19/11/14 12:59, L.P.H. van Belle wrote:
> Hi Rowland,
> Yes i've seen that and even is the server is running standalone, dns resolving still needs to work.
> ( wel would make me happy if it does ;-) )
> If he even cant ping the server by hostname.
> maybe a mixed up with fixed ip/dns settings in the W8.1 pc and/or user without password.
>
> ( speculation mode on )
> so the router gives dhcp, the router send ISP DNS ipnumbers.
> logical ping hostname does not work but internet does work.
>
> the other pc's are know in the network, maybe fixed ip, and with fixed ip, arp/netbiosname is know in the router.
> ( speculation mode off )  ;-)
>
> so i suggest change  in global.
>
> security = USER
> to
> security = share
>
> and add to the share:
>      guest ok = yes
>
> now it should accept every connection.
> if not add also : map to guest = bad password
>
> but i dont know if he want security at all on that server.
>
> and now access the server by  open explorer and type  \\IP_of_server\
> and report back.
>
> Louis
>
>
>> -----Oorspronkelijk bericht-----
>> Van: rowlandpenny at googlemail.com
>> [mailto:samba-bounces at lists.samba.org] Namens Rowland Penny
>> Verzonden: woensdag 19 november 2014 13:28
>> Aan: samba at lists.samba.org
>> Onderwerp: Re: [Samba] Windows 8.1 client not able to see and
>> connect to samba server
>>
>> On 19/11/14 12:18, L.P.H. van Belle wrote:
>>> Hai,
>>>
>>> based on below, im guessing the computer hasn't joined the domain.
>>> You can try to set a domain prefix on the lan interface in
>> windows, so the domain search/dns request are correct.
>>> second option, add the servername in the hosts file on the
>> win8.1 computer.
>>> and does the user on this windows 8.1 uses a password, or
>> password less login on the pc.
>>> and you can try to change :
>>>
>>> map to guest = bad user
>>> to
>>> map to guest = bad password
>>>
>>>
>>>
>>> Greetz,
>>>
>>> Louis
>>>
>>>
>>>> -----Oorspronkelijk bericht-----
>>>> Van: rowlandpenny at googlemail.com
>>>> [mailto:samba-bounces at lists.samba.org] Namens Rowland Penny
>>>> Verzonden: woensdag 19 november 2014 12:54
>>>> Aan: samba at lists.samba.org
>>>> Onderwerp: Re: [Samba] Windows 8.1 client not able to see and
>>>> connect to samba server
>>>>
>>>> On 19/11/14 11:33, Eike Hinderk Jürrens wrote:
>>>>> Hi Marc,
>>>>> thank you for your response.
>>>>>
>>>>> On 18.11.2014 21:37, Marc Muehlfeld wrote:
>>>>>> Hello Eike,
>>>>>>
>>>>>> Am 18.11.2014 um 14:05 schrieb Eike Hinderk Jürrens:
>>>>>>> My Windows 7 and Windows 8.1 client are able to find the
>> server and
>>>>>>> connect to the shares but the Windows 8.1 client of a
>>>> colleague is not
>>>>>>> able to find and connect to the server.
>>>>>>>
>>>>>>> The failing client is able to ping the IP of the samba
>>>> server but when
>>>>>>> connecting to it, I get the following error message:
>>>>>>>
>>>>>>> 0x80004005 unspecified error
>>>>>>>
>>>>>>> Searching for this error results in some hits that
>>>> requires to change
>>>>>>> three registry entries under
>>>>>>>
>>>>>>>
>>>> [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWor
>>>> kstation\Parameters]
>>>>>>> DWORD DomainCompatibilityMode 1
>>>>>>> DWORD DNSNameResolutionRequired 0
>>>>>>> DWORD RequireSecureNegotiate 0
>>>>>>>
>>>>>>> All three do not solve the problem.
>>>>>> If your other Win 8.1 client didn't require these changes,
>>>> it can't be
>>>>>> the cause on the other one. ;-)
>>>>>>
>>>>>> Registry changes are only required, if this is an NT4
>>>> domain - not an
>>>>>> AD. And it's only required for joining the NT4 domain:
>>>>>>
>> https://wiki.samba.org/index.php/Registry_changes_for_NT4-style_domains
>>>>>>
>>>>>>
>>>>>> But it's not that easy to help. You didn't gave much
>>>> information about
>>>>>> your environment.
>>>>>> * Is this a Member/PDC/DC/Standalone?
>>>>> The samba server is configured as standalone and should only
>>>> server as
>>>>> file server in a workgroup. The output of testparm -v can be
>>>> found here:
>>>>>        http://pastebin.com/gpvYTQcv
>>>>>
>>>>>
>>>>>> * DNS resolution on the client works?
>>>>> Which client do you mean?
>>>>> The failing Windows 8.1 client is able to resolve public
>>>> domains but not
>>>>> the hostname of the samba server to its IP.
>>>>>
>>>>>
>>>>>> * Errors in the logs?
>>>>> /var/log/samba/log.nmbd contains no errors and covers the
>> last three
>>>>> days incl. my tests from yesterday.
>>>>>
>>>>> /var/log/samba/log.smbd contains errors about CUPS which
>>>> where fixed by
>>>>> disabling print stuff at all using
>>>>>
>>>>>       printing = bsd
>>>>>       printcap name = /dev/null
>>>>>
>>>>>
>>>>>> * etc.
>>>>> What else could I provide?
>>>> How about the smb.conf that is on your machine, not 'testparm -v'
>>>>
>>>> Rowland
>>>>
>>>>>
>>>>>> Regards,
>>>>>> MArc
>>>>> Kind regards,
>>>>> Eike
>>>> -- 
>>>> To unsubscribe from this list go to the following URL and read the
>>>> instructions:  https://lists.samba.org/mailman/options/samba
>>>>
>> Hi Louis, from what I could extract from the OP's massive smb.conf
>> (before my eyes glazed over ;-) ), the machine is running as a
>> standalone workgroup server and isn't a member of a domain.
>>
>> Rowland
>> -- 
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/options/samba
>>
Until the OP posts the smb.conf he is using and just what 
authentication/security he wants, we are all just speculating.

Rowland