Windows 10: Network Discovery broken again

[esamett]

Windows 10 did another mandatory update this week and I cant find my FreeNAS server again under Network. I have gone to advanced network settings and opened up all settings again: sharing, no password, no home group, etc. This time I cant even enter the IP address (192.168.0.193) of my box in windows search. When I do I get the FreeNAS control panel login screen. Same result with \\freenas. I am still running the Free NAS 9.x. I seem to recall that entering the IP address manually used to work.

As suggested in my thread last year (https://forums.freenas.org/index.php?threads/windows-10-network-discovery-broken-again.42831/) I am didthe DISM and SFC commands in CMD/Administrator window.

If it helps, I have Win XP running as a Virtual PC using VMWare. There is no problem with XP.

Help please!

 

[gpsguy]

Can you access it using \\ipaddress\sharename in Windows Explorer?

 

[Ericloewe]

That's not merely NetBIOS being worthless, that's a real issue client-side. What's the network setup?

 

[esamett]

Search window on right fails. Address line on left works.

Running asus router running dhcp and a couple switches around house. Gateway is 192.168.0.1. Nas is 192.168.0.193 fixed. Using old style workgroup "samett", 40 bit old style encryption, no passwords, no workgroups.

 

[Ericloewe]

Maybe a misbehaving antimalware suite?

 

[esamett]

Running win 10 Microsoft only. I also recently upgraded to newest 9.x freenas build

 

[gpsguy]

Which Windows 10? Creators Update aka 1703?

Did you try my earlier suggestion?

 

[muctl]

Similar problem here.
The freenas is not shown in network-section on Win-machines.
Connect via \\freenas\share works.

Error in log.nmbd:
[2017/08/08 18:55:51.767970, 0] ../source3/nmbd/nmbd_subnetdb.c:127(make_subnet)
nmbd_subnetdb:make_subnet()
Failed to open nmb bcast socket on interface 192.168.11.255 for port 137. Error was Can't assign requested address
[2017/08/08 18:55:51.768011, 0] ../lib/util/become_daemon.c:111(exit_daemon)
STATUS=daemon failed to start: NMBD failed when creating subnet lists, error code 13

Any hints ?

FreeNAS ist last version 11.0-U2

 

[muctl]

Problem solved.
FreeNAS' smb/cifs can´t work with DHCP. Changed to fixed IP and the box appears in Win10.

 

[pschatz100]

Glad you got it solved. It is probably a problem with your router, or something in your network setup. I think there are lots of people who use FreeNAS with DHCP.

 

[esamett]

Problem solved.
FreeNAS' smb/cifs can´t work with DHCP. Changed to fixed IP and the box appears in Win10.

I have fixed IP and problem isn't fixed...

 

[esamett]

Can you access it using \\ipaddress\sharename in Windows Explorer?

It worked the other day with \\ip address. this morning I woke up to another win 10 update and entering \\ ipaddress\share is now windows security is now asking for network credentials. all my shares are "guest access". also my pc is now the only computer in my network according to windows.

will check security settings again

 

[esamett]

no changes to advanced network settings.

 

[anodos]

It worked the other day with \\ip address. this morning I woke up to another win 10 update and entering \\ ipaddress\share is now windows security is now asking for network credentials. all my shares are "guest access". also my pc is now the only computer in my network according to windows.

will check security settings again

Please send me a debug tarball through a PM. I'll take a look at it when I have some free time.

 

[esamett]

Please send me a debug tarball through a PM. I'll take a look at it when I have some free time.

sorry, I don't understand

 

[anodos]

sorry, I don't understand

Click System->Advanced->Save Debug. Send the debug file to me via a personal message in the forumware.

 

[esamett]

...seems fixed again. Thanks Microsoft