samba - Aug 2019 - 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

A (by MS recommended) workaround: 

- Click Start and type "services.msc" and right click on it and choose
"run as Administrator".

- Scroll through the list of services, then double click "Function
Discovery Provider Host (FDPHost)"
	this will bring up a new window. Next to the heading "Service Status"
it should say "Running"
	if it is not, then click the "Start" button. 
	Above that, set the "Startup type" to "Automatic
(Delayed)".

Do the same for the following services: 
- Function Discovery Resource Publication (FDResPub)
- Network Connections (NetMan)
- UPnP Device Host (UPnPHost) 
- Peer Name Resolution Protocol (PNRPSvc)
- Peer Networking Grouping (P2PSvc)
- Peer Networking Identity Manager (P2PIMSvc)

Repeat the same procedure for all PCs on the network.
Or even better, configure a GPO for it. 

When the changes have been made, reboot all PCs.
Finally, attempt to access your systems over the network using an UNC path using
File Explorer.

Now this is a workaround. 

If everthing is configured correctly, above is not needed! 
As in, i dont use it, i have set one important GPO settings, Wait for Network. 


Read also : 
https://support.microsoft.com/en-us/help/172218/microsoft-tcp-ip-host-name-resolution-order


Greetz, 

Louis

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

@Rowland - all the hosts / hostname changes made no difference - made all
changes and rebooted.

@Louis - The version is 1809.17763.253 and I believe this to be a windows 10
problem as well because this is not happening on Windows 7 machines on the
network.

I checked and the dns suffix is webb.local - see below:

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : webb.local
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::f9a2:1eec:771c:ab92%9(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.5.100(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Tuesday, August 13, 2019 7:20:02 AM
   Lease Expires . . . . . . . . . . : Friday, August 16, 2019 9:43:43 AM
   Default Gateway . . . . . . . . . : 192.168.5.254
   DHCP Server . . . . . . . . . . . : 192.168.5.254
   DHCPv6 IAID . . . . . . . . . . . : 158651445
   DNS Servers . . . . . . . . . . . : 192.168.5.160
   NetBIOS over Tcpip. . . . . . . . : Enabled

Notice the last line - I don't think NetBIOS is a good thing anymore right? 
I disabled it and right now I can access \\fs1 .  I'll have to see if it
stays working although it is also enabled on the Windows 7 machine that is
working.

Thanks, 
Rich

----- On Aug 12, 2019, at 1:53 PM, samba samba at lists.samba.org wrote:
> 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
> 
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba

Hai Rich, 

Your output of ipconfig /all

Where are these? 
Primary Dns Suffix  . . . . . . . :
DNS Suffix Search List. . . . . . :

This one is below in the output.  
Connection-specific DNS Suffix  . : 

Verify above again, if these 3 are all there and set to webb.local
Then try this : in you network settings, disable ipv6 
Beside ipv6 and the 2 missing outputs, i see the same here on my pc. 

DNS server 192.168.5.160 is one of your DC's ? 
And if you have more DC's, add the other also in the dhcp config. 

And Is dhcp option 015 DNS Domain Name set? 

Greetz, 

Louis

 
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Rich 
> Webb via samba
> Verzonden: dinsdag 13 augustus 2019 15:49
> Aan: samba
> Onderwerp: Re: [Samba] Windows cannot access \\server check 
> the spelling of the name 0x800704cf
> 
> @Rowland - all the hosts / hostname changes made no 
> difference - made all changes and rebooted. 
> 
> @Louis - The version is 1809.17763.253 and I believe this to 
> be a windows 10 problem as well because this is not happening 
> on Windows 7 machines on the network.  
> 
> I checked and the dns suffix is webb.local - see below:
> 
> Ethernet adapter Ethernet:
> 
>    Connection-specific DNS Suffix  . : webb.local
>    Description . . . . . . . . . . . : Realtek PCIe GBE 
> Family Controller
>    DHCP Enabled. . . . . . . . . . . : Yes
>    Autoconfiguration Enabled . . . . : Yes
>    Link-local IPv6 Address . . . . . : 
> fe80::f9a2:1eec:771c:ab92%9(Preferred)
>    IPv4 Address. . . . . . . . . . . : 192.168.5.100(Preferred)
>    Subnet Mask . . . . . . . . . . . : 255.255.255.0
>    Lease Obtained. . . . . . . . . . : Tuesday, August 13, 
> 2019 7:20:02 AM
>    Lease Expires . . . . . . . . . . : Friday, August 16, 
> 2019 9:43:43 AM
>    Default Gateway . . . . . . . . . : 192.168.5.254
>    DHCP Server . . . . . . . . . . . : 192.168.5.254
>    DHCPv6 IAID . . . . . . . . . . . : 158651445
>    DNS Servers . . . . . . . . . . . : 192.168.5.160
>    NetBIOS over Tcpip. . . . . . . . : Enabled
> 
> Notice the last line - I don't think NetBIOS is a good thing 
> anymore right?  I disabled it and right now I can access 
> \\fs1 .  I'll have to see if it stays working although it is 
> also enabled on the Windows 7 machine that is working.
> 
> Thanks, 
> Rich
> 
> ----- On Aug 12, 2019, at 1:53 PM, samba samba at lists.samba.org wrote:
> 
> > 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
> > 
> > --
> > To unsubscribe from this list go to the following URL and read the
> > instructions:  https://lists.samba.org/mailman/options/samba
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
> 
>