Can see network, but cannot connect

Tipiford · 09 Aug 2017

SoundOfMind said:

... there might be a problem with your network".

I am confident the network is functioning fine, it is reached by every other computer on the network, Win7 and XP.

maconnolly · 10 Aug 2017

Tipiford said:

Ver 6.1 build 7601; SP1. Getting error, "Windows cannot access \\SERVER"

Really simplistic first step - but can you replace the DNS name in the network path with the IP address of the server and confirm if there is a different result?

So, if you have \\SERVERNAME\ShareName, instead, type \\xx.xx.xx.xx\ShareName into the address bar in Windows Explorer on the client machine.

If it is able to resolve by IP address, but not by DNS name, then the issue is with DNS resolution and we can look at why that is.
@SoundOfMind - you could try something similar and report back; this may equally be a DNS issue for you.

Tipiford · 14 Aug 2017

bro67 said:

Did you go into Services to see if Computer browser is there and running. You can use lan Scanner from Downloads | Scotties Tech.Info to see in the Command Window that the computers are all being seen by your machine.

Services.msc reports: Computer browser running, and all the Lanscan program does is reports the networks on the system, which is what we already see, but cannot access.

Tipiford · 14 Aug 2017

maconnolly said:

can you replace the DNS name in the network path with the IP address of the server and confirm if there is a different result?

So, if you have \\SERVERNAME\ShareName, instead, type \\xx.xx.xx.xx\ShareName into the address bar in Windows Explorer on the client machine.

Still no joy in networkville

bro67 · 14 Aug 2017

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.

Tipiford · 14 Aug 2017

bro67 said:

...nbtstat -r or nbtstat -rr. B

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

bro67 · 14 Aug 2017

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.

Tipiford · 14 Aug 2017

bro67 said:

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

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

Samuria · 14 Aug 2017

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

bro67 · 14 Aug 2017

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.