Windows can not access \\192.168.x.xxx

I have Windows 10 home which is updated to the latest version.

Here’s the problem.

I have a raspberry pi3 running retropie which is on my network via WiFi.
I have an ancient optiplex 740 running Windows 10 home

Initially I was running Windows 7 and I was able to access it by typing either
\\192.168.x.xx
Or
\\RETROPIE

I upgraded from win 7 to win 10 and still had no issues.

I then wiped my hard drive and reinstalled win10 using the utility in the settings menu.
Ever since then for some reason I cannot get windows to access the pi3.

If I go to the address bar and type in \\192.168.x.xx I get the generic cannot access error window
If I go to the address bar and type \\RETROPIE. I get the generic error window
I can even see the silly thing under my network connections.
I click it and get the error window.

If I go to command prompt and ping \\192.168.x.xx I get a reply
If I use winscp instead of Windows I can access it no problem.

What gives with this? It’s been driving me insane.

Tackett1980 said:

I have a raspberry pi3 running retropie...

...wiped my hard drive and reinstalled win10 using the utility in the settings menu.
Ever since then for some reason I cannot get windows to access the pi3.

Welcome to Ten Forums Tackett1980.


What version of Samba does your Raspberry Pi3 support? If it is only version 1, then you may need to enable the 'SMB 1.0/CIFS Client' in Windows Features. This is disabled by default in a clean install of Windows 10.



Turn Windows Features On or Off in Windows 10

Bree said:

Welcome to Ten Forums Tackett1980.


What version of Samba does your Raspberry Pi3 support? If it is only version 1, then you may need to enable the 'SMB 1.0/CIFS Client' in Windows Features. This is disabled by default in a clean install of Windows 10.



Turn Windows Features On or Off in Windows 10

Hello thank you for the reply.

To my knowledge and what I can find on the google, the pi3 supports samba share 1.0

However I did try as suggested without any results. Still getting the same error.

By trying to contact to an IP that is the PC you need to connect to a share is 192.168.1.45\\sharename

Tackett1980 said:

However I did try as suggested without any results. Still getting the same error.

Check your Windows Features again and make sure the Client is enabled (not the Server). If that's OK, open a command prompt and type:

NET VIEW \\192.168.x.xx

obviously, using the correct IP address, not 'x.xx'. By the way, 193.168.xxx.xxx addresses are a Private address range, only accessible from within your own network. There's nothing to be gained by hiding it with 'xx'. Almost every home router appears with an IP address of 192.168.1.254 on its internal network, for example.

The above command should produce a list of shares available on the server who's IP address you gave it. You should be able to connect to a share by typing \\192.168.x.xx\<sharename>

Bree said:

Check your Windows Features again and make sure the Client is enabled (not the Server). If that's OK, open a command prompt and type:

NET VIEW \\192.168.x.xx

obviously, using the correct IP address, not 'x.xx'. By the way, 193.168.xxx.xxx addresses are a Private address range, only accessible from within your own network. There's nothing to be gained by hiding it with 'xx'. Almost every home router appears with an IP address of 192.168.1.254 on its internal network, for example.

The above command should produce a list of shares available on the server who's IP address you gave it. You should be able to connect to a share by typing \\192.168.x.xx\<sharename>

Yes, I’m aware those are internal addresses. I wasn’t really hiding it just trying to truncate the information for clarity purposes, I apologize if it had the opposite effect.

I can confirm that samba 1.0 client only is enabled.

If I type ‘NET VIEW \\192.168.2.75 i receive an error

“System error 53 has occurred.”
“The network path was not found”

If I type ‘NET VIEW \\RETROPIE’ I receive an identical error.

Again, thank you all for your assistance so far.

From what you have said so far it sounds like the W10 PC is now set up correctly and it should work. Do you have any 3rd-party AV that may be blocking the connection?

The only thing left to suggest is to run the Network Troubleshooter in Settings > Network & Internet > Status.

If that doesn't work, then try the 'Network reset' link at the bottom of that page. NB: you will have to set up your WiFi connection again after that, so make sure you have the security key handy.

Bree said:

From what you have said so far it sounds like the W10 PC is now set up correctly and it should work. Do you have any 3rd-party AV that may be blocking the connection?

The only thing left to suggest is to run the Network Troubleshooter in Settings > Network & Internet > Status.

If that doesn't work, then try the 'Network reset' link at the bottom of that page. NB: you will have to set up your WiFi connection again after that, so make sure you have the security key handy.

What would be an example of third party AV? As far as I know, no. The pi is connected via WiFi and my pc is connected via Ethernet to the same network and that’s all.

I’ve ran the troubleshooter and it gives me no answer, cannot identify a problem.

I have reset my network settings twice already with no effect.

I just tried and I can ping it.
I can access via winscp

Can not access via windows explorer.

Tackett1980 said:

What would be an example of third party AV? As far as I know, no.

an example would be Norton, are you just using what came with win 10

oscer1 said:

an example would be Norton, are you just using what came with win 10

Yeah just using what came in Windows. No other applications.