Netbios over TCP/IP issue from recent update? - Windows 10

2017-11-16

Question

_{Thursday, November 16, 2017 10:31 PM | 1 vote}

Hello everyone.

I running Windows 10 x64 with newest updates (latest from 15 of Nov, 2017), did anyone experienced that you cannot ping local devices by hostname? Nslookup and tracert also found nothing.

Even forcing the Netbios tcp/ip to enabled on NIC does nothing and ipconfig /all says, that is disabled on every interface I've tried.

I've tried also "Reset network" from menu start, but it just wiped all WiFi profiles, didn't fixed the issue for me.

And yes, I also done every possible solution on the web as checking services related to network running, dnsflushes, changing dns, sockets etc.

All services that has "network" in name are enabled and setup to automatic start.

Network is set to private.

Also tried "sfc /scannow" but no changes at all.

Reinstalling all NICs drivers does nothing also.

Disabling all of the 3rd party on boot does exactly the same - nothing.

Turned off, then uninstalled Avast antyvirus didn't changed much at all also.

Windows firewall down - no change.

Other Windows devices in my LAN can ping by hostnames, but this is strictly related to Windows 10.

About week ago everything was fine, I've realized it today because my network driver that are mapped by hostname of my NAS cannot connect. But when I try using IP address of my NAS - everything is fine.

Any ideas or is it just a bug in some of the latest updates?

My updates:

https://i.imgur.com/CbIU8Oz.png

All replies (11)

_{Friday, November 17, 2017 1:22 AM}

It is probably because SMB 1.0 is disabled by default in Windows 10 now. If you do enable it, make sure that you disable the computer browser service on the Windows 10 machine as you will have problems if it becomes the master browser.

The latest versions of Windows 10 do not play well with the old NT-style browser service (which your NAS probably relies on). You will find other posts on this topic in this forum.

Bill

_{Friday, November 17, 2017 2:35 AM}

Rollback to 1607 while you still can - after 10 days rolling back is much more work. Make a backup first though because the rollback has some major glitches in 1709 as well. If they made a movie about the FU (1709) Fall Update edition of Windows 10 it would be a German Scheisse movie called Zwei Mädchen und ein PC

_{Friday, November 17, 2017 7:55 AM}

I using Synology DS216j, which is quite new and I didn't change SMB version on it from few months and everything worked fine till now. SMB on my NAS is set to use min. SMB 2 and max SMB 3.

_{Monday, November 20, 2017 4:18 AM}

Hi logiczny,

Thank you for your post.

I've met some people have the issue before after upgrade to Windows 1709 version.

You could check the registry in the below link.

https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/netbios-over-tcpip-broken-since-upgrade-to/fd141dd9-8500-419d-b8e7-ac7255f44ec0

If the issue still insists, I’m afraid that we could only format and reinstall.

I also forward this information to the appropriate department through our internal channel. Hope to launch an automated repair tool to fix.

Best regards,

Carl

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

_{Friday, November 24, 2017 1:18 PM}

Hi,

Any update?

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

_{Monday, March 12, 2018 4:16 PM}

OK - wow! - Under HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters\Interfaces\ I have four Tcpip entries - NONE of them show a DhcpNameServerList key. All 4 show keys "NameServerList" and "NetbiosOptions" keys, but NONE of them are configured with any values.

Uninstalling and reinstalling my network card didn't help.

Ideas?? I want my NetBios back - can't connect see my LAN shares!

Thanks, Joe

_{Wednesday, March 14, 2018 1:39 AM}

Thank you for helping me!

I am trying to get my Technet account verified so I can post screen shots (!) - I am a new user - but

my Device Manager shows multiple virtual network adapters related to VirtualBox, VPNs, etc. I am concerned that deleting the devices in Device Manager will disrupt the installations of those programs, no? They wouldn't reinstall automatically on restart like real hardware.

Do you possibly have another way I can send you screen shots of my Device Manager and ipconfig?

Thanks!

Joe

_{Wednesday, March 14, 2018 2:55 AM}

I've used other file upload services, but not Google Drive, though I do have it available. Don't I need an email address to share with you? Apparently I can't post hyperlinks either, until "verified".

Thanks,

Joe

_{Wednesday, March 28, 2018 9:23 PM}

Wow! I finally found a recent post which sounds like it's related to the issue I'm having!

I'm attempting to get a Windows 10 Pro AND a Windows 7 Pro PC to accept print jobs generated in a Red Hat Linux server.

I have all firewalls off, windows defender off, internet security uninstalled, malware programs uninstalled.

Countless times I was ABLE to set up a printer on a Win 7 Pro and even Windows 10 Pro PC and, after I set up/enabled the guest account, made the password blanks with netplwiz, disabled firewalls, enabled 56-bit encryption, enabled NetBIOS over TCP/IP, I was able to print to the shared printer on those PCs...

But in the past couple months I have two customers I've been trying to set up a shared printer on a Windows 10 pro and a Windows 7 Pro PC and the print jobs just are not allowed to pass to the PCs.

Here's a command that I use in Linux which tests windows shares...

$ smbclient -L 192.168.1.4 -U guest

Here's a GOOD result...

[root@silvwh etc]# smbclient -L 192.168.1.4 -U guest

Password:

Domain=[SILVWH002] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

Sharename Type Comment

IPC$ IPC Remote IPC

print$ Disk Printer Drivers

Drawer Printer Drawer

Receipt Printer Receipt

ADMIN$ Disk Remote Admin

C$ Disk Default share

session request to 192.168.1.4 failed (Called name not present)

session request to 192 failed (Called name not present)

Domain=[SILVWH002] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

Server Comment

Workgroup Master

[root@silvwh etc]#

*****

****

******And here is what I've been getting recently....******

******

[root@silvwh etc]# smbclient -L 192.168.1.2 -U guest

Password:

Anonymous login successful

Domain=[WORKGROUP] OS=[Windows 7 Professional 7601 Service Pack 1] Server=[Windo

ws 7 Professional 6.1]

Sharename Type Comment

Error returning browse list: NT_STATUS_ACCESS_DENIED

session request to 192.168.1.2 failed (Called name not present)

session request to 192 failed (Called name not present)

session request to *SMBSERVER failed (Called name not present)

NetBIOS over TCP disabled -- no workgroup available (BUT… NETBIOS over TCP/IP is ENABLED!!... and the workgroup is set to WORKGROUP!!)

[root@silvwh etc]#

(Yes that specific result is for the Win 7 Pro PC but I get the same exact result from the customer with the Windows 10 Pro PC... I just happened to be logged into this other customer today)

I have triple and quadruple checked the settings in the one and only Network adapter... I go into the Properties, highlight Internet Protocol version 4 TCP/IP, click Properties, click Advanced, click on the WINS tab, and the "Enable NetBIOS over TCP/IP" setting is the one that is selected.

So, it seems like, even though the SETTING says it's enabled, Windows ACTUALLY has NetBIOS DISABLED somewhere behind the scenes!

Does that sound about right?

If so, am I really supposed to find some key value in a specific registry key then find a BUNCH of places in the registry and add that key to all those places? There isn't a way to just re-enable NetBIOS over TCP/IP?

Thanks so much ahead of time for any help you can provide!

_{Thursday, March 29, 2018 2:11 PM}

Hi Acester,

You can still enable or disable NetBIOS over TCP/IP through the registry:

Start the registry editor (regedit.exe).

Move to HKLM\SYSTEM\CurrentControlSet\services\NetBT\Parameters\Interfaces.

Select each interface GUID.

Any GUID that has a NetbiosOptions

• 0: Use the DHCP value or the default settings (this is to enable NetBIOS)

• 2: Disable NetBIOS over TCP/IP

Momominta

That is the same as using the GUI. It is already set to enable.

_{Thursday, September 6, 2018 4:38 PM}

Solucione el problema para habilitar el NetBios y acceder a las carpetas compartidas con esta soluciòn

Si no encuentran DhcpNameServerList es la primera NetbiosOptions REG_DWORD (1) que tenga (1) ya que es de mi tarjeta de Eternet que Habilite Netbios en la pestaña WINS en Configuraciòn avanzada TCP / IP.... en ese caso tome la Tcpip_ {} ya que estaba activa NetbiosOptions REG_DWORD (1)

Gracias por la ayuda..

En HKLM \ SYSTEM \ CurrentControlSet \ Services \ NetBT \ Parameters \ Interfaces \ verá una o más entradas de Tcpip. Para determinar qué entrada Tcpip se refiere a su tarjeta roja, simplemente haga clic en cada una hasta que vea una con DhcpNameServerList a la izquierda con una dirección IP completa. La larga cadena de letras y números en el {} por esa clave es lo que se necesita (su) se refiere a esa clave. Básicamente, acabo de copiar las claves ya en lo siguiente y agregué {su}} a cada una una.

HKLM \ SYSTEM \ CurrentControlSet \ Services \ LanmanServer \ Linkage

Enlazar-ejemplo

Adicional:

\ Dispositivo \ Tcpip_ {su}}
\ Dispositivo \ Tcpip6_ {su}}
\ Dispositivo \ NetBT_Tcpip_ {su}}
\ Dispositivo \ NetBT_Tcpip6_ {su}}
\ Dispositivo \ Smb_Tcpip_ {su}}
\ Dispositivo \ Smb_Tcpip6_ {su}

Haga lo mismo, haciendo coincidir los ajustes de la clave y agregando {su} a Exportar y enrutar. Cada clave es diferente, así que asegúrese de hacer coincidir lo que ya está allí. También haga esto para enlazar, exportar y encaminar a la siguiente:

HKLM \ SYSTEM \ CurrentControlSet \ Services \ LanmanWorkstation \ Linkage

HKLM \ SYSTEM \ CurrentControlSet \ Services \ NetBIOS \ Linkage

HKLM \ SYSTEM \ CurrentControlSet \ Services \ NetBT \ Linkage

Reinicia el sistema.

Momominta

Viernes, 26 de enero de 2018 a las 6:01 a.m.

Respuesta

Citar

Proponer como respuesta

Informar como abuso

momominta

6,855 Puntos

Share via

Netbios over TCP/IP issue from recent update? - Windows 10

Question

All replies (11)

Additional resources