Windows 10: Can see network, but cannot connect

What do you get back if you run nbtstat -r or nbtstat -rr. You may have to remove the network adapter and drivers in device manager and then reboot. The other could be that it is another machine not releasing Master for smb/cifs.

This mess is getting to where even Microsoft will not own up to what and how much they have made a mess of smb/cifs with Windows 10.

I do have on the one desktop running Windows 10, that Guest is enable, password protection turned off in advanced sharing. I do not have Homegroup being used, since it can tend to make a mess of things.

Now what you could do also is a Repair of the OS, which does not remove anything, just fixes what any of the updates have screwed up.

 

I get "Resolved by Broadcast = 42; Resolved by Nameserver = 0; Registered by Broadcast = 86; Registered by Nameserver = 0; and a grouping of the networks with several blocks of "?" and neither do we use homegroup

 

I had the same issue with wing-dings in the Command Terminal also. Had to change fonts to get rid of them. See if this fixes the whole Unicode mess from Run. C:\Windows\System32\cmd.exe /K chcp 65001 It is basically making the change in the registry at this position. HKEY_CURRENT_USER\Console\%SystemRoot%_system32_cmd.exe\CodePage to 0xfde9 (65001 in decimal system

Each day with Windows 10 is like getting presents from gandma and never now what is in them.

 

The only thing in HKEY_CURRENT_USER\Console\ is:
HKEY_CURRENT_USER\Console\%SystemRoot%_System32_WindowsPowerShell_v1.0_powershell.exeandHKEY_CURRENT _USER\Console\%SystemRoot%_SysWOW64_WindowsPowerShell_v1.0_powershell.exe

I ran C:\Windows\System32\cmd.exe /K chcp 65001 and it does not to the registry nor changes our network issue
Thanx for helping out on this

 

Local network doesnt use dns it uses netbios does this show all pc and which one is master browser NetBScanner - NetBIOS scanner

Then on a pc you cant connect to from a cmd prompt type

net share

post results

 

The adding of that key is to fix the garbage from wingdings in the terminal. Never stated that it had anything to do with the network problem. You will most likely have to do what I did with my wife's desktop and do a repair that does not remove any user settings or programs. It just fixes anything that is messed up or missing.

There is no rhyme or reason why the wingdings due to messed up Unicode happened with Command Terminal. It just popped up over the past week when I was working on her machine to get things done on it, so that I am not spending hours every day to fix something that Microsoft screwed up in their code.

 

Sorry to break your heart. Netbios is a left over from the old legacy days. Modern day systems do not even use NBF anymore. They resolve with the IP out of the DNS scheme and NBT. I do not even see CIFS staying around much longer, since it is a hashed up protocol that Microsoft created in order to communicate in the first days of SMB1.

The last time that I remember using WINS and Netbios, was back in the Windows 9x and NT4 days. Those days are gone. Microsoft is stuck in the past in how they allow their machines to communicate across a network, especially in today's mixed networks that the gateway/router is running on Linux, streaming devices are running on Android OS, tablets and smartphones either running Android OS or iOS, along with desktops and laptops that may be running Windows, Linux, Chrome OS or Mac OS. Even now as we speak, there are Android based Laptops that are out on the market.

 

Thanks so much!! Setting the static IP did allow me to access server shares. Then I messed with my router and wireless access point. The WAP was doing it's own DNS (which I just now changed back to using the modem/router DNS). That was done because the modem/router seems a little flaky. If it is still unreliable, I might disable the router portion and add a router.

 

Sorry to respond to this after such a long time - but I'm glad you were able to make some progress!

In general, I'm glad things are functioning now - although if you want us to go further into it, please feel free to respond. You're also welcome to PM me if you'd like to avail more details about specific configurations on different equipment that you are concerned about.