Windows 10: Can see network, but cannot connect

I have discovery and sharing on, and I can see the network, but cannot connect. I have 'forgotten' the network and re-connected, but that doesn't resolve the issue. I reach the internet through this network but cannot connect to our server, and other computers connect to it but not this win10 computer.

:)

 

Win 10 Network Printer Connection Problem

When connected to a network that has a printer connected to it I can see and use the network but cannot see or use the printer. The printer is on the network from a Win 7 system and I have a Win 10 system

Other pc's can see the printer and use it. I cannot even find the printer in Devices or searching for it.

I have other networks where I can see my printers and use them on the PC with Win 10

 

Windows 10 Upgrade Network computers no longer available

I upgraded my computers on my network to Windows 10 and I cannot connect to printers attached to a local machine. Each computer can see the printer attached to the server, but we can no longer share printers connected to a local machine. I also cannot
see the other computers on the network,

 

Hey Tipiford,
Little more info would help....

What version of Win10 ? (winkey+r > type in winver > click ok)
What error are you getting ?

 

If smb1 is turned off in Windows Features, it removes the Computer Browser service, which is needed for SMB2 & 3. I posted the info on how to disable smb1 from the command line, turn Computer Browser to Automatic and all computers will be seen in Network, instead of having to always remember the IP to get to them.

 

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

 

I can see all the computers in the network, just cannot access them.

 

What shares are set up and who has rights on the shares?

 

All are shared, and Everyone has permissions.

 

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.

The Firewall can cause problems, same as if you disabled SMBv1 an did not go through the steps to disable from the command Window with the sc.exe command.

 

In my client's windows explorer network, I can see my server SHOWDOG. When I click on it, I get "windows cannot access \\SHOWDOG Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose."
Clicking on Diagnose results in "Your computer appears to be correctly configured, but the device or resource (SHOWDOG) is not responding".
SMB1 and Computer Browser are running on server.
Both client and server are in the same workgroup.
Server is Win 10 pro version 1703, running static IP (block of static IP addresses is reserved in router)
Client is Win 7 pro version 6.1 build 7601 Service pack 1 running dynamic IP
Has been running successfully for a long time, but lately no access is allowed.
I can use remote desktop from client using the server's static IP address, but never could access using server name (not a problem, just confirmation that server can be accessed).
I have a local account on the server, with read and write permissions for two folders.

 

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

 

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.

 

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.

 

Still no joy in networkville