Cannot map to NAS drive in corporate system

Hi everyone -

OK. I need a second opinion.

I have a client who has a PC with W10 Pro that is a corporate system.
Therefore, some things are managed by Group Policy.

My problem is that the client wants to map a drive to the NAS but can't.
Seems that the SMB option (pointed to with arrow) is not displayed and can't see the LAN.



This picture is from another W10 Pro system that can see the same LAN.
Yes, Network Discovery is properly enabled. The NAS needs the SMB 1.

Any idea of how I can restore that option or force it via Command Line or PowerShell?
Can these settings still be checked off, yet inhibited via another method?

Many thanks!

Hi

I just got a NAS and was searching how to's. Came across this.

It has a Powershell command to enable SMBv1.0

https://support.microsoft.com/en-gb/...windows-server




Ken

Caledon Ken said:

Hi

I just got a NAS and was searching how to's. Came across this.

It has a Powershell command to enable SMBv1.0

https://support.microsoft.com/en-gb/...windows-server




Ken

Hi Ken -

It's a Linksys EA-9500 Router with an HDD hanging off the USB 3.0 port.
You would think that they would have support for the latest and more secure SMB protocols.

I really don't think the vendors care as most people won't ask.

I was reading about hardening devices, my Netgear router has a set Admin Id you cannot change and my IoT thermostat doesn't seem to have a userid or password. Eventually this will change. Things I will be asking about next time.

My new NAS allows you to set a range of SMB which is a different approach.

I'm going to try a few tricks from here but I don't think it will help.
Perhaps creating a temporary Administrator account...

Enable or Disable SMB1 File Sharing Protocol in Windows | Tutorials

I guess the powershell command failed?

Caledon Ken said:

I guess the powershell command failed?

The SMB1 was already enabled so doing it again had no effect.

I checked everything that I could. It is not possible to even see the Router (except for one time) and that is what I find most strange!
It's almost like a standalone, since the Router (and network name) are not displayed. However the PC is network functional.

Function Discovery Discovery Resource Publication (Running)

UPnP Device Host service (Running)

Strangest thing that I had seen, but the owner said the problem happened right after her company pushed 1809 (from 1803.)

I'm open to ideas, if any.

Just did battle with my own network, mobile devices couldn't use Guest network.

I'm sure you've tried power off and on the router. Will they let you sign into router to check settings?

You've likely already tried resetting network on troubled PC.

I used these commands to ensure something is lurking.

ipconfig /flushdns (Clear the dns cache)
nbtstat -RR (release and refresh NetBIOS names)
netsh int ip reset (reset ip settings)
netsh winsock reset (Reset Winsock Catalog)

Solved.

The system was clean in terms of the W10 configuration, but was blocked from accessing private LAN addresses as in 10.0.0.0 - what you would find behind the router.
Since the user was running McAfee Endpoint Security, I had no choice but to let that IT group provide a rule to allow access to the router - they nicely complied and pushed the rule to the client endpoint program.

Once done and the system rebooted, the "NAS" hanging off the router was visible and able to be mapped.

Many IP addresses use the 192.168. range. In a nutshell, it’s a “private” network. In other words, it can’t be accessed directly via the Internet.

There are three such ranges:

1. 10.x.x.x
2. 172.16–31.x.x
3. 192.168.x.x

So any time you ever see any of those used, it’s a private network. The McAfee Endpoint blocked a range of those.

That's it.

Cool. Glad you figured that one out.