My PC is not listed in Network

K, lets make sure both PCs are using the same SMB and for now we want to use SMB1 on both.

On the laptop ...
Open PowerShell as Administrator and run the following command
Set-SmbServerConfiguration -EnableSMB1Protocol $true

Then run this one and make sure both are yes
Get-SmbServerConfiguration | Select EnableSMB1Protocol, EnableSMB2Protocol

On both PCs ...
Open Command Prompt as Administrator
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb10 start= auto



Reboot both PCs

Hi

Both HT-PC and laptop had been configured with your last info.

Then 2 restarts on both HT-PC and laptop. Now is not HT-PC visible in network list on no computer.

When I try \\192.168.1.64 in search on laptop i get same error message with problem with SMB on HT-PC.

I'm still not sure why your nebios/tcpip is disable or how to fix it right now ... but since your netbios/tcpip is showing disabled in ipconfig you won't be able to use the \\192.168.1.64\ShareName ... See if \\ComputerName\ShareName works ?

FYI ... On the SMB stuff ...
For now you want both SMB1 and SMB2 server/client protocols enabled on ALL PC's.
SMB2 is preferred over SMB1 and once you get things working, you may want to disable SMB1, but you don't have to.

The BOLD is want to you want run on each PC and you must reboot each PC for them to take effect.

PowerShell as Administrator ...
Get-SmbServerConfiguration | Select EnableSMB1Protocol, EnableSMB2Protocol
If one shows No ... see the Server Commands below to enable it
Command Prompt as Administrator ....
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb10 start= auto
sc.exe config mrxsmb20 start= auto

===============================================================

Server Commands to be run in PowerShell as Administrator ...

To obtain the current state of the SMB server protocol configuration, run the following cmdlet:
Get-SmbServerConfiguration | Select EnableSMB1Protocol, EnableSMB2Protocol

To disable SMBv1 on the SMB server, run the following cmdlet:
Set-SmbServerConfiguration -EnableSMB1Protocol $false
To enable SMBv1 on the SMB server, run the following cmdlet:
Set-SmbServerConfiguration -EnableSMB1Protocol $true
To disable SMBv2 and SMBv3 on the SMB server, run the following cmdlet:
Set-SmbServerConfiguration -EnableSMB2Protocol $false
To enable SMBv2 and SMBv3 on the SMB server, run the following cmdlet:
Set-SmbServerConfiguration -EnableSMB2Protocol $true
=============================================================

Client Commands to run in Command Prompt as Administrator ....

To disable SMBv1 on the SMB client, run the following commands:
sc.exe config lanmanworkstation depend= bowser/mrxsmb20/nsi
sc.exe config mrxsmb10 start= disabled
To enable SMBv1 on the SMB client, run the following commands:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb10 start= auto

To disable SMBv2 and SMBv3 on the SMB client, run the following commands:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled
To enable SMBv2 and SMBv3 on the SMB client, run the following commands:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb20 start= auto


Reference ... https://support.microsoft.com/en-us/...ws-and-windows