samba - Aug 2019 - Windows cannot access \\server check the spelling of the name 0x800704cf

So then looking at my config files for both machines you see no problems there? 
I'm testing now, but I'm wondering if this is only happening on windows
10 clients.

Thanks, 
Rich

> Avahi is the usual problem if you use '.local' (which isn't
recommended
> any more), but the more I think about this, I begin to think this is a
> Windows problem.
> 
> Rowland
>

On 10/08/2019 16:22, Rich Webb via samba wrote:
> So then looking at my config files for both machines you see no problems
there?  I'm testing now, but I'm wondering if this is only happening on
windows 10 clients.
Searching on google with '0x800704cf share' brings up about 16,900
results

It looks like it is a common Windows problem.

Rowland

On 12/08/2019 14:18, Rich Webb wrote:
> I would agree except now it smells more like a DNS issue since when I try: 
\\fs1 I get the error but if I do \\fs1.webb.local then it works every time.
>
> I've checked my dns suffix settings and search domains and all is
correct.  Could there be an issue with the Samba 4 internal DNS server?
>
OK, lets check your settings, please post the contents of the following 
files:

/etc/hostname

/etc/hosts

/etc/resolv.conf

Also the output of these commands:

host -t A fs1

host -t A fs1.webb.local

They need to all come from both the DC and the filserver.

Rowland

Ps. 

Why UNC Paths Break with April Creators Update. (build 1803 April 2018) and
later.

! These builds 1804 are getting forced update to 1903.
(Tip: Avast antivirus users, remove Avast, and reinstall after if you pc keeps
crashing at 85%.)

The reason why the UNC paths won't resolve in Windows 10 April Creators
Update is because Microsoft has removed "SMB v1.0" and
"CIFS" services due to a critical bug that can allow for remote code
execution. In other words, hackers could take over your system. This bug was
discovered March 14, 2017 but it has taken Microsoft this long to issue a
"fix," which unfortunately breaks the network name resolution for a
lot of users.

It is possible to re-enable SMB v1.0 using Powershell, but due to the
vulnerability I highly recommend you do not and instead follow the fix described
next.

Now its in the list so everybody can find it ;-) 


Greetz, 

Louis

> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> L.P.H. van Belle via samba
> Verzonden: maandag 12 augustus 2019 16:21
> Aan: samba at lists.samba.org
> Onderwerp: Re: [Samba] Windows cannot access \\server check 
> the spelling of the name 0x800704cf
> 
> 
> 
> Windows 10? Then this is normal behaivor. 
> 
> 
> > -----Oorspronkelijk bericht-----
> > Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> > Rowland penny via samba
> > Verzonden: maandag 12 augustus 2019 15:50
> > Aan: sambalist
> > Onderwerp: Re: [Samba] Windows cannot access \\server check 
> > the spelling of the name 0x800704cf
> > 
> > On 12/08/2019 14:18, Rich Webb wrote:
> > > I would agree except now it smells more like a DNS issue 
> > since when I try:  \\fs1 I get the error but if I do 
> > \\fs1.webb.local then it works every time.
> > >
> > > I've checked my dns suffix settings and search domains and 
> > all is correct.  Could there be an issue with the Samba 4 
> > internal DNS server?
> 
> Rowland forgot to ask. 
> 
> The windows version?? 
> Because, Error code 0x800704cf: The network location cannot 
> be reached.  Is a windows error. 
> 
> If you can access \\server.FQDN and not \\server 
> 
> Start here: check if you firewall on the windows PC is set to 
> "Work network" 
> 
> Then what is set ? ( cmd : ipconfig /all ) 
> ?? 
> Primary Dns Suffix  . . . . . . . : ( should be the same as 
> on a linux server : hostname -d ) 
> DNS Suffix Search List. . . . . . : ( should be the same as 
> on a linux server : hostname -d ) 
> 
> If that is the case. ( same as hostname -d on linux ) 
> Then i suggest, you verify if you server also has its PTR 
> record configured. 
> 
> A few other options to check or what might be a problem here. 
> The IpStack is kaput. Run: : netsh int ip reset 
> 
> Or 
> Enable "Client for microsoft networks"
> - From the Network and Sharing Center click Change Adapter Settings
> - Right Click on Adapter >> Select Properties
> - Check if "Client For Microsoft Networks" is installed? If not;
> - Click Install
> - Double-Click Clients
> - Choose Client for Microsoft Networks
> - Click Ok >> OK
> - Restart the computer
> 
> 
> 
> Greetz, 
> 
> Louis
> 
> 
> 
> 
> 
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
> 
>

>From FS1 (file server):
#> cat /etc/hostname
fs1.webb.local

#> cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.5.161   fs1.webb.local  fs1

#> cat /etc/resolv.conf
# Generated by NetworkManager
search webb.local
nameserver 192.168.5.160

#> host -t A fs1
fs1.webb.local has address 192.168.5.161

#> host -t A fs1.webb.local
fs1.webb.local has address 192.168.5.161
---------------------------------------------------------
>From DC2 (domain controller)
#> cat /etc/hostname
dc2.webb.local

#> cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

#> cat /etc/resolv.conf
# Generated by NetworkManager
search webb.local
nameserver 192.168.5.160

#> host -t A fs1
fs1.webb.local has address 192.168.5.161

#> host -t A fs1.webb.local
fs1.webb.local has address 192.168.5.161

Thanks, 
Rich

----- On Aug 12, 2019, at 9:50 AM, samba samba at lists.samba.org wrote:
> On 12/08/2019 14:18, Rich Webb wrote:
>> I would agree except now it smells more like a DNS issue since when I
try:
>> \\fs1 I get the error but if I do \\fs1.webb.local then it works every
time.
>>
>> I've checked my dns suffix settings and search domains and all is
correct.
>> Could there be an issue with the Samba 4 internal DNS server?
>>
> OK, lets check your settings, please post the contents of the following
> files:
> 
> /etc/hostname
> 
> /etc/hosts
> 
> /etc/resolv.conf
> 
> Also the output of these commands:
> 
> host -t A fs1
> 
> host -t A fs1.webb.local
> 
> They need to all come from both the DC and the filserver.
> 
> Rowland
> 
> 
> 
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba