[Samba] Windows cannot access \\server check the spelling of the name 0x800704cf

[Rich Webb]

Thanks Louis for the reply.

I will have to check the version when I get home but I *believe* it's 1809.  I have several windows 10 partitions with a multi-boot manager on my various drives that I use for different things and they all seem to exhibit this behavior.  I haven't tried this in Windows 7 which I also have.  

I have a firewall on my internet connection so I have the Windows Firewall disabled on all my internal computers.  It just causes issues and usually when I need to remotely access something across a vpn when I'm 1000s of miles away from my network. 

Client for MS networks is there and I will have to check again but the dns suffix I checked before and it was set correctly (to webb.local)

I'm guessing it's not the IP stack but I could be wrong. I only say that because it's happening on all my Windows 10 partitions.  Now if the source IP stack is gone (the one I cloned the partitions from) then that would make sense and is possible. 

Thanks, 
Rich
----- On Aug 12, 2019, at 10:20 AM, samba samba at lists.samba.org wrote:

> 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