@MDtar7 Im running out of ideas, but try enabling SMB 1.0 support on your PC. Its in Control Panel, Programs and Features, Turn Windows Feature On or Off and select SMB 1.0/CIFS File Sharing Support. Restart your computer and try it again.

@YFZdude Yes I tried turning it on. Really whatever I do makes no difference. I think it’s just something screwy in windows, I hate windows. Scraping the way previously described worked perfectly, thank you as usual mitu.

@mitu many thanks. fixed

Stupid question but I don't see it asked here: Did you enable/configure SSH in the Software Configuration Menu on the new install in the Pi?

Check the docs - https://retropie.org.uk/docs/SSH/.

it may be the problem of your router login panel ..you should reboot the router and then try again..

@dandy_j Can you run sudo rfkill unblock all (from the terminal, after exiting Emulationstation) and see if you can detect the wifi networks afterwards. Is your WiFi configured for 2.4 Ghz b/g or it's just 5Ghz ? The PI only has 2.4 Ghz capabilities.

@mitu +1 for you That's the easiest solution indeed! I always use this. It even works for annother RetroPie setup but not simultanous of course ;)

@rod419 said in Noob Dilemma: No IPV4 address/No SSIDs Showing up: Also I can't seem to SSH from my PC, regardless of what IP I use. Well, if there is no network configured it's not possible to use SSH to the PI, unless you have a wired connection. If you have one, then you first need to enable SSH, since it's disabled by default - use the raspi-config script (see here). Remember that the PI 3 only connects over 2.4Ghz, so if your access point only works in 5Ghz, then you'll not see the SSID. This happened to me the other day. Maybe the external wireless adapter has 5Ghz support and that's why it's able to connect. Here is a Wireless configuration guide for the PI - including command to scan for SSIDs and configure the wireless from command line.

All that I can suggest is to connect another device to the network port of the PC to see if the network connection is shared to that device correctly. Then at least you know if the Pi or PC is to blame. personally, when things like this take too long I give up, in this case I would just conenct the Pi directly to the router.

Common mistake :)

I just told my DHCP server to assign the same IP address to the Pi's MAC address.

It works perfectly, thanks a lot!

Anyone?

@hellska said in Dynamic IP address 'not stable': The power supply is 2Amp, is it weak for the WiFi to function properly? @hellska It probably depends on what else you have attached to you RPi, but the specs for RPi3 say 2.5A is recommended. Your issue reminds me the behavior of my RPi1 with an external Wifi dongle. I never confirmed it was caused by insufficient power, but the fact was I had a poor 1.5A power supply back then. Using scp (which is consuming bit of CPU btw) was causing my Wifi to disconnect many times.

Sorry it was me,one of the network cables had come out of the router,I have 3 routers you see but only one connects to the internet,the other 2 are used as hubs..;) Its been solved..

@neobium Please use the @+name-sign or click on reply so the user you might want to talk is mentioned. If the WIFI IP is the one you've setted in the config and you can't connect to the Pie via WIFI then your security key (=WLAN Password, WPA passphrase.... ) might be wrong. Please check this first. To varify use CLI and use ping command ping your router first ping 192.168.1.1 or via router hostname ping myrouter.ip ctrl+c stops ping command! or you can try wget command to download some files wget http://www.retropie.org.uk/ you will get index.html from retropie Or are you behind a company proxy and want to play some games while in work? ;) Or is your subnet mask the right one? Is your router setted to only pass trusted devices? Are you able to optain a connection via DHCP? if yes then use the method @hansolo77 and myself explained. Change the hostname with raspi-config and you can use any IP you want .

Hi, Couldn't pin point the problem with this, so I've done a new build. The kodi on this build is running at 10% idle. The only thing I can think off, is ive written a script which is cause kodi to sap up the cpu. Will just have to test as I go along to find what was causing it.

This fixed it for me. https://pi-hole.net/faq/how-do-i-set-a-static-ip-address-in-raspbian-jessie-using-etcdhcpcd-conf/