Network Discovery Won't Stay Turned On

cloud_dog

AndyPix wrote: »

Another thought , A recent update might have disable SMBv1 .. or V2
So, open an elevated command prompt and type the following to re-enable it ..

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb10 start= auto

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb20 start= auto

Then reboot

note : SmbV1 is the attack vector for spreading the most recent malware through your network, so ideally you dont really want legacy kit that relies on this

Did this....no joy.

cloud_dog

Annoyingly, in Windows Explorer both the Logitech Media Server and the ReadNAS show up under the 'Network Locations' but, then that is probably using a different protocol to CIFS/SMB.

esuhl

I've skim-read this and I'm drunk, but...

When using Windows (SMB) shares across multiple computers, I'm pretty sure you need to make sure that you have set up the same Windows username/password on both devices.

If you are sitting at computer A and try to access computer B, your login details from A will be used to log in to B. So you may need to add a new user on B with the same username/password as you use on A in order to be granted access.

I've never used Windows HomeGroups or UPnP, so maybe it's different with them enabled...

Also, I've always found (Unix-based) NFS more reliable than (Windows) SMB. You can install NFS drivers in Windows if you want to try NFS shares instead.

cloud_dog

esuhl wrote: »

I've skim-read this and I'm drunk, but...

When using Windows (SMB) shares across multiple computers, I'm pretty sure you need to make sure that you have set up the same Windows username/password on both devices.

If you are sitting at computer A and try to access computer B, your login details from A will be used to log in to B. So you may need to add a new user on B with the same username/password as you use on A in order to be granted access.

I've never used Windows HomeGroups or UPnP, so maybe it's different with them enabled...

Also, I've always found (Unix-based) NFS more reliable than (Windows) SMB. You can install NFS drivers in Windows if you want to try NFS shares instead.

Hi

I'm trying to access a share on the NAS (life used to be straightforward but now....not). My PC user name/password is also set up on the NAS. For the share/mapped folder I was trying to access it has guest read-only configured with my user configured for updates (add/delete).

I can access the share quite happily from another laptop but not from my PC (access used to be hit n miss recently but now it just seems unable to connect to it no matter what.

I am unable to browse to the share or indeed across the home network from this PC as Network Discovery is turned off (am unable to turn it on or for it to stay on).

Thought Network Discovery (being off) was the problem but proved that the other laptop can access the share with it turned off also.

Thought it may be user ID/password related so have re-created all that.

Will try NFS (am open to anything). If I install the drivers I am unsure how I connect via NFS or SMB from the PC. I know I've set up the share with equal access rights for both CIFs and NFS but (as stated) unsure how to utilise NFS rather than CIFS?

EDIT: Ok, I see from Google, I might need a utility and / or mount the shares

debitcardmayhem

Try deleting your adaptor or search for changing a network from public to private...its microsofts way to make you love them...just about every second update causes problems like this in 10.
Maybe here https://forums.moneysavingexpert.com/discussion/5551314

cloud_dog

debitcardmayhem wrote: »

Try deleting your adaptor or search for changing a network from public to private...its microsofts way to make you love them...just about every second update causes problems like this in 10.
Maybe here https://forums.moneysavingexpert.com/discussion/5551314

Hi

Network & Sharing Centre show the network as 'Private'.

AndyPix

Try resetting tcpip stack and winsock ..


Open elevated command prompt


netsh int ip reset
netsh winsock reset


reboot and try again..


We will get there in then end

cloud_dog

I'm sure (without having any actual knowledge of this) that the inability to 'browse' to network locations/devices and or add a 'Network Location' just have to be related.

If, when mapping the drivce, I click on 'Browse' I get the error 'Network Discovery' is not turned on. If I try to add a Network Location (all in Windows Explorer), I get the pop-up window which shows 'Network' but then there isn'y anything else listed and I cannot expand anything or navigate (double click etc).

AndyPix

Ok, more things to try (Just keep going till its fixed)


type services.msc into search bar and press enter.
Make sure "workstation" is running and set to start automatically ..


Next thing to try :


Go into system, then , next to "computer name" click "change settings"


You will see "to rename ... etc etc" - next to this, click change.
You wil then see "member of" and it will likely be a workgroup called "WORKGROUP"


Change that to something else , eg TEST


Reboot computer once this is acknowledged


Go back into system and change "TEST" back to "WORKGROUP"


Reboot and try again


let us know

cloud_dog

AndyPix wrote: »

Try resetting tcpip stack and winsock ..

Open elevated command prompt

netsh int ip reset
netsh winsock reset

reboot and try again..

We will get there in then end

You're very persistent. :T

Just giving it a go.