Solved Can't access Administrative Shares

perdrix · Dec 14, 2022

I'm been trying to connect to the normal Administrative Shares on my Windows 11 system from a Windows 10 system. I tried to connect to:

\\Apollo\C$

I get a timeout eventually. I am able to connect to the admin shares on the W10 system from the W11 system.
I did load the classic registry set:

Windows Registry Editor Version 5.00

Code:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"LocalAccountTokenFilterPolicy"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters]
"AutoShareWks"=dword:00000001
"AutoShareServer"=dword:00000001

But that didn't change a thing

Did the admin shares get abolished in W11?

FreeBooter · Dec 14, 2022

Why add those registry values, delete them and reboot your computer, execute net share command from Admin Command Prompt to view all shares on Windows 11.

perdrix · Dec 14, 2022

Without deleting those registry entries which were needed on W10 to enable admin shares:

Code:

C:\Windows\System32>net share

Share name   Resource                        Remark

-------------------------------------------------------------------------------
C$           C:\                             Default share
D$           D:\                             Default share
IPC$                                         Remote IPC
ADMIN$       C:\WINDOWS                      Remote Admin
The command completed successfully.

So the shares are apparently present but I cannot access them from W10.

I will remove those entries and reboot and report back.

Bree · Dec 14, 2022

perdrix said:
...the shares are apparently present but I cannot access them from W10.

See if this helps....

Solved!
I had to turn on "Enable insecure guest logons", as described here.
Apparently it's required on 22H2, but not on 20H2.

22H2 can't access network shares of 20H2 - Windows 10 Help Forums - post #4

perdrix · Dec 14, 2022

Hmm deleting those entries didn't change the output of net share:

Code:

net share

Share name   Resource                        Remark

-------------------------------------------------------------------------------
C$           C:\                             Default share
D$           D:\                             Default share
IPC$                                         Remote IPC
ADMIN$       C:\WINDOWS                      Remote Admin
The command completed successfully.

perdrix · Dec 14, 2022

And here's what I get on the W10 machine:

Userids and passwords are the same, workgroup name is DEVELOPMENT for both if it weren't I couldn't access the shares of the W10 system from W11).This will of course turn out to be something amazingly simple!

FWIW the W10 machine is 21H2.

OAT · Dec 14, 2022

Can you go to your command prompt and ping your Appolo machine?

perdrix · Dec 14, 2022

perdrix · Dec 14, 2022

Windows firewall on the W11 side is set to allow File Sharing for the network (which is a private one).

D.

FreeBooter · Dec 14, 2022

OAT said:
Can you go to your command prompt and ping your Appolo machine?

As suggested use Ping command to check if Windows 10 can see the shares.

Also execute net view \\ComputerName /ALL command. This command displays a list of domains, computers, or resources that are being shared by the specified computer. Used without parameters, net view displays a list of computers in your current domain.

perdrix · Dec 14, 2022

Code:

C:\Users\amonra>ping apollo

Pinging Apollo.local [fe80::c18f:c362:c3e0:cc30%5] with 32 bytes of data:
Reply from fe80::c18f:c362:c3e0:cc30%5: time<1ms
Reply from fe80::c18f:c362:c3e0:cc30%5: time<1ms
Reply from fe80::c18f:c362:c3e0:cc30%5: time<1ms
Reply from fe80::c18f:c362:c3e0:cc30%5: time<1ms

Ping statistics for fe80::c18f:c362:c3e0:cc30%5:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Users\amonra>net view \\charon
Shared resources at \\charon

charon server (Samba, Ubuntu)

Share name  Type  Used as  Comment

-------------------------------------------------------------------------------
Shared      Disk
The command completed successfully.


C:\Users\amonra>net view \\apollo
System error 53 has occurred.

The network path was not found.

FreeBooter · Dec 14, 2022

To resolve this problem, make sure File and Printer Sharing is enabled on Windows 11.

Share a printer as a network printer - Microsoft Support

Learn how to share a printer between a primary Windows device and secondary Windows devices on a network.

support.microsoft.com

cereberus · Dec 15, 2022

FreeBooter said:
To resolve this problem, make sure File and Printer Sharing is enabled on Windows 11.

Share a printer as a network printer - Microsoft Support

Learn how to share a printer between a primary Windows device and secondary Windows devices on a network.

support.microsoft.com

Also, when I did this ages ago, I seem to remember you had to have same account and password credentials on remote pc as on host. Also at back of my mind, you had to enable smb.

It is just easier to setup your own shares.

perdrix · Dec 15, 2022

It is enabled and user/password are the same

FreeBooter · Dec 15, 2022

cereberus said:
Also, when I did this ages ago, I seem to remember you had to have same account and password credentials on remote pc as on host. Also at back of my mind, you had to enable smb.

It is just easier to setup your own shares.

@cereberus, have a good idea, try connecting to share you have setup just to make sure its only hidden shares that you are problem connecting.

perdrix · Dec 15, 2022

Did that, still get:

Code:

C:\Users\amonra>net view \\apollo
System error 53 has occurred.

The network path was not found.

FreeBooter · Dec 15, 2022

Top 7 Ways to Fix Windows 11 Can't Access Shared Folder

Unable to access the shared folder on Windows 11? Check out this troubleshooting guide to fix issues with the shared folder on Windows 11.

www.guidingtech.com

perdrix · Dec 15, 2022

"Top 7 Ways ... got me nowhere I fear.

Attached pdf shows what wireshark has to say on the W10 system

perdrix · Dec 15, 2022

Firewall logging of dropped packets shows:

Code:

#Version: 1.5
#Software: Microsoft Windows Firewall
#Time Format: Local
#Fields: date time action protocol src-ip dst-ip src-port dst-port size tcpflags tcpsyn tcpack tcpwin icmptype icmpcode info path pid

                                                                                                                                                                                                                    2022-12-15 15:34:43 DROP UDP 192.168.129.1 192.168.129.255 138 138 237 - - - - - - - RECEIVE 4
2022-12-15 15:34:43 DROP UDP 192.168.129.1 192.168.129.255 138 138 242 - - - - - - - RECEIVE 4
2022-12-15 15:34:44 DROP TCP 192.168.129.119 192.168.129.82 63887 445 52 S 3658297995 0 64240 - - - RECEIVE 4
2022-12-15 15:34:45 DROP TCP 192.168.129.119 192.168.129.82 63887 445 52 S 3658297995 0 64240 - - - RECEIVE 4
2022-12-15 15:34:45 DROP TCP 192.168.129.119 192.168.129.82 63888 139 52 S 3833053951 0 64240 - - - RECEIVE 4
2022-12-15 15:34:46 DROP TCP 192.168.129.119 192.168.129.82 63888 139 52 S 3833053951 0 64240 - - - RECEIVE 4
2022-12-15 15:34:47 DROP TCP 192.168.129.119 192.168.129.82 63887 445 52 S 3658297995 0 64240 - - - RECEIVE 4
2022-12-15 15:34:49 DROP TCP 192.168.129.119 192.168.129.82 63888 139 52 S 3833053951 0 64240 - - - RECEIVE 4
2022-12-15 15:34:51 DROP TCP 192.168.129.119 192.168.129.82 63887 445 52 S 3658297995 0 64240 - - - RECEIVE 4
2022-12-15 15:34:53 DROP TCP 192.168.129.119 192.168.129.82 63888 139 52 S 3833053951 0 64240 - - - RECEIVE 4
2022-12-15 15:34:59 DROP TCP 192.168.129.119 192.168.129.82 63887 445 52 S 3658297995 0 64240 - - - RECEIVE 4
2022-12-15 15:35:01 DROP TCP 192.168.129.119 192.168.129.82 63888 139 52 S 3833053951 0 64240 - - - RECEIVE 4
2022-12-15 15:35:07 DROP UDP 192.168.129.119 192.168.129.255 137 137 78 - - - - - - - RECEIVE 4
2022-12-15 15:35:07 DROP TCP 192.168.129.119 192.168.129.82 63898 139 52 S 3281114501 0 64240 - - - RECEIVE 4
2022-12-15 15:35:08 DROP TCP 192.168.129.119 192.168.129.82 63898 139 52 S 3281114501 0 64240 - - - RECEIVE 4
2022-12-15 15:35:10 DROP TCP 192.168.129.119 192.168.129.82 63898 139 52 S 3281114501 0 64240 - - - RECEIVE 4
2022-12-15 15:35:14 DROP TCP 192.168.129.119 192.168.129.82 63898 139 52 S 3281114501 0 64240 - - - RECEIVE 4
2022-12-15 15:35:22 DROP TCP 192.168.129.119 192.168.129.82 63898 139 52 S 3281114501 0 64240 - - - RECEIVE 4
2022-12-15 15:38:14 DROP UDP 192.168.129.101 192.168.129.255 138 138 238 - - - - - - - RECEIVE 4
2022-12-15 15:38:14 DROP UDP 192.168.129.101 192.168.129.255 138 138 238 - - - - - - - RECEIVE 4

What I don't understand is WHY:

cereberus · Dec 15, 2022

FreeBooter said:
@cereberus, have a good idea, try connecting to share you have setup just to make sure its only hidden shares that you are problem connecting.

Well, I have no issues as I know how to set shares up. I never use the admin share as they were always a bit hit or miss.

Solved Can't access Administrative Shares

Active member

My Computer

Well-known member

My Computer

Active member

My Computer

Well-known member

My Computers

Active member

My Computer

Active member

My Computer

Pragmatic Member

My Computers

Active member

My Computer

Active member

My Computer

Well-known member

My Computer

Active member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Active member

My Computer

Well-known member

My Computer

Active member

My Computer

Well-known member

My Computer

Active member

Attachments

My Computer

Active member

My Computer

Well-known member

My Computer

Similar threads