New
#11
Well, no luck.
Weird thing is, when my wife's Windows 10 laptop is on and connected to the network, I can connect to it from my computer in question. She can access the servers from her laptop, I can access her laptop from my computer, but I can't access the servers.
A couple of things...
The services mentioned should be set for Automatic (delayed Start) rather than just Automatic, not sure why probably to allow other things to start first
Also the Servers may be running a version of embedded Linux that only accepts SMBv1 for connection. Obviously there has been issues with using SMBv1 since the Wannacry attacks of last year, Windows ten is however fully patched against the vulnerability, so in conjunction with a modern security product/suite it should be safe to enable the SMBv1 protocol in the Add & Remove windows features (windows key then type feature should give access)
Hopefully these slight changes on all systems running Windows 10 should solve the issues.
Warningplease be careful with any older windows operating systems, (Pre Windows 10), ensuring they are fully patched against the Wannacry threat before using SMBv1 connections
I would like to add... Seeing the box asking for a user name and password suggests you are using password sharing. You will need to make an account on the other computers with your login details
OR
Turn off password sharing so you can access it.
Turn On or Off Password Protected Sharing in Windows 10 | Windows 10 Tutorials
Hey ARAMP1,
This is a long shot, but it looks like something I ran across the other day. See if you can manually access one of your servers by using \\pcname.local (i.e. \\MUSICSERVER.local)
Note:
1. If it connects, you should get a Credentials Window, which can take a few seconds to show up.
2. Enter credentials, but do NOT save credentials
3. Now try to manually access the server using \\MUSICSERVER
Here's my post about this - Network Share \\PCNAME vs \\PCNAME.local - Windows 10 Forums
Ive changed around so many settings I dont know what Ive done so far, so I decided to reinstal windows and start again.
I have 6 machines used for network render, and I need to manually transfer files all the time. I was getting so frustrated with network access from explorer being intermittent - even after doing network reset on all machines. The odd thing is - I could access the pcs by IP, but they either disappear from explorer or 'access denied'.
I solved this by making desktop shortcuts to the IPs (R-click new shortcut), and sticking these in a folder. Now I have access to all my render nodes, but the big question is - why does Microsoft keep breaking networking? It must be a deliberate strategy...
The whole mess was caused by the Wannacry mess last year, MS had in reality not changed the basic networking structure in quite a few years, (I will ignore Homegroup, as did most people, and likely caused it's demise).
Microsoft kept SMBv1 active due to its use in many Embedded linux operating systems used for NAS, TV and Media Devices,
They got around the emergency with Wannacry with a heavy handed solution, they simply disabled the use of SMBv1 in windows operating systems, which helped to protect the OSs until they could be properly patched, but totally FUBARed may systems that used non MS devices. There was even a timer that switched the SMBv1 protocol back off if you re enable it (that's gone in 1803)
This heavy handed approach has softened in the 1803 release but still needs some changes to services and the enabling of the SMBv1 protocol if you need it (most will as the old Network Browser system that dates back to NT3.5 still relies on it.)
The changes to services and reenabling of protocols have to be performed on all Windows devices and the system is not an instant fix, and may take a few reboots of all devices over time to fully "populate" the network with all devices