SMBv2 not listening on Port 445

Question

_{Saturday, March 3, 2018 9:59 PM}

Is there a service which uses SMBv2 ("smbwmiv2.dll" [nirsoft]) to open Port 445 for listening?

netstat -a

shows no listener for Port 445 even with the Windows Defender Firewall temporarily off.

The following is more information about SMBv2:

C:\Windows\System32\smbwmiv2.dll

File description: WMIv2 Providerfor SMB File Server/Client
Type: Application extension
Reversion: 10.0.16299.15

smbwmiv2.dll appears in the following registry locations so it is registered:

Computer\HKEY_CLASSES_ROOT\CLSID\3B873591-9427-4418-A086-79175735738F}\InprocServer32

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\3B873591-9427-4418-A086-79175735738F}\InprocServer32

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\50b9e206-9d55-4092-92e8-f157a8235799}

In PowerShell,

Get-SmbServerConfiguration | Select EnableSMB2Protocol

says SMBv2 is True.

"sfc /scannow" is 100% so "smbwmiv2.dll" is not corrupted.

Network Reset button did not correct issue.
Start > Settings > Network & Internet > Status > "Network reset" button

Is there a service I need to have running to tell it to start listening?

Thanks in advance.

All replies (16)

_{Saturday, March 3, 2018 11:39 PM}

Not sure what stops 445 listening but have seen a similar post (that one the poster put down to an image issue as a clean install worked fine).

Try from an admin command prompt;

netcfg -d

and then reboot. That resets the networking see if that helps.

_{Sunday, March 4, 2018 2:47 AM}

According to the following article, "Network reset" button does the same as "netcfg –d".

How to Cleanup and Reset Network Adapters in Windows 10

Start > Settings > Network & Internet > Status > "Network Reset" button

Unfortunately, "Network Reset" button did not correct the problem.

Thank you for the suggestion.

_{Sunday, March 4, 2018 5:31 PM | 1 vote}

Ok yes that does appears the same as netcfg -d sorry.

So just had tried to stop a test machine listening on 445, remembered about the Server service, had to disable that and reboot then my machine no longer shows listening on 445.

So is the Server service running, from PowerShell;

Get-Service -Name Server | Select-Object *

What does that show?

_{Wednesday, March 14, 2018 8:10 AM}

Hi,

We haven’t heard from you for a couple of days, have you solved the problem? 

Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Saturday, June 16, 2018 7:19 PM}

I am having the same issue.  Prior to build 1803, I was fixing this problem by un-installing and re-installing File and Printer Sharing for Microsoft Networks.  After that, all would be good again until next reboot.

Now with Windows 10 version 1803, I can no longer remove File and Printer Sharing.

_{Saturday, June 16, 2018 7:57 PM}

I am having the same issue.  Prior to build 1803, I was fixing this problem by un-installing and re-installing File and Printer Sharing for Microsoft Networks.  After that, all would be good again until next reboot.

Now with Windows 10 version 1803, I can no longer remove File and Printer Sharing.

is the Server service running, from PowerShell;

Get-Service -Name Server | Select-Object *

What does that show?

_{Tuesday, July 10, 2018 8:59 PM}

The server seems to be running:

PS C:\WINDOWS\system32> Get-Service -Name Server | Select-Object *

Name                : LanmanServer
RequiredServices    : {SamSS, Srv2}
CanPauseAndContinue : False
CanShutdown         : False
CanStop             : True
DisplayName         : Server
DependentServices   : {Browser}
MachineName         : .
ServiceName         : LanmanServer
ServicesDependedOn  : {SamSS, Srv2}
ServiceHandle       : SafeServiceHandle
Status              : Running
ServiceType         : Win32OwnProcess, Win32ShareProcess
StartType           : Automatic
Site                :
Container           :

Netstat -ano 

...  TCP    172.19.7.88:3793       40.84.43.40:443        ESTABLISHED     6224
  TCP    [::]:7                 [::]:0                 LISTENING       5272
  TCP    [::]:9                 [::]:0                 LISTENING       5272
  TCP    [::]:13                [::]:0                 LISTENING       5272
  TCP    [::]:17                [::]:0                 LISTENING       5272
  TCP    [::]:19                [::]:0                 LISTENING       5272
  TCP    [::]:80                [::]:0                 LISTENING       4
  TCP    [::]:135               [::]:0                 LISTENING       1160
  TCP    [::]:443               [::]:0                 LISTENING       9736
  TCP    [::]:623               [::]:0                 LISTENING       1584
  TCP    [::]:1536              [::]:0                 LISTENING       828
  TCP    [::]:1537              [::]:0                 LISTENING       2736...

the Get-SmbServerNetworkInterface command doesn't show any adaptors

_{Friday, July 13, 2018 7:42 PM | 4 votes}

I just saw that I had the same issue. I unchecked the File sharing protocol on the NIC. Re-Opened the settings and checked the box again to re-activate it. Then suddenly I was able to access this device.

I am using Windows 1703.

_{Sunday, September 2, 2018 2:37 PM}

Does it survive reboot? Having the same  issue, just cannot find a permanent fix for it.

_{Wednesday, September 5, 2018 8:49 PM | 1 vote}

Just had a case in which the un-check / re-check of the File and sharing feature on NIC did the trick. You can also try the command netsh int ip reset. Finally, you can try updating NIC drivers.

Also, ensure the server service (or its internal name "lanmanserver") is up and running. That's the server which controls the port TCP 445 on Windows.

_{Thursday, November 15, 2018 5:32 PM}

I have this same problem, Windows 10 was not listening on port 445, network device is an OpenVPN Tap.

"netcfg -d" did not help.

Simply un-checking & re-checking the box resolves the issue, but, as per above, it does not survive a reboot.

Does anyone know a permanent fix?

_{Thursday, November 29, 2018 11:33 PM}

I just saw that I had the same issue. I unchecked the File sharing protocol on the NIC. Re-Opened the settings and checked the box again to re-activate it. Then suddenly I was able to access this device.

I am using Windows 1703.

Thank you!!! Crazy it works this way and not through Advanced Sharing Settings

_{Saturday, December 8, 2018 2:30 AM}

Bravo!

What a stupid bug ...

_{Monday, December 17, 2018 7:23 PM | 3 votes}

Hello All,

Here is the workaround which work for me.

I have created the following powershell script. (restart.Ps1)

Disable-NetAdapterBinding -Name "AdapterName" -DisplayName "File and Printer Sharing for Microsoft Networks"
Enable-NetAdapterBinding -Name "AdapterName" -DisplayName "File and Printer Sharing for Microsoft Networks"

 Than created .bat file for the startup execution. (Autorun.bat)

 PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& {Start-Process PowerShell -ArgumentList '-NoProfile -ExecutionPolicy Bypass -File ""D:\restart.ps1""' -Verb RunAs}"

Hope this help  !

_{Sunday, December 23, 2018 9:52 PM}

Thanks a lot!

This fixed the issue for me, I would just add that you can get your "AdapterName" using Get-NetAdapter, under column one "Name" is the string you should use.

Tony

_{Friday, March 29, 2019 2:21 PM | 1 vote}

Here is language independent version

Disable-NetAdapterBinding -Name "Ethernet" -ComponentID "ms_server"
Enable-NetAdapterBinding -Name "Ethernet" -ComponentID "ms_server"