name resolution
-
This seems to be a common thing; GoOgle returns a lot of unsatisfactory info.
From my windows machine I can access the RetroPie by name (i.e. "RETROPIE") in file manager, if the RetroPie is connected to the network by ethernet.
If it is connected to the same network by wifi RETROPIE shows in the network list, but is not accessible. It is accessible if I type \192.168.1.x into the address bar.
Likewise, when using WinSCP I can login using "retropie" on ethernet, but must use the ip address on wifi.
The reason this is important is that I am setting this up for someone that I may loose contact with and they know nothing about computers, so I'm trying to make loading roms easy as pie.
Yes, I know how to use WinSCP; I know how to type the ip address. Samba seems to work just fine. The ONLY problem is making it easy for someone that doesn't know.
Is there a way to get name resolution to work over wifi?
-
@donbrew I have been successful connecting over different networks via SMB on Mac using;
smb://retropie.local
You didn’t mention it, but perhaps this name works in more situations?Another thought, and probably something you don’t want to hear is the fact that the Pi is and probably always will be a teaching platform. It is intended to be used as a tool to teach people (often kids) technology. We can’t help but applaud the efforts of everyone involved with RetroPie, from founders, devs and “official” people to the vast contribution by community members on the forums. But even with all of this combined effort, it is not like a commercial, turn-key platform. Yeah, it can be easy, but whether we admit it or not, it is still very complex and technical, and the first time something breaks (either by our own doing, after an update–whatever) it reveals how the apparent ease of use is built upon a very technical foundation. I would hesitate handing over a project without carefully setting expectations that it can come with a fair amount of tinkering.
-
This is not my first venture into linux, raspbian , rpi etc. I have been through having to setup smb in ubuntu when it was not included in the distro. SMB is working.
The oddity is that I have full access to the rpi on ETHERNET using the name; i.e. \retropie But, on WIFI access is only by ip number i.e.\192.168.1.175.
I have never encountered something like this in probably 15 distros on my rpi 1B.
I have seen MANY of the exact question when I GoOgle the problem. All of the answers are totally unhelpful; they all say : "use \192.168.1.175" or "use WinSCP". Those solutions DO work for somebody that is a bit tech minded; they don't work for somebody that can barely grasp drag n' drop in explorer.
The intended user is expecting to plug n' play and if they want to add a rom, just drag n' drop in explorer without calling me for directions.
There is no problem connecting, just in the path to connecting in WIFI. There must be some arcane line in some config file somewhere. I don't know why it would be different using eth0 or wlan0.
I know in LibeELEC somebody added a line to smb.conf that allowed the pi to become master, but would not let it talk to the other computers, that does not seem to be the case here.
BTW: the editor won't allow 2 slashes in front of the file, not a misprint.
I am using jessie with the new 4.9.35-v7+ kernel. -
BTW this is on a RPi 3B
-
SOLVED!
Edit /etc/samba/smb.conf
Global settings
dns proxy = yes
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.