Windows 10: Dual NIC No Network Browsing on one Subnet

Hello,

I just finished updating from Windows 7 to Windows 10. My PC has a dual NIC and I am connected to two subnets. I am fully able to browse subnet A, the same as I could in Windows 7.

However, I am unable to automatically browse subnet B. I previously could in Windows 7.

In other words, when I go to "Network" on windows 10, all the Computer names on subnet A get populated. None of those on subnet B appear. However, if I manually type in the name of a device on subnet B (\\DEVICENAME) it will open it and I can browse the contents.

I had no problem in Windows 7 with browsing both subnets. I suspect there is a setting or difference in Windows 10, but I'm unable to find it. I've checked and the Computer Browser service is running, but it seems to only list PC's connected to the one NIC (subnet A) and not the other.

Any ideas?

:)

 

Map Network Drive across subnet

I have a PC on one subnet with a fixed I/P of 192.168.2.25

When it was a Windows 7 machine I set selected folders in it for share - anyone - read only and life was good - other PC's on that same 192.168.2.xxx network could access the folders just by browsing the network. PC's on a second subnet of 192.168.1.xxx
could use Map Network Drive to get to the PC using \\192.168.2.25\ then browse and also access the shared folders.

Then I upgraded the PC to Windows 10. ....

I checked the sharing and see it is still in place for the folders.

But when I went on a 192.168.2.xxx PC to try to access the PC I got the "enter login" screen....

to get around that I added a account to the 192.168.2.25 PC to allow PC's on the same 192.168.2.xxx network to access the files - and it requires those PC's to 'login' with that newly set up account. So that is a pain - but doable...

However on the 192.168.1.xxx network I no longer am able to 'see' the 192.168.2.25 PC using map network drive.

When I enter \\192.168.2.25 or \\192.168.2.25\ it craps out the first time I try it - then on subsequent attempts it is only showing my current network devices (the ones on 192.168.1.xxx).

 

PC lagging and stuttering during network traffic (Win 10)

I have the *exact* same problem. It only affects traffic to the default route, not traffic to my in-house subnet. When the problem kicks in, I can *not* ping (nor access) my default route (nor anything behind it). I *can* ping (or access) any device
on my subnet (e.g. another computer, a printer, even a raspberry pi). This problem showed up *after* some Windows 10 update and was *not* corrected by the fall 2017 Creator's Update. This problem is driving me *crazy*. The local subnet is wifi. The network
device is an Intel Dual-Band Wireless AC-8260. All of my software (OS, drivers) is up-to-date. Power saving for the wireless adapter is turned off.

 

Update

I played around with this for several hours and still don't have a fully working solution.

To elaborate on the problem, all the devices on subnet A are Windows devices running Win7, Win8, or Win10. Everything there is working as expected. All the devices on subnet B are linux, with smb shares.

The linux devices are "appliances". They boot linux but have no linux UI. They are read only and boot a preconfigured linux. They have an SSD attached for storage, which is what I need to access. One device is a linux server.

From any of the linux devices, they all see each other and they all see the windows 10 PC. No problems there. The only device that win10 can see is the linux server, and I think that is because I have a user on that server that has the same username and password as my win10 account.

When I browse the network, it doesn't show this device but if I type \\DEVICENAME into the browser, it will open it. I can then pin it into quick access and that sort of works. Scripts on my win10 PC that call it out by \\DEVICENAME work when I run them.

The appliances are a different story. At first I couldn't access them at all in win10. But I moved the network to public from private, and used a registry hack to allow connections to devices with no password. FYI, these appliances have no option to create users. You either turn samba on or off. If it is on, it publishes a share into the specified workgroup that is the same as the device name. If it is off, you have no share.

Anyway, now I can access these devices by \\IP_ADDRESS, but I cannot access them by \\DEVICENAME. This will require me to update all my scripts with IP's instead of device names, which sucks and makes it hard to keep things straight. When I run the win10 troubleshooter, it says devices aren't accessible because of a problem with the DNS server. The router is the DNS server, the same one used for the linux server, which works using \\DEVICENAME.

It just seems like win7 was gathering all the samba share info device names and IP's and then let you browse them. As a result you could use DEVICENAME for the the appliances. But Win10 is not performing this same behavior.

Still looking for help...