Client PC unable to reach shared directory on Server PC

Post your questions about SoftEther VPN software here. Please answer questions if you can afford.
Post Reply
prprprx
Posts: 20
Joined: Mon Feb 07, 2022 7:54 pm

Client PC unable to reach shared directory on Server PC

Post by prprprx » Mon Feb 07, 2022 8:18 pm

Using SoftEther of course, I have....

SERVER
Installed a VPN Server onto PC1, using the "Remote Access VPN Server" option in SoftEther, using the "Enable L2TP Server Function (L2TP over IPsec)" option. I have clicked on "Local Bridge Setting" and I have created a bridge (I assumed this was needed).

CLIENT
Installed a VPN Client onto PC2 (located in a separate office).

WHAT IS WORKING
I AM able to "connect" from PC2 to PC1. (The Status on PC2 says "connected".) So, this seems successful.

WHAT IS NOT WORKING
HOWEVER, PC1 is sharing a directory over the LAN, and I need PC2 to have access to this directory. I am trying to Map to this shared directory, but I do not find a way to do this. I have tried Browsing for the shared directory as I would on the LAN, but no success. I have tried typing in the directory path, but without success.

Any direction/thoughts/suggestions. Clearly I'm missing something here.

Thank you.

solo
Posts: 512
Joined: Sun Feb 14, 2021 10:31 am

Re: Client PC unable to reach shared directory on Server PC

Post by solo » Mon Feb 07, 2022 10:28 pm

Can you ping PC1 from PC2?
If yes, on PC2 do this mapping: net use x: \\192.168.y.z\share-name
- where 192.168.y.z is PC1's IP address
Is the 'x' drive letter browsable now?

prprprx
Posts: 20
Joined: Mon Feb 07, 2022 7:54 pm

Re: Client PC unable to reach shared directory on Server PC

Post by prprprx » Tue Feb 08, 2022 2:14 pm

solo, thank you so much for your help.

This morning I remembered that I need to set up port forwarding. I had forgotten that detail.

Still, thank you, solo, for your help.

prprprx
Posts: 20
Joined: Mon Feb 07, 2022 7:54 pm

Re: Client PC unable to reach shared directory on Server PC

Post by prprprx » Thu Feb 10, 2022 2:51 am

Okay, so I was wrong. I don't have the issue resolved.

And to answer solo's question, No, that command does not give me access to the shared folder on the server. Instead I get a "The network name cannot be found." message.

The Client PC IS getting an IP address assigned from the VPN Server. And a Default Gateway that is the VPN Server. And from the Client PC, I can ping the Default Gateway.

But I can't figure out how to get access to the shared folder on the VPN Server. Any thoughts would be appreciated.

prprprx
Posts: 20
Joined: Mon Feb 07, 2022 7:54 pm

Re: Client PC unable to reach shared directory on Server PC

Post by prprprx » Thu Feb 10, 2022 3:19 am

REINSTALLED SoftEther VPN Server so that I could document the steps I took....

Here are some details, for clarity:

SoftEther VPN Server / Bridge Easy Setup Screen (that comes up on first run)
... Remote Access VPN Server CHECKED
... Site-to-site VPN Server or VPN Bridge CHECKED
... ... VPN Server that Accepts Connection from Other Sites (Center) SELECTED

IPsec / L2TP / EtherIP / L2TPv3 Serer Settings Screen
... Enable L2TP Server Function (L2TP over IPsec) CHECKED
... Enable L2TP Server Function (Raw L2TP with No Encryptions) CHECKED
... Enable EtherIP / L2TPv3 over IPsec Server Function CHECKED
... an IPsec Pre-Shared Key was created (although I never use it anywhere)

VPN Azure Service Settings Screen
... Disable VPN Azure SELECTED

VPN Easy Setup Tasks Screen
... User was created
... Local Bridge was created

Other details:
... A User Name was created
... ... Auth Type: Password Authentication
... SecureNAT was Enabled

solo
Posts: 512
Joined: Sun Feb 14, 2021 10:31 am

Re: Client PC unable to reach shared directory on Server PC

Post by solo » Thu Feb 10, 2022 3:30 am

prprprx wrote:
Thu Feb 10, 2022 3:19 am
... Local Bridge was created
... SecureNAT was Enabled
There it is - the two options are mutually exclusive. Please disable SecureNAT, reconnect VPN client, and retry the ping/map I posted before.

If the problem persists, please post the output of "netstat -r" after VPN connection from both PC1 and PC2, and paste them as code.

prprprx
Posts: 20
Joined: Mon Feb 07, 2022 7:54 pm

Re: Client PC unable to reach shared directory on Server PC

Post by prprprx » Thu Feb 10, 2022 3:46 am

Thank you. Okay, I will do those things right now.

Question though, Isn't the SecureNAT where the "Virtual DHCP Server Functions" are, and don't I need those DHCP functions?

Still, I have disabled the SecureNAT.

Taking next steps you recommend. Will post in a few moments .......

prprprx
Posts: 20
Joined: Mon Feb 07, 2022 7:54 pm

Re: Client PC unable to reach shared directory on Server PC

Post by prprprx » Thu Feb 10, 2022 3:57 am

On PC2 (the Client PC), I'm not sure what IP address to use for the "net use x: \\192.168.y.z\share-name" command you suggest. .... ipconfig on PC2 gives me a 169.254.xxx.xxx IP address for the VPN adapter, and no Default gateway back to PC1. And if I try to ping PC1 from PC2 using PC1's local network IP, there's no success there.

Apologies for lack of knowledge here. Not sure how to proceed.

And, is it safe for me to post netstat -r ? There's a lot of info there.

Thank you!

prprprx
Posts: 20
Joined: Mon Feb 07, 2022 7:54 pm

Re: Client PC unable to reach shared directory on Server PC

Post by prprprx » Thu Feb 10, 2022 4:12 am

Here are the results of

Code: Select all

netstat -r
for both machines:

PC1 (Server)

Code: Select all

===========================================================================
Interface List
 16...84 a9 3e 72 2a ca ......Realtek PCIe GbE Family Controller
  7...ae d5 64 c9 2f 4d ......Microsoft Wi-Fi Direct Virtual Adapter #3
 20...ee d5 64 c9 2f 4d ......Microsoft Wi-Fi Direct Virtual Adapter #4
 10...ac d5 64 c9 2f 4d ......Realtek RTL8821CE 802.11ac PCIe Adapter
  5...ac d5 64 c9 2f 4e ......Bluetooth Device (Personal Area Network)
  1...........................Software Loopback Interface 1
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0         10.0.2.1       10.x.x.xxx     55
      10.xx.xx.xx    255.255.255.0         On-link        10.x.x.xxx    311
      10.xx.xx.xx  255.255.255.255         On-link        10.x.x.xxx    311
      10.xx.xx.xx  255.255.255.255         On-link        10.x.x.xxx    311
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    331
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    331
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    331
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    331
        224.0.0.0        240.0.0.0         On-link        10.x.x.xxx    311
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
  255.255.255.255  255.255.255.255         On-link        10.x.x.xxx    311
===========================================================================
Persistent Routes:
  None

PC2 (Client)

Code: Select all

===========================================================================
Interface List
  3...5e f4 e4 b7 74 be ......VPN Client Adapter - VPN
  5...50 81 40 75 cd df ......Realtek PCIe GbE Family Controller
 12...00 ff 67 f2 cb bd ......ExpressVPN TAP Adapter
  6...5e fb 3a 3e fc 01 ......Microsoft Wi-Fi Direct Virtual Adapter #3
 21...de fb 3a 3e fc 01 ......Microsoft Wi-Fi Direct Virtual Adapter #4
 11...5c fb 3a 3e fc 01 ......Realtek RTL8821CE 802.11ac PCIe Adapter
  8...5c fb 3a 3e fc 02 ......Bluetooth Device (Personal Area Network)
  1...........................Software Loopback Interface 1
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.0.1    192.168.0.108     35
      75.xx.xx.xx  255.255.255.255      192.168.0.1    192.168.0.108     35
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    331
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    331
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    331
     130.xx.xx.xx  255.255.255.255      192.168.0.1    192.168.0.108     35
      169.254.0.0      255.255.0.0         On-link    169.254.206.14    257
   169.254.206.14  255.255.255.255         On-link    169.254.206.14    257
  169.254.255.255  255.255.255.255         On-link    169.254.206.14    257
      192.168.0.0    255.255.255.0         On-link     192.168.0.108    291
    192.168.xx.xx  255.255.255.255         On-link     192.168.0.108    291
    192.168.0.255  255.255.255.255         On-link     192.168.0.108    291
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    331
        224.0.0.0        240.0.0.0         On-link    169.254.206.14    257
        224.0.0.0        240.0.0.0         On-link     192.168.0.108    291
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
  255.255.255.255  255.255.255.255         On-link    169.254.206.14    257
  255.255.255.255  255.255.255.255         On-link     192.168.0.108    291
===========================================================================
Persistent Routes:
  None

solo
Posts: 512
Joined: Sun Feb 14, 2021 10:31 am

Re: Client PC unable to reach shared directory on Server PC

Post by solo » Thu Feb 10, 2022 4:13 am

prprprx wrote:
Thu Feb 10, 2022 3:57 am
And, is it safe for me to post netstat -r ? There's a lot of info there.
No worries, do post, there is nothing privacy-exposing in it, here is mine:

Code: Select all

Route Table
===========================================================================
Interface List
0x2 ...8e 72 5c e8 91 33 ...... VPN Client Adapter - VPN
0x10005 ...3c 97 0e 39 e7 72 ...... Intel(R) 82579LM Gigabit Network Connection
0x20004 ...60 67 20 ac b6 a0 ...... Intel(R) Centrino(R) Advanced-N 6205
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.8.1   192.168.8.100       20
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
      192.168.8.0    255.255.255.0    192.168.8.100   192.168.8.100       20
    192.168.8.100  255.255.255.255        127.0.0.1       127.0.0.1       20
    192.168.8.255  255.255.255.255    192.168.8.100   192.168.8.100       20
        224.0.0.0        240.0.0.0    192.168.8.100   192.168.8.100       20
  255.255.255.255  255.255.255.255    192.168.8.100           10006       1
  255.255.255.255  255.255.255.255    192.168.8.100   192.168.8.100       1
  255.255.255.255  255.255.255.255    192.168.8.100           10005       1
  255.255.255.255  255.255.255.255    192.168.8.100               2       1
Default Gateway:       192.168.8.1
===========================================================================
Persistent Routes:
  None
But first perhaps reboot both units and re-check mapping again.

prprprx
Posts: 20
Joined: Mon Feb 07, 2022 7:54 pm

Re: Client PC unable to reach shared directory on Server PC

Post by prprprx » Thu Feb 10, 2022 4:17 am

.... Thanks. I'm sure you see that I posted them both above. .... Let me know if you'd like me to do something else. ..... Um, I don't believe I rebooted before posting, but can do that if you need me to.

Thank you, again.

solo
Posts: 512
Joined: Sun Feb 14, 2021 10:31 am

Re: Client PC unable to reach shared directory on Server PC

Post by solo » Thu Feb 10, 2022 4:37 am

please post the output of "netstat -r" after VPN connection
You posted client's netstat without the VPN connection.

prprprx
Posts: 20
Joined: Mon Feb 07, 2022 7:54 pm

Re: Client PC unable to reach shared directory on Server PC

Post by prprprx » Thu Feb 10, 2022 4:42 am

Um. Hmm. On PC2, I double-clicked the line in the SoftEther VPN Client Manager. The line says "Connected". Then I ran the netstat -r command and posted it.

Since then, I have rebooted both machines, and reconnected the VPN. The VPN Client Manager says "Status" "Connected". The netstat -r command looks the same to me.

prprprx
Posts: 20
Joined: Mon Feb 07, 2022 7:54 pm

Re: Client PC unable to reach shared directory on Server PC

Post by prprprx » Thu Feb 10, 2022 4:44 am

.... You're apparently not seeing something that you expect to be there.

.... Thoughts on what I should do, or what I should check?

solo
Posts: 512
Joined: Sun Feb 14, 2021 10:31 am

Re: Client PC unable to reach shared directory on Server PC

Post by solo » Thu Feb 10, 2022 5:03 am

As SecureNAT is now disabled, SE server's bridge should deliver via your LAN's DHCP a 10.0.2.x interface to the client. Perhaps you've no DHCP there and only use static IPs? Double-check the bridge's existence too.

EDIT
Did you bridge to "Realtek PCIe GbE Family Controller" or "Realtek RTL8821CE 802.11ac PCIe Adapter"?
Which one connects to the internet?

prprprx
Posts: 20
Joined: Mon Feb 07, 2022 7:54 pm

Re: Client PC unable to reach shared directory on Server PC

Post by prprprx » Thu Feb 10, 2022 5:21 am

On PC1, the server...
The Bridge is with "Realtek PCIe GbE Family Controller"

As for your other comments, I confess I'm sitting here thinking about them but uncertain how to proceed yet. But I'm here. I would really love to get this figured out tonight if possible. I'm so grateful for your input.

WOW. Perfect question! Which one has Internet. NOT the one I set up the bridge with.
The "Realtek RTL8821CE" is the one that has the Internet connection.
BUT, that one is not showing up in the "LAN Adapter" drop-down on the "Local Bridge Settings" screen on the PC1/VPN Server.

I have deleted the Bridge now with the wrong device.

The correct device still is not showing up in the "LAN Adapter" drop-down for me to choose it. What might cause that?
Last edited by prprprx on Thu Feb 10, 2022 5:30 am, edited 1 time in total.

solo
Posts: 512
Joined: Sun Feb 14, 2021 10:31 am

Re: Client PC unable to reach shared directory on Server PC

Post by solo » Thu Feb 10, 2022 5:29 am

No worries, we're getting there.
On PC1, the server... please post its "ipconfig /all"

prprprx
Posts: 20
Joined: Mon Feb 07, 2022 7:54 pm

Re: Client PC unable to reach shared directory on Server PC

Post by prprprx » Thu Feb 10, 2022 5:31 am

.... I made a few Edits to my last post. Dont' know if you saw them. ..... I'm about to post what you asked as well.

EDIT
I have now posted the results of ipconfig /all in the following post. Long posts seem to need a few moments to be approved by a monitor or something. But it's coming.
Last edited by prprprx on Thu Feb 10, 2022 5:37 am, edited 1 time in total.

prprprx
Posts: 20
Joined: Mon Feb 07, 2022 7:54 pm

Re: Client PC unable to reach shared directory on Server PC

Post by prprprx » Thu Feb 10, 2022 5:35 am

Code: Select all

C:\Users\tharr>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : DESKTOP-xxxx
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
   Physical Address. . . . . . . . . : 84-A9-3E-72-2A-CA
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 3:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #3
   Physical Address. . . . . . . . . : AE-D5-64-C9-2F-4D
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 4:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #4
   Physical Address. . . . . . . . . : EE-D5-64-C9-2F-4D
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek RTL8821CE 802.11ac PCIe Adapter
   Physical Address. . . . . . . . . : AC-D5-64-C9-2F-4D
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::391b:1d4a:31a2:ae77%10(Preferred)
   IPv4 Address. . . . . . . . . . . : 10.0.2.132(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.0.2.1
   DHCPv6 IAID . . . . . . . . . . . : 128767332
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-25-33-2A-E4-84-A9-3E-72-2A-CA
   DNS Servers . . . . . . . . . . . : 1.1.1.1
                                       1.0.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Bluetooth Network Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
   Physical Address. . . . . . . . . : AC-D5-64-C9-2F-4E
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

solo
Posts: 512
Joined: Sun Feb 14, 2021 10:31 am

Re: Client PC unable to reach shared directory on Server PC

Post by solo » Thu Feb 10, 2022 5:46 am

OK, thanks for the updates and edits, everything is clear now, read on...

SoftEther does not offer "Realtek RTL8821CE" bridge because this WiFi hardware does not support promiscuous mode. In this situation there are two options:

#1 turn off WiFi and connect with a LAN cable "Realtek PCIe GbE Family Controller" to your internet router

#2 ...will use it if the above is inconvenient :-)

prprprx
Posts: 20
Joined: Mon Feb 07, 2022 7:54 pm

Re: Client PC unable to reach shared directory on Server PC

Post by prprprx » Thu Feb 10, 2022 5:56 am

Wow. Great info.

Okay. Option #1 is definitely inconvenient, if even possible. The location is an hour's drive away, and due to setup there, not sure it's even possible to connect with a LAN cable.

Can we explore Option #2?

EDIT...
We still need to explore Option #2, but it's late where I'm at and I'm tired .. I momentarily confused the server / client physical locations .. the server is 20 mins away, but is in an office without a LAN jack in the wall. So, still not convenient. Hoping Option #2 is something we can do.

FYI, the Router-and-Switch equipment is Ubiquiti equipment, and I do have access to it from here in the event useful.

Thank you, again. I'm short on words for how grateful I am.

solo
Posts: 512
Joined: Sun Feb 14, 2021 10:31 am

Re: Client PC unable to reach shared directory on Server PC

Post by solo » Thu Feb 10, 2022 6:18 am

Sure, option #2...

On the server:
- remove the bridge
- enable SecureNAT (with all defaults as is)
- on the server run "ipconfig /all" and note "IPv4 Address" for the WiFi adapter (currently 10.0.2.132 but may change later)

On the client:
- connect VPN
- map using the above address: net use x: \\10.0.2.132\share-name
- browse 'x'

Note that SecureNAT is slower than a bridged connection and may be problematic for performance of the shared folder.

prprprx
Posts: 20
Joined: Mon Feb 07, 2022 7:54 pm

Re: Client PC unable to reach shared directory on Server PC

Post by prprprx » Thu Feb 10, 2022 6:33 am

Okay. Did all that. Still not quite there though.

On PC2 / the client, I CAN SUCCESSFULLY ping 10.0.2.132, however, the net use command results in this:

Code: Select all

C:\Users\innov>net use z: \\10.0.2.132\DESKTOP-8ASIBFL\Drake Programs
System error 67 has occurred.

The network name cannot be found.

prprprx
Posts: 20
Joined: Mon Feb 07, 2022 7:54 pm

Re: Client PC unable to reach shared directory on Server PC

Post by prprprx » Thu Feb 10, 2022 6:52 am

.... And just to confirm, No port forwarding is needed here? And why not?

solo
Posts: 512
Joined: Sun Feb 14, 2021 10:31 am

Re: Client PC unable to reach shared directory on Server PC

Post by solo » Thu Feb 10, 2022 6:59 am

prprprx wrote:
Thu Feb 10, 2022 6:52 am
.... And just to confirm, No port forwarding is needed here? And why not?
It seems that NAT-T does its job, so port forwarding is optional. As for the share error, it's simple: use quotes for share names with spaces, eg
net use z: "\\10.0.2.132\Drake Programs"

prprprx
Posts: 20
Joined: Mon Feb 07, 2022 7:54 pm

Re: Client PC unable to reach shared directory on Server PC

Post by prprprx » Thu Feb 10, 2022 7:09 am

Okay. Added the quotes. Thanks. (I spend my days on Linux and haven't used spaces in years for directory names. Windows is a little foreign to me. Sorry.)

I'm getting "Enter the user name for 10.0.2.132"

But in Windows on PC1, I turned off Password protected sharing. The workstations on the local LAN do not need a password to get to the share. Any thoughts? I feel like we're an inch away.

EDIT: And I've tried the server's username and password nonetheless, but isn't accepted.
EDIT: Have created a shared folder as well with no spaces. Still same result. Asks for a user name.

EDIT: My apologies! I had the username wrong (wasn't what I was given--I made a guess and it was something else instead). I typed in the correct username and password, and I've got the shared directory on the PC2 now. Wow.

SO,
1) Thank you for your COMMENT on how not using Bridged isn't going to be as performant or dependable. I'll get the LAN jack matter addressed.
2) Don't understand why user name/pw needed when that's turned off, but no big deal.
3) Thank you, thank you, thank you, Sir. Really, really. So very grateful for your time, knowledge, and patience. Excellent!!!
Last edited by prprprx on Thu Feb 10, 2022 7:24 am, edited 2 times in total.

solo
Posts: 512
Joined: Sun Feb 14, 2021 10:31 am

Re: Client PC unable to reach shared directory on Server PC

Post by solo » Thu Feb 10, 2022 7:19 am

On the shared folder:

- security: add "everyone" with full control
- sharing/advanced-sharing/permissions: make "everyone" with full control

Also, these must be undefined or allowed:
Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > Security Options >
- Network Security: Restrict NTLM: Outgoing NTLM traffic to remote server
- Network Security: Restrict NTLM: Incoming NTLM Traffic

EDIT
I see now that you got it working. In conclusion, SecureNAT in the context of Windows shares is the last resort not only because of performance issues but the above usability obstacles. With a bridged connection you'd use GUI share tools as usual, as if on the LAN directly.

Cheers!

prprprx
Posts: 20
Joined: Mon Feb 07, 2022 7:54 pm

Re: Client PC unable to reach shared directory on Server PC

Post by prprprx » Thu Feb 10, 2022 7:26 am

Okay!

With regard to the "undefined or allowed" note you made, I'm unfamiliar with where those are found but will look it up and take care of it.

Those are so as to avoid typing username/pw?? (Just confirming I'm on the same page as you.)

solo
Posts: 512
Joined: Sun Feb 14, 2021 10:31 am

Re: Client PC unable to reach shared directory on Server PC

Post by solo » Thu Feb 10, 2022 7:34 am

Yes, and check my edit above.

prprprx
Posts: 20
Joined: Mon Feb 07, 2022 7:54 pm

Re: Client PC unable to reach shared directory on Server PC

Post by prprprx » Thu Feb 10, 2022 7:38 am

Okay. I checked your edit/additional notes.

Thank you for everything. I've been stumbling on this for days. Thank you very, very much. Excellent!!! So grateful. Have a good evening/day.

prprprx
Posts: 20
Joined: Mon Feb 07, 2022 7:54 pm

Re: Client PC unable to reach shared directory on Server PC

Post by prprprx » Thu Feb 10, 2022 7:59 am

Sir, could I impose on you one last time please?

I am searching and searching but can't find "Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > Security Options"

This is a Windows 11 machine.

I keep landing on websites telling me to run "secpol.msc", but it doesn't seem to exist on the machine.

Where is this at, please?

EDIT: I found it! Nevermind.
Needed to run gpedit.msc, which doesn't exist on Windows 11 Home.
Found how to add it/enable it on the Internet.

Thank you again for everything !!

solo
Posts: 512
Joined: Sun Feb 14, 2021 10:31 am

Re: Client PC unable to reach shared directory on Server PC

Post by solo » Thu Feb 10, 2022 8:47 am

The policies' defaults are OK, so maybe don't worry about them.
More importantly, both server and client need to be in the same net 'workgroup'.
Finally, on the server run (and reboot?):

Code: Select all

reg ADD HKLM\SYSTEM\CurrentControlSet\Control\Lsa /v forceguest /t REG_DWORD /d 00000000 /f
reg ADD HKLM\SYSTEM\CurrentControlSet\Control\Lsa /v limitblankpassworduse /t REG_DWORD /d 00000000 /f
If or when you change over to a bridged server, undo the regs to improve security.

solo
Posts: 512
Joined: Sun Feb 14, 2021 10:31 am

Re: Client PC unable to reach shared directory on Server PC

Post by solo » Thu Feb 10, 2022 11:56 am

If you wish we could test out experimental bridge workarounds :-)

The first workaround requires a minor hardware mod. Simply connect the LAN adapter to something, like an old hub/switch, to simulate "Media connected". Then do the following:
- set static IP on the LAN adapter, eg 192.168.3.1 mask 255.255.255.0 DG/DNS irrelevant
- disable SecureNAT
- bridge the LAN adapter to your SE HUB
On the client:
- set static IP on the VPN adapter, eg 192.168.3.2 mask 255.255.255.0 DG/DNS irrelevant
- connect VPN
- verify ping 192.168.3.1
- try "Browsing for the shared directory as I would on the LAN" or "typing in the directory path"

The second workaround does not reqire any hardware intervention, only an extra software component. Install Microsoft Loopback Adapter and reboot the PC. Then do the following:
- set static IP on the MLA adapter, eg 192.168.3.1 mask 255.255.255.0 DG/DNS irrelevant
- disable SecureNAT
- bridge the MLA adapter to your SE HUB
On the client:
- set static IP on the VPN adapter, eg 192.168.3.2 mask 255.255.255.0 DG/DNS irrelevant
- connect VPN
- verify ping 192.168.3.1
- try "Browsing for the shared directory as I would on the LAN" or "typing in the directory path"

It should work just like on the LAN and without annoying share password prompts. The client will lose other internet access unless you uncheck "Use default gateway on remote network" in the VPN adapter's advanced properties.

Post Reply