I'm also having this identical issue, and I'm suspecting it's related to Hyper V Virtual Switches. My other Windows 11 machines don't have this issue; only the one with Hyper V hosting enabled does.
net use stopped working April 17, 2025 for no reason - System error 67
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
* UNABLE TO UPLOAD IMAGES TO THIS QUESTION VIA EDGE OR FIREFOX * URGH!! - makes it difficult to share details - SIGH!
The issue ...
Cannot access NAS via smb shares on a server on only one laptop - all other computers (windows and chrome books) remain able to access shares without issue. On the windows 11 pro laptop the following errors occur. The shares worked prior to April 17, 2025 at 10 am EST. Now they do not.
C:\Windows\System32>net use X: \192.168.68.112\SSD /user:mysmbuser mysmbpasswd
System error 67 has occurred.
The network name cannot be found.
C:\Windows\System32>net use X: \raspberrypi\SSD /user:mysmbuser mysmbpasswd
System error 67 has occurred.
The network name cannot be found.
PS C:\WINDOWS\system32> New-PSDrive -Name X -PSProvider FileSystem -Root \192.168.68.112\SSD -Credential (Get-Credential)
cmdlet Get-Credential at command pipeline position 1
Supply values for the following parameters:
New-PSDrive : The network name cannot be found
At line:1 char:1
+ New-PSDrive -Name X -PSProvider FileSystem -Root \192.168.68.112\SSD ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (X:PSDriveInfo) [New-PSDrive], Win32Exception
+ FullyQualifiedErrorId : CouldNotMapNetworkDrive,Microsoft.PowerShell.Commands.NewPSDriveCommand
I have a Windows 11 Pro laptop which sudden stopped being able to see network shares attached to a raspberry pi. No Windows Update or software changes that I am aware of preceded the sudden failure. The laptop has been able to see the shares for months without issue. The network shares are via samba on a raspberry pi. I have another windows 10 laptop as well as a google chrome laptop which have no difficulty seeing and accessing the network shares on the raspberry pi and continue to be able to do so without issue. I have read many forums to try to resolve this issue. I have followed all of the guidance provided.
* Disabled Hardening UNC path
* Updated network drivers - all did not require updating - full updated as is the operating system
* I do not have IP NAT so could not disable it in device manager
* I have done a windows reset and and had windows rescue install the rescue version of the latest windows - didn't help
What I can do
PS C:\WINDOWS\system32> Test-NetConnection -ComputerName 192.168.68.112 -InformationLevel "Detailed" -Port 445
ComputerName : 192.168.68.112
RemoteAddress : 192.168.68.112
RemotePort : 445
NameResolutionResults : 192.168.68.112
MatchingIPsecRules :
NetworkIsolationContext : Private Network
InterfaceAlias : Ethernet 2
SourceAddress : 192.168.68.114
NetRoute (NextHop) : 0.0.0.0
TcpTestSucceeded : True
PS C:\WINDOWS\system32> Test-NetConnection -ComputerName 192.168.68.112 -InformationLevel "Detailed" -Port 139
ComputerName : 192.168.68.112
RemoteAddress : 192.168.68.112
RemotePort : 139
NameResolutionResults : 192.168.68.112
MatchingIPsecRules :
NetworkIsolationContext : Private Network
InterfaceAlias : Ethernet 2
SourceAddress : 192.168.68.114
NetRoute (NextHop) : 0.0.0.0
TcpTestSucceeded : True
Running tcpdump listening to port 139 and port 445 on the raspberry pi I can see the network traffic so traffic is not blocked and all firewall access is open
The hosts file on windows laptop has an entry for the ip address of the raspberry pi so ping and tracert work without issue.
C:\Windows\System32> ping raspberrypi
Pinging raspberrypi [192.168.68.112] with 32 bytes of data:
Reply from 192.168.68.112: bytes=32 time<1ms TTL=64
Reply from 192.168.68.112: bytes=32 time<1ms TTL=64
Reply from 192.168.68.112: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.68.112:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Windows\System32>tracert raspberrypi
Tracing route to raspberrypi [192.168.68.112]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms raspberrypi [192.168.68.112]
Trace complete.
The issue persists whether I use WIFI or Ethenet. The ethernet adapter
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : ASIX USB to Gigabit Ethernet Family Adapter
Physical Address. . . . . . . . . : E4-B9-7A-E0-F8-C4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.68.114(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : April 18, 2025 8:56:41 AM
Lease Expires . . . . . . . . . . : April 18, 2025 11:56:52 AM
Default Gateway . . . . . . . . . : 192.168.68.1
DHCP Server . . . . . . . . . . . : 192.168.68.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
207.164.234.193
NetBIOS over Tcpip. . . . . . . . : Enabled
The network itself is a deco mesh attached to a bell wan router. As all other devices on the network remain able to access the NAS via the raspberry pi and can see the network shares, the network itself is not the issue. It is something specific to the Windows 11 Pro laptop. Details below - note the issue persists whether the VPN I have installed is engaged or not or stopped completely. All the NAS shares were all working with the VPN prior to yesterday morning without issue as well as when the VPN is turned off.
Have done a full virus scan as well and no issue.
Host Name: DESKTOP-NHGKVFR
OS Name: Microsoft Windows 11 Pro
OS Version: 10.0.22631 N/A Build 22631
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
Registered Owner: ***********@gmail.com
Registered Organization: N/A
Product ID: 00330-81486-80827-*****
Original Install Date: 2025-04-18, 12:46:32 AM
System Boot Time: 2025-04-18, 11:09:05 AM
System Manufacturer: Dell Inc.
System Model: XPS 15 9570
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 158 Stepping 10 GenuineIntel ~2904 Mhz
BIOS Version: Dell Inc. 1.27.0, 2022-08-12
Windows Directory: C:\WINDOWS
System Directory: C:\WINDOWS\system32
Boot Device: \Device\HarddiskVolume1
System Locale: en-us;English (United States)
Input Locale: en-us;English (United States)
Time Zone: (UTC-05:00) Eastern Time (US & Canada)
Total Physical Memory: 32,502 MB
Available Physical Memory: 21,649 MB
Virtual Memory: Max Size: 37,366 MB
Virtual Memory: Available: 24,925 MB
Virtual Memory: In Use: 12,441 MB
Page File Location(s): C:\pagefile.sys
Domain: WORKGROUP
Logon Server: \DESKTOP-NHGKVFR
Hotfix(s): 4 Hotfix(s) Installed.
[01]: KB5054980
[02]: KB5027397
[03]: KB5055528
[04]: KB5053665
Network Card(s): 6 NIC(s) Installed.
[01]: ASIX USB to Gigabit Ethernet Family Adapter
Connection Name: Ethernet 2
DHCP Enabled: Yes
DHCP Server: 192.168.68.1
IP address(es)
[01]: 192.168.68.114
[02]: Killer Wireless-n/a/ac 1535 Wireless Network Adapter
Connection Name: Wi-Fi
Status: Media disconnected
[03]: OpenVPN Data Channel Offload
Connection Name: OpenVPN Data Channel Offload for NordVPN
Status: Media disconnected
[04]: TAP-NordVPN Windows Adapter V9
Connection Name: Local Area Connection
Status: Media disconnected
[05]: Bluetooth Device (Personal Area Network)
Connection Name: Bluetooth Network Connection
Status: Media disconnected
[06]: WireGuard Tunnel
Connection Name: NordLynx
DHCP Enabled: No
IP address(es)
[01]: 10.5.0.2
[02]: fe80::723e:7ca:789d:a5aa
Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.
In reading this post: https://cordero.me/windows-unc-access-to-share-ports-smb/ I understand that the flow is as follows:
* DNS Query
* SMB Negotiation
* SMD Session
As I can see traffic on both port 139 and port 445, that is not the issue
I have tried to turning on SMB1 (restarting computer) etc ... no help ... turned off the SMB1
I believe it is something to do with the DNS query step in the process of setting up the connection to the share on the windows 11 pro laptop. As I have an entry in the HOSTS file which resolves without issue for ping and tracert I am not sure why it would not resolve for net use. The issue persists when using the ip address directly so no DNS should be required!!! So confused!
Here is the SMB details from the windows 11 pro laptop
PS C:\WINDOWS\system32> Get-SmbServerConfiguration
AnnounceComment :
AnnounceServer : False
AsynchronousCredits : 64
AuditClientCertificateAccess : False
AuditSmb1Access : False
AutoDisconnectTimeout : 15
AutoShareServer : True
AutoShareWorkstation : True
CachedOpenLimit : 10
DisableCompression : False
DisableSmbEncryptionOnSecureConnection : True
DurableHandleV2TimeoutInSeconds : 180
EnableAuthenticateUserSharing : False
EnableDirectoryHandleLeasing : True
EnableDownlevelTimewarp : False
EnableForcedLogoff : True
EnableLeasing : True
EnableMultiChannel : True
EnableOplocks : True
EnableSecuritySignature : False
EnableSMB1Protocol : False
EnableSMB2Protocol : True
EnableSMBQUIC : True
EnableStrictNameChecking : True
EncryptData : False
EncryptionCiphers : AES_128_GCM, AES_128_CCM, AES_256_GCM, AES_256_CCM
InvalidAuthenticationDelayTimeInMs : 0
IrpStackSize : 15
KeepAliveTime : 2
MaxChannelPerSession : 32
MaxMpxCount : 50
MaxSessionPerConnection : 16384
MaxThreadsPerQueue : 20
MaxWorkItems : 1
NullSessionPipes :
NullSessionShares :
OplockBreakWait : 35
PendingClientTimeoutInSeconds : 120
RejectUnencryptedAccess : True
RequestCompression : False
RequireSecuritySignature : False
RestrictNamedpipeAccessViaQuic : True
ServerHidden : True
Smb2CreditsMax : 2048
Smb2CreditsMin : 128
SmbServerNameHardeningLevel : 0
TreatHostAsStableStorage : False
ValidateAliasNotCircular : True
ValidateShareScope : True
ValidateShareScopeNotAliased : True
ValidateTargetName : True
PS C:\WINDOWS\system32> Get-NetUDPEndpoint
LocalAddress LocalPort
------------ ---------
:: 62454
:: 56718
:: 56710
:: 51847
:: 50502
::1 50062
fe80::723e:7ca:789d:a5aa%35 50061
::1 5353
:: 5353
:: 3702
fe80::723e:7ca:789d:a5aa%35 1900
::1 1900
0.0.0.0 62453
127.0.0.1 59312
0.0.0.0 56717
127.0.0.1 56716
0.0.0.0 56709
0.0.0.0 50502
127.0.0.1 50065
192.168.68.114 50064
10.5.0.2 50063
127.0.0.1 10010
192.168.68.114 5353
10.5.0.2 5353
0.0.0.0 5353
0.0.0.0 5050
0.0.0.0 3702
192.168.68.114 1900
127.0.0.1 1900
10.5.0.2 1900
192.168.68.114 138
10.5.0.2 138
192.168.68.114 137
10.5.0.2 137
I am at a complete lose now as to what I can do as I cannot find developer details on exactly how net use or New-PSDrive actually work under the hood that could help me figure out the root cause.
Any guidance would be truly appreciated.
Windows for home | Windows 11 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
4 answers
Sort by: Most helpful
-
Anonymous
2025-06-02T20:46:56+00:00 -
Anonymous
2025-05-06T13:12:28+00:00 Just following up. Would anyone on the Microsoft team be able to assist with this issue.
-
Anonymous
2025-04-19T00:30:20+00:00 Thank you so much for taking the time to consider my problem and replying. It is truly appreciated! Unfortunately, I continue have the issue persist. An additionally issue presented itself when running netcfg -d
C:\Windows\System32>netcfg -d
... failed. Error code: 0x0.
I have rebooted several times - still get this message after running ipconfig /flushdns (which works as expected)
I did run sfc /scannow and it indicated there are no issues.
I update the SMB config as suggested (before doing the flushdns and netcfg step and subsequent reboots)
PS C:\WINDOWS\system32> Get-SmbServerConfiguration
AnnounceComment :
AnnounceServer : False
AsynchronousCredits : 64
AuditClientCertificateAccess : False
AuditSmb1Access : False
AutoDisconnectTimeout : 15
AutoShareServer : True
AutoShareWorkstation : True
CachedOpenLimit : 10
DisableCompression : False
DisableSmbEncryptionOnSecureConnection : True
DurableHandleV2TimeoutInSeconds : 180
EnableAuthenticateUserSharing : False
EnableDirectoryHandleLeasing : True
EnableDownlevelTimewarp : False
EnableForcedLogoff : True
EnableLeasing : True
EnableMultiChannel : True
EnableOplocks : True
EnableSecuritySignature : False
EnableSMB1Protocol : False
EnableSMB2Protocol : True
EnableSMBQUIC : True
EnableStrictNameChecking : False
EncryptData : False
EncryptionCiphers : AES_128_GCM, AES_128_CCM, AES_256_GCM, AES_256_CCM
InvalidAuthenticationDelayTimeInMs : 0
IrpStackSize : 15
KeepAliveTime : 2
MaxChannelPerSession : 32
MaxMpxCount : 50
MaxSessionPerConnection : 16384
MaxThreadsPerQueue : 20
MaxWorkItems : 1
NullSessionPipes :
NullSessionShares :
OplockBreakWait : 35
PendingClientTimeoutInSeconds : 120
RejectUnencryptedAccess : False
RequestCompression : False
RequireSecuritySignature : False
RestrictNamedpipeAccessViaQuic : True
ServerHidden : True
Smb2CreditsMax : 2048
Smb2CreditsMin : 128
SmbServerNameHardeningLevel : 0
TreatHostAsStableStorage : False
ValidateAliasNotCircular : True
ValidateShareScope : True
ValidateShareScopeNotAliased : True
ValidateTargetName : True
Still getting System error 67 ...
C:\Windows\System32>net use X: \192.168.68.112\SSD /user:mysmbuser mysmbpasswd
System error 67 has occurred.
The network name cannot be found.
Ping and TraceRt work
My hosts file does have the mapping for raspberrypi to the lan address and both ping and tracert resolve the name to ip address without issue.
C:\Windows\System32>ping raspberrypi
Pinging raspberrypi [192.168.68.112] with 32 bytes of data:
Reply from 192.168.68.112: bytes=32 time<1ms TTL=64
Reply from 192.168.68.112: bytes=32 time<1ms TTL=64
Reply from 192.168.68.112: bytes=32 time<1ms TTL=64
Reply from 192.168.68.112: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.68.112:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0msTracing route to raspberrypi [192.168.68.112]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms raspberrypi [192.168.68.112]
Trace complete.
Additionally nbstat can see raspberrypi
C:\Windows\System32>nbtstat -a raspberrypi
OpenVPN Data Channel Offload for NordVPN:
Node IpAddress: [0.0.0.0] Scope Id: []
Host not found.Local Area Connection:
Node IpAddress: [0.0.0.0] Scope Id: []
Host not found.Ethernet 2:
Node IpAddress: [192.168.68.114] Scope Id: []
NetBIOS Remote Machine Name Table Name Type Status --------------------------------------------- RASPBERRYPI <00> UNIQUE Registered RASPBERRYPI <03> UNIQUE Registered RASPBERRYPI <20> UNIQUE Registered ☺☻\_\_MSBROWSE\_\_☻<01> GROUP Registered WORKGROUP <00> GROUP Registered WORKGROUP <1D> UNIQUE Registered WORKGROUP <1E> GROUP Registered MAC Address = 00-00-00-00-00-00Bluetooth Network Connection:
Node IpAddress: [0.0.0.0] Scope Id: []
Host not found.Wi-Fi:
Node IpAddress: [0.0.0.0] Scope Id: []
Host not found.NordLynx:
Node IpAddress: [10.5.0.2] Scope Id: []
Host not found.Local Area Connection* 1:
Node IpAddress: [0.0.0.0] Scope Id: []
Host not found.Local Area Connection* 2:
Node IpAddress: [0.0.0.0] Scope Id: []
Host not found.If you could direct me to a low level debugging tool that could help me understand what net use is actually doing under the hood when it trying to establish or find the ip address. Whatever net use "resolver" function is has something that seems amiss on this one laptop which was working just fine until 10 am yesterday. No issues and then it just stopped being able to see the shares. The other computers remain able to see the shares and I have updated the global setting in the smb.conf file a suggested and restarted the smbd and nmbd services on the raspberry pi.
Again, my sincere thanks for your guidance and I look forward to any further guidance that might be able to provide or tools that I can use to get a finer level of debug information out of net use.
I just discovered that I got this in event viewer:
The SMB Signing registry value is not configured with default settings.
Default Registry Value:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]
"EnableSecuritySignature"=dword:1
Configured Registry Value:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]
"EnableSecuritySignature"=dword:0
and
The AllowInsecureGuestAuth registry value is not configured with default settings.
Default Registry Value:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]
"AllowInsecureGuestAuth"=dword:0
Configured Registry Value:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]
"AllowInsecureGuestAuth"=dword:1
These are set ... so not sure why I am getting this warning in the A&S Logs>Microsoft>Windows>SMBClient>Security Event Viewer
In the A&S Logs>Microsoft>Windows>SMBClient>Connectivity I am getting these errors when I try to add the share via file explorer.
The server name cannot be resolved.
Error: The requested interface is not supported.
Server name: 192.168.68.112
Guidance:
The client cannot resolve the server address in DNS or WINS. This issue often manifests immediately after joining a computer to the domain, when the client's DNS registration may not yet have propagated to all DNS servers. You should also expect this event at system startup on a DNS server (such as a domain controller) that points to itself for the primary DNS. You should validate the DNS client settings on this computer using IPCONFIG /ALL and NSLOOKUP.
appears WINS is not running?? Does WINS run on Windows 11 Pro??
PS C:\WINDOWS\system32> Get-Service -Name WINS
Get-Service : Cannot find any service with service name 'WINS'.
At line:1 char:1
+ Get-Service -Name WINS
+ ~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (WINS:String) [Get-Service], ServiceCommandException
+ FullyQualifiedErrorId : NoServiceFoundForGivenName,Microsoft.PowerShell.Commands.GetServiceCommand
192.168.2.1 is the wan router ip address. It is not a "true" dns server but rather forwards to the provided by the internet provider.
C:\Windows\System32>net use \192.168.68.112\SSD /user:mysmbuser mysmbpasswd
System error 67 has occurred.
The network name cannot be found.
results with this in the event log:
The server name cannot be resolved.
Error: The requested interface is not supported.
Server name: 192.168.68.112
Guidance:
The client cannot resolve the server address in DNS or WINS. This issue often manifests immediately after joining a computer to the domain, when the client's DNS registration may not yet have propagated to all DNS servers. You should also expect this event at system startup on a DNS server (such as a domain controller) that points to itself for the primary DNS. You should validate the DNS client settings on this computer using IPCONFIG /ALL and NSLOOKUP.
I have confirmed that TCP/IP NetBIOS Helper is running ... but to no avail ... Sigh ...
The issue is definitely related to the resolution of the "server" step ... how do I get more insight?
Again my thanks in advance.
-
Anonymous
2025-04-18T21:17:14+00:00 Hello! According to the description, I understand that you are facing the "System Error 67: The network name cannot be found" issue. In order to resolve this, follow the below steps:
- Open PowerShell as Administrator and run: Set-SmbServerConfiguration -EnableStrictNameChecking $false
- Run: Set-SmbServerConfiguration -RejectUnencryptedAccess $false
- On the Raspberry Pi: Update /etc/samba/smb.conf to include: [global] client min protocol = SMB2 server max protocol = SMB3 Restart Samba with: sudo systemctl restart smbd
- Resolve any misconfigurations in the network stack by executing the following commands: ipconfig /flushdns netcfg -d Reboot the system after running these commands.
- Add the Pi's IP address to the HOSTS file located at C:\Windows\System32\drivers\etc\hosts: 192.168.68.112 raspberrypi Alternatively, test direct IP-based access with: net use X: \192.168.68.112\SSD /user:mysmbuser mysmbpasswd
- After completing the above steps, map the network share again: net use X: \192.168.68.112\SSD /user:mysmbuser mysmbpasswd
Best Regards, Van Johnson | Microsoft Community Moderator