I cannot get my Raspberry pi to show up on samba please help

[supppp]

please help I am using an Alienware windows 10 laptop and the raspberry pi will not show up on the network they are on the same network too
i Model or other hardware: raspberry pi 3+
Power Supply used: micro USB to USB charger
RetroPie Version Used: 4.7
Built From: pre-made image from retropie
USB Devices connected:
Controller used:ps4 dual shock/Logitech USB keyboard
Error messages received: none
Guide used: I followed the retropie guild and many other youtube videos that I cannot find

[mitu]

Is your PI connected to the same network as your laptopn (Wi-Fi or Wired) ?
How are you trying to connect via Samba from Windows ?

[supppp]

@mitu I am on the same wireless network and I am going into files and clicking network to connect

[mitu]

Try opening Windows explorer and type the name of the share into the address bar - \\retropie or \\retropie.local. If that doesn't show up, then look-up the network address (IP) for your RetroPie by opening the Show IP menu in RetroPie and then type \\<RetroPie_IP in the address bar (replacing <RetroPie_IP> with the real IP address shown).

[supppp]

@mitu ok I will try that and look at yesterdays post by me the final fantasy games won't work

[blackshadow]

if you can access it with mitus suggestion it may be worth checking the instructions on this page afterwards as i had a case of my pi not showing on my windows 10 machine in network due to SMB 1.0/CIFS Client being disabled by default enabling it displayed my pi immediatly of note it was still accessable before by typing the ip or \retropie the system just didnt auto pick it up under network

https://www.asus.com/support/FAQ/1037477/

[mitu]

@blackshadow That's not recommended and it's not the proper solution - SMB1 was disabled for security reasons and Rasbian/RetroPie supports SMB2/SMB3 without any problems.

[supppp]

@mitu ok so use samba 2?

[supppp]

@supppp how do i enable samba 2

[Ashpool]

@supppp AFAIK it should be working ootb. As you said you are on the same wireless network: can you provide or verify the (local) IP Addresses for your Win Machine and the Pie? Does your Raspi has Internet Access?
I am simply asking, because I for myself had with various setups (Pi3B/3B+/4) and Retropie versions made the observation that sometimes DHCP ain't getting me any valid IP and I had to reboot various times 'till my router and the raspi communicated properly (1).
Are both in the same range (example: router 192.168.0.1, Win PC 192.168.0.<a> and Raspi also 192.168.0.<b>)? From your Windows PC, can you Ping your Raspi (Open a Console (cmd) and type ping <Raspis IP>)? Here is an example from one of my Windows PCs pinging a Raspi running RetroPie:

C:\>ping 192.168.1.21

Ping wird ausgeführt für 192.168.1.21 mit 32 Bytes Daten:
Antwort von 192.168.1.21: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.1.21: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.1.21: Bytes=32 Zeit<1ms TTL=64

[1] therefore I have switched to static ips some time ago (for my desktop pcs that was&is a standard procedure for me (at least for ip4, on my LAN ip6 is disabled), just make sure those ips are reserved for static in your routers setup))

[supppp]

@ashpool yes i can see the on my windows It just won't show up on the network

[supppp]

@mitu I have tried all of this it doesn't work

[mitu]

@supppp said in I cannot get my Raspberry pi to show up on samba please help:

@supppp how do i enable samba 2

There's nothing to enable, it's already included/enabled on both systems (Pi and Windows).

@mitu I have tried all of this it doesn't work

Check if you have Samba enabled on the Pi - use the RetroPie-Setup menu and go to Configuration / tools -> samba, then run the Install & Restart Samba.

EDIT: do test that your PI is accessible from your Windows system, as indicated by @Ashpool.

[Ashpool]

@supppp "It just won't show up on the network" -> Ok, just to clarify that one: Do you mean by opening the Network View with Windows Explorer? Then that is, at least on all of my systems, normal behaviour. Or did you mean that you cannot open it with the explorer, even if you enter the Pies Networkname or IP Address in the addressbar of the windows-explorer (like mitu said in the second post)? If thats the case, and Samba is enabled in retropie, and as you have said you can reach the Pi from windows... I confess to have no real idea to pinpoint the problem (Are you using only Win 10 build in security meassures,or are you using a 3rd party AV and/or Firewall, any settings done (be it firewall/network policies) that should matter? At least enabling/disabling network discovery on windows should make no difference (I can access the Pi from systems regardless of that setting)).

[YFZdude]

"It just won't show up on the network" -> Ok, just to clarify that one: Do you mean by opening the Network View with Windows Explorer? Then that is, at least on all of my systems, normal behaviour.

I agree that this is how my system behaves as well. The Network Explorer in Windows probably relies on some network advertising protocol that linux systems don't use to announce themselves by default. Even on Windows 10 systems you have to enable that setting in the file sharing settings.

[supppp]

@ashpool I cannot see the raspberry pi on the network explorer file using the IP address or the other way but I can create a file shortcut that shows it but I cannot use the shortcut for skraper

[Ashpool]

@supppp You've lost me there... how are you creating a shortcut if you cannot access the pi from within the explorer? Couldn't you (to get a usable workaround for your case) map a network drive or create a symlink instead? Btw. I am not a user of "Skraper", but ain't you supposed to enter the path to retropies config/romfolder from within skraper in the way \\<raspiIP>\<sambafolder> (example: \\192.168.0.42\configs )?

[supppp]

@ashpool yes I do not know how that works but I can create a shortcut but not see it on the network file

[supppp]

@supppp how do I create a symlink?

[Ashpool]

@supppp As you want to link a folder: (I think it is better to run cmd as admin in this case, as there my be some group policies preventing the creation of a symlink over network for regular users)-> mklink /d <path to link that is to be created> <path to target>
Example:

F:\TMP>mklink /d roms \\192.168.1.21\roms
symbolische Verknüpfung erstellt für roms <<===>> \\192.168.1.21\roms