That's not going to work, it's how CIFS/SMB works. You can't mount a host, just a share. Sure, the file browser shows you the available shares, but even on Windows (using Map Drive) you can't do that. Maybe there's another solution with an intermediary program that reads the shares and mounts them separately so you can see them side-by-side, but underneath mount will still only map each shared folder.

@hooperre Well, Microsofts considers it's insecure, so they must have a reason. I guess is mitigates the risk that someone inadvertently opens a guest only share and mistakenly runs something from it. https://support.microsoft.com/en-us/help/4046019/guest-access-in-smb2-disabled-by-default-in-windows-10-and-windows-ser

@Dwarfboysim thank you for your help, I did all the installation from the start and it goes well. have a nice day :)

@Efriim Then the problem is the Samba share and not the Pi. Restart Samba after you the USB is mounted and then re-try to copy the file to the share.

@moltke44 I think you've been bitten by this change in Win10 which disables the guest browsing of shares, specifically for Enterprise and Educational versions of the OS. That's why for me (Win 10 Professional) still works, but not for you. You can try the workaround described here, which I wouldn't recommend, especially if your computer is domain managed and there are security policies in place. Another option is to disable guest access in the RetroPie file sharing service (Samba), but that's a little more involved and it's not so straightforward.

@Link You can create a folder for the ROMs on the /media/usb0 partition, copy the contents of /home/pi/RetroPie/roms to it, then symlink /home/pi/RetroPie/roms to the folder on the HDD. Make sure you create a back of /home/pi/RetroPie/roms first, just in case. Or you can bind mount the folder over /home/pie/RetroPie/roms with something like mount -o bind /media/usb0/<Folder_name> /home/pi/RetroPie/roms

If you're not blocking the port yourself, check with your ISP. RetroPie doesn't come with any firewall rules configured (unless you did so).

Nothing?

@turnerl Because this is the easiest way to transfer your ROMs to the Pi system. Since this is a gaming dedicated system, it makes sense to make this operation as easy as possible.

@ericdave you should not edit that file but the autostart.sh. the file you edited is not meant to be user editable and will be overwritten.

I just ended up using a different method, winscp on Windows, I also just mount my USB directly now instead of transferring files cause I reimage so often

My microSD card became corrupt and I had to revisit this issue, and I just realized I never thanked you guys! Thanks for helping me twice!!!

Forgot to mention, both partitions are formatted in ext4 format. Not sure if that info was need lol but noticed i had not added it. Cheers

Yup, confirmed. Don't install the Control Block module from the Drivers list if you're not using it and updating with Retropie 4.3.5, because it looks for it and if not detected, initiates the shutdown sequence.

@darkbibble here's the module code. https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/supplementary/samba.sh#L31

Thanks for the help and suggestions. I figured there was a decent chance I'd need to reinstall... I shut Retropie down through the emulationstation menu, but I'll have to make sure I'm waiting long enough before unplugging. I have had to hard shut it off several times when games have hung, but that was rare.

@pawpie said in Samba share no longer working: 2nd issue- scraping images... What Scraper are you using ? If it's the default ES one then maybe you have the "user decides conflicts" option on. With Off it does the job for all games (for the systems you selected). Detailed info on Scrapers here.

now i have another problem, the data transfer from pc to rom directory is 10mbit but to my ex hdd its 60kb sec... what could be the matter ?