Another Super Frustrated Windows 10 User Not Able to Transfer Files Via Samba Share

[1984]

This USED to work, but something changed in Debian and or Retropie, but with workarounds(enabling things that are disabled by default in newer versions of Debian/Retropie, changing settings,etc) it used to be able to be made to work again. But for for years and years no workaround or setting change I have tried is getting this working anymore.

There are literally dozens of forum posts on this subject with dozens of proposed fixed and NONE have worked for me.

For years and years my workaround has been to use a computer running Linux to either access the SD card directly or access Retropie over the network which still works like a charm even with no credentials.

I would like to be able to add and remove files from Retropie from Windows. I hate being forced to have Linux installed on a computer because it refuses to work in Windows.

What I have tried........

-Enable SSH and Samba on my Raspberry Pi 4
-Connecting the Raspberry Pi via ethernet
-Turning my Windows firewall off
-Enabling SMB 1.0 support in Windows. Yes! I already know that Retropie SHOULD support SMB 2.0 and SMB 3.0 and that enabling SMB 1.0 is a bad idea, but doing this AT LEAST got Retropie to show up in my network.
-Trying to connect to the Samba share using the IP address of my Retropie install rather than \RETROPIE

YES! I am sure that...........

-My computer and raspberry pi are on the same network and in the same IP range
-I CAN ping my Raspberry Pi from my computer and get a response.
-I have enabled and double checked that Samba is installed and active in my Retropie install
-My Windows firewall is not active.
-My router firewall is not active

No matter what I have tried I CANNOT connect to Retropie.

\RETROPIE =Windows cannot access \RETROPIE -The forum is not showing double back slashes, but I promise that I am using double back slashes.

\<ip address of Retropie>= Windows cannot access \<ip address>

Type IP address into the browser= <ip adress> refused to connect.

Like I said, literally dozens of users having this issues and it gets resolved in 1 of three ways

1. Something I have already tried and had fail works for someone else.

2. The OP just figures it out, but never states what actually worked or it was something I have already tried

3. (Most common scenario) The responses start to amount to "Duh I don't know why you are having issues. It works fine for me" and the trail goes cold.

I've pretty much just accepted that this is NEVER going to work again and I'm mostly just venting my weapons grade frustration over it, but......

If anyone has any ideas for getting this to work in Windows THAT I HAVEN'T ALREADY TRIED I would be greatly appreciative and highly willing to try anything and post my results.

[ExarKunIv]

@1984 just to help start figuing out whats going on,

can you get in with SSH or WinSCP

[mitu]

What Windows edition are you using ? Please also provide the rest of the info asked in https://retropie.org.uk/forum/topic/3/read-this-first.

[1984]

@ExarKunIv

Yes and yes.

So it looks like WinSCP is the best current work around.

Still frustrating that it inexplicably stopped working natively in Windows years and years ago and no one seems to know why.

[ExarKunIv]

@1984 that is odd for sure

what version of windows are you using if you want more help with getting your samba working again

[1984]

@mitu

Raspberry Pi 4
Standard issue Pi 4 power supply(first party)
RetroPie v4.8 Released March 14, 2022
retropie-buster-4.8-rpi4_400.img(prebuilt)
No USB devices
8bitdo SN30 pro+
"Windows cannot access \RETROPIE"
NA
NA
NA
NA
NA
Double click on the "RETROPIE" item under network in Windows Explorer

[mitu]

@1984 Which Windows edition are you using - Home/Professional/Enterprise/Education/etc. ?

[1984]

@ExarKunIv

This is actually Windows 10 Lite from Ghost Spectre.

My wife has a fool version of Windows 11 on her laptop.
I'll try it from there and report back just in case my version of Windows is missing something critical.

[stoney66]

@1984 also you could ssh into your PI and run tcpdump to even see if your windows machine is attempting to connect, pending tcpdump is installed.

e.g.

sudo tcpdump -nni any port 445

Also you should check if 445 is even listening on the PI itself

netstat -an | grep 445

[1984]

@stoney66

pi@retropie:~ $ sudo tcpdump -nni any port 445
sudo: tcpdump: command not found
pi@retropie:~ $ netstat -an | grep 445
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN
tcp6 0 0 :::445 :::* LISTEN

STREAM CONNECTED 16445

pi@retropie:~ $

[stoney66]

@1984 ok at least the service shows as listening. You would have to install tcpdump it looks like. sudo apt-get install tcpdump

[Trainman52]

I've also noticed that the samba access disappeared with the new version of Retropie. My workaround is is click on "This PC" in Windows Explorer and then select "Map a Network Drive" from the ribbon menu. The path is \ip of retropie]ROMS. So far it has worked flawlessly.

[stoney66]

@1984 Did you happen to see this thread?

https://retropie.org.uk/forum/topic/29661/samba-shares-stopped-working-after-recent-windows-10-update/24

I know it doesn't help, but I fired up my windows10 system and it worked fine. I am running windows 10 home.

[Darksavior]

@1984 Altered versions of Windows usually remove too much stuff for my tastes. Reproduce the problem on an unmodified version.

[cdaters]

I don't mean to come across disparagingly or anything. Are you sure your Pi is connected to the network?

Did you pull down any Windows updates lately? I know that Windows 10 has issues connecting to NASs that aren't on the same level of SMB. Microsoft has turned off SMB 1.0 some updates ago because they don't trust you to be secure in your networking. Check your SMB settings and enable 1.0 if that is turned off...

[mitu]

@cdaters said in Another Super Frustrated Windows 10 User Not Able to Transfer Files Via Samba Share:

Check your SMB settings and enable 1.0 if that is turned off...

@1984 said they already enabled it.

[navi87]

Ive been using samba on windows 10 for years without issues.

Also, if you have installed a firewall on your pi recently, that could be blocking. i think port 445 is for samba. have a google, u can find it out easily.

I would also double check the service status of smbd on your pi via command line, maybe the service cant start?

Maybe check from another device to see if you can access it. Because at the moment you have no idea if the issue is with windows or with your samba service.

Orrrr.....access your pi via Firezilla on windows using SSH to transfer your files.