Shared folders not accessable using file folder sharing after update?

jkirkman44 · 14 Sep 2018

Dear Forum,

I like to consider myself pretty tech savvy, and knowledgeable in Windows 10 settings etc. But I am absolutely stumped on this issue. My File & Folder sharing is no longer accessible or even broadcasts over my home private Wi-Fi network, and it was working fine until Microsoft installed updates, just not sure which update. I have double checked advanced file sharing settings and they are set correctly, and the proper services are running to enable sharing. It even shows folder under Network in file explorer. I have done system restore 3 times, and literally done everything but reset the operating system which is Windows 10 Home v1803 Build: 17134.185. I have attached the Wlan Report, Network Diag Report, and Incoming Connection diag report. Please help???

Eagle51 · 14 Sep 2018

Hey jkirkman44,
It would help to know the error your getting when trying to connect to the share, but it looks like it's a Share & NTFS Permission issue. You probably need to add Everyone with Full Access to both the Share & NTFS Permissions.

See this tutorial - Share Files and Folders Over a Network in Windows 10 | Windows 10 Tutorials

jkirkman44 · 14 Sep 2018

It does not give me an error. Upon running shared folder troubleshooter it says " can not connect to remote source"?

Eagle51 · 14 Sep 2018

It does not give me an error. Upon running shared folder troubleshooter it says " can not connect to remote source"?

Hmmm ... when you try to access the share and it fails ... usually there is a network error box that pops up like this and if you hit "Show Details" it gives you the error code.

Shared folders not accessable using file folder sharing after update?-13180_1.png

jkirkman44 · 14 Sep 2018

Shared folders not accessable using file folder sharing after update?-screenshot-240-.png

Error 0x80070035

Eagle51 · 15 Sep 2018

Hey jkirkman44,
1. Are you using any 3rd party Firewalll ?
2. Can you access KIRKNET-PEOC by it's IPADDRESS ?
Example:
File Explorer > Address Bar > \\192.168.1.5

IF you can access it by the IPADDRESS, then it's an issue people are seeing with Win10(1803) and accessing network shares by PCNAME ... People have had varying success using one of the following ...

1. Disable IPv6 - Enable or Disable IPv6 in Windows | Windows 10 Tutorials
Note: If you prefer NOT to disable IPV6, you can use the Prefer IPv4 over IPv6 - https://support.microsoft.com/en-us/...advanced-users
2. Rename PC's - Change Computer Name in Windows 10 | Windows 10 Tutorials

IF you use Static IPs you can try one of these ...

1. Map a Network Drive - Map Network Drive in Windows 10 | Windows 10 Tutorials
2. Hosts File - Edit Hosts file on ALL your PC's and Map IP to PCNAME.
Example:
192.168.1.5 KIRKNET-PEOC
192.168.1.6 MYOTHER-PC

jkirkman44 · 15 Sep 2018

The system failed to register host (A or AAAA) resource records (RRs) for network adapter
with settings:

Adapter Name : {1081FD34-955B-42E6-934A-F574996B76BF}
Host Name : KIRKNET-PEOC
Primary Domain Suffix : home
DNS server list :
192.168.1.1
Sent update to server : <?>
IP Address(es) :
2605:a000:1803:8000:0:4923:eb79:9c54, 192.168.1.100

The reason the system could not register these RRs was because the DNS server failed the update request. The most likely cause of this is that the authoritative DNS server required to process this update request has a lock in place on the zone, probably because a zone transfer is in progress.

You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator

The system failed to register host (A or AAAA) resource records (RRs) for network adapter
with settings:

Adapter Name : {1081FD34-955B-42E6-934A-F574996B76BF}
Host Name : KIRKNET-PEOC
Primary Domain Suffix : home
DNS server list :
192.168.1.1
Sent update to server : <?>
IP Address(es) :
192.168.1.100

The reason the system could not register these RRs was because the DNS server failed the update request. The most likely cause of this is that the authoritative DNS server required to process this update request has a lock in place on the zone, probably because a zone transfer is in progress.

You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator.

jkirkman44 · 15 Sep 2018

The system failed to register host (A or AAAA) resource records (RRs) for network adapter
with settings:

Adapter Name : {1081FD34-955B-42E6-934A-F574996B76BF}
Host Name : KIRKNET-PEOC
Primary Domain Suffix : home
DNS server list :
192.168.1.1
Sent update to server : <?>
IP Address(es) :
2605:a000:1803:8000:0:4923:eb79:9c54, 192.168.1.100

The reason the system could not register these RRs was because the DNS server failed the update request. The most likely cause of this is that the authoritative DNS server required to process this update request has a lock in place on the zone, probably because a zone transfer is in progress.

You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator.

Name resolution for the name go.trouter.io timed out after none of the configured DNS servers responded.

The IP address lease 192.168.1.9 for the Network Card with network address 0xF20194E9C209 has been denied by the DHCP server 192.168.1.1 (The DHCP Server sent a DHCPNACK message).

Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 0x26C246F51149. The following error occurred: 0x79. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server
ipconfig /allindows IP Configuration

Host Name . . . . . . . . . . . . : KIRKNET-PEOC
Primary Dns Suffix . . . . . . . : home
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : home

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
Physical Address. . . . . . . . . : AC-E2-D3-3F-6C-98
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 10:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 28-C6-3F-DF-F8-05
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter KIRKNET-PEOC Wi-Fi:

Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 3168
Physical Address. . . . . . . . . : F2-01-94-E9-C2-09
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2605:a000:1803:8000:0:4923:eb79:9c54(Preferred)
Lease Obtained. . . . . . . . . . : Saturday, September 15, 2018 8:47:49 PM
Lease Expires . . . . . . . . . . : Saturday, September 22, 2018 10:59:04 AM
Link-local IPv6 Address . . . . . : fe80::9807:5e9b:3426:a992%4(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Saturday, September 15, 2018 8:47:47 PM
Lease Expires . . . . . . . . . . : Tuesday, September 18, 2018 10:35:08 PM
Default Gateway . . . . . . . . . : fe80::78a5:ecff:fe65:984a%4
192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 82968980
DHCPv6 Client DUID. . . . . . . . : 00-03-00-01-F2-01-94-E9-C2-09
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Disabled
Connection-specific DNS Suffix Search List :
home

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 28-C6-3F-DF-F8-08
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Network Adapter Details

Connection-specific DNS Suffix: home
Description: Intel(R) Dual Band Wireless-AC 3168
Physical Address: ‎F2-01-94-E9-C2-09
DHCP Enabled: Yes
IPv4 Address: 192.168.1.100
IPv4 Subnet Mask: 255.255.255.0
Lease Obtained: Saturday, September 15, 2018 8:47:47 PM
Lease Expires: Tuesday, September 18, 2018 10:35:08 PM
IPv4 Default Gateway: 192.168.1.1
IPv4 DHCP Server: 192.168.1.1
IPv4 DNS Server: 192.168.1.1
IPv4 WINS Server:
NetBIOS over Tcpip Enabled: No
IPv6 Address: 2605:a000:1803:8000:0:4923:eb79:9c54
Lease Obtained: Saturday, September 15, 2018 8:47:49 PM
Lease Expires: Saturday, September 22, 2018 10:59:04 AM
Link-local IPv6 Address: fe80::9807:5e9b:3426:a992%4
IPv6 Default Gateway: fe80::78a5:ecff:fe65:984a%4
IPv6 DNS Server:

Eagle51 · 16 Sep 2018

Is there a reason you have ... NetBIOS over Tcpip Enabled: No .. It should be set to default.

Check your IPv4 settings ...
Control Panel > Network and Sharing Center > Change Adapter Settings Right Click on your network connection > Properties > Internet Protocol Version 4 TCP/IPv4 > Properties > General > Advanced

WINS Tab

Shared folders not accessable using file folder sharing after update?-wins.png

DNS Tab

Shared folders not accessable using file folder sharing after update?-dns.png

I see you have IPv6 setup ...

Does your ISP support IPv6 and do you actually use it ?

If not you can Disable IPv6 - Enable or Disable IPv6 in Windows | Windows 10 Tutorials

If it does and you want to use it ... you might want to check your router and make sure the IPv6 is setup correctly.

Note:
1. My ISP does support IPv6 and I have it setup in my router.
I use Googles DNS Servers for both.
The Google Public DNS IP addresses (IPv4) are as follows:

8.8.8.8
8.8.4.4

The Google Public DNS IPv6 addresses are as follows:

2001:4860:4860::8888
2001:4860:4860::8844

2. On my Netgear router for IP Assignment ... I have to use Auto Config vs Use DHCP Server so that my actual IPv6 address isn't shown (which can reveal unwanted information) and it uses a Temporary IPv6 address. You can check your IPv6 here - Test your IPv6.

jkirkman44 · 16 Sep 2018

Test IPv4 DNS records
Success (0.837s) Use ipv4
Testing IPv6 DNS records
Fail (0.175s)
Testing dual stack DNS records
Success (0.644s) Use ipv4
Dual stack DNS and large packet testing
Success (0.647s) Use ipv4
IPv4 without DNS
Omitted (0.280s)
Testing IPv6 Without DNS
Omitted (0.026s)
IPv6 Large Packet Test
Failure (0.204s)
Test if IPv6 is used on your ISP's DNS server
Failure (3.463s)
Finding an IPv4 Service Provider
Using success (0.753s) ipv4 ASN 10796
Finding an IPv6 service provider
Failure (0.245s)

Ipv6 Status Using Powershell

Local Area Connection* 11 Internet Protocol Version 6 (TCP/IPv6) ms_tcpip6 True
Bluetooth Network Connection Internet Protocol Version 6 (TCP/IPv6) ms_tcpip6 True
Ethernet Internet Protocol Version 6 (TCP/IPv6) ms_tcpip6 True
KIRKNET-PEOC Wi-Fi Internet Protocol Version 6 (TCP/IPv6) ms_tcpip6 True

Shared folders not accessable using file folder sharing after update?

Shared folders not accessable using file folder sharing after update?

Error Code

Event LOg Entries RE: DNS Client?? Clue???

Ipv6 Status Report Using Ipv6 test results