RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    transfer roms though lan cat5 cable?

    Scheduled Pinned Locked Moved Help and Support
    cat5lanromstransfer
    23 Posts 8 Posters 5.9k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      Shadowblitz16
      last edited by

      actually my cable fell out of my rp3,
      but now it recognizes it and send packets to it but the rp3 doesn't send packets back,
      so I can't see the folders.

      1 Reply Last reply Reply Quote 0
      • stoney66S
        stoney66
        last edited by

        @Shadowblitz16 make sure you can ping the RPI from the windows machine. Open up cmd prompt and "ping 192.168.1.20" see if you get replies.

        Also if you have console on RPI run "ifconfig" make sure eth0 has the correct IP address.

        1 Reply Last reply Reply Quote 0
        • S
          Shadowblitz16
          last edited by Shadowblitz16

          under wlan0?
          it says that inet is 192.168.0.62 which is its wifi address.
          there is also lo which uses the 127.0.0.1 and enxb827ebb34f59 which has a inet value of 169.254.91.47

          also I tried pinging and I get no response

          uhh and I am getting a bit of it back
          Ping statistics for 192.168.1.20:
          Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

          mituM 1 Reply Last reply Reply Quote 0
          • stoney66S
            stoney66
            last edited by

            if you plugged in the ethernet cable then your interface will usually be eth0. wlan0 is your wifi interface.

            It sounds like enx is your RJ45 interface and only has a link local IP so it's not set.

            sudo ifconfig enxb827ebb34f59 192.168.1.20/24

            then ping should work.

            1 Reply Last reply Reply Quote 0
            • mituM
              mitu Global Moderator @Shadowblitz16
              last edited by

              @shadowblitz16 Are you sure your Wifi isn't connected still ?

              1 Reply Last reply Reply Quote 0
              • S
                Shadowblitz16
                last edited by Shadowblitz16

                @stoney66 yep that worked! thankyou so much!

                @mitu
                to my raspberry pi?
                ya it is I don't know how to shut it off without completely disconnecting though

                1 Reply Last reply Reply Quote 0
                • stoney66S
                  stoney66
                  last edited by stoney66

                  @Shadowblitz16 cool. You can disable the wifi from the retropie menu.

                  https://github.com/RetroPie/RetroPie-Setup/wiki/Wifi

                  Note that the changes you made for enxb827ebb34f59 will not be persistent on reboot. There is prob a setting in retropie menu for that, I haven't checked. The url you pasted above https://www.jeffgeerling.com/blog/2018/setting-static-ip-address-raspbian-jessie-lite-on-raspberry-pi will work, you just need to change eth0 to enxb827ebb34f59

                  1 Reply Last reply Reply Quote 0
                  • edmaul69E
                    edmaul69 @Shadowblitz16
                    last edited by

                    @shadowblitz16 it is really easy to connect pi to windows 7. Get a crossover cable and plug it into the pi and pc. After that on the pi exit emulationstation and in the terminal type sudo ifconfig. Look at the ip address for eth0. On the pc use the programs putty and winscp. Use that ip address you got from the pi in putty and winscp to login. Easy as pi.

                    edmaul69E 1 Reply Last reply Reply Quote 0
                    • edmaul69E
                      edmaul69 @edmaul69
                      last edited by

                      @edmaul69 transferring roms through ethernet is 1000’s of times faster. Any wireless connection is far too slow

                      1 Reply Last reply Reply Quote 0
                      • S
                        steptoe
                        last edited by

                        I first used Putty, but far too slow due to encryption. I then tried FileZilla, much much faster, but still use Putty to access the PI and run or edit some thinga via Putty through a console on the Windows desktop. N ever used wireless, far too slow and problems with connections as you've found out

                        https://www.raspberrypi.org/documentation/remote-access/ssh/windows.md

                        Transferring ROMs via FileZilla is about as fast as you will get over an thernet cable, which is what I use but I use cat6 cables

                        https://www.dexterindustries.com/howto/how-to-transfer-files-to-your-raspberry-pi-from-a-pc-computer/

                        1 Reply Last reply Reply Quote 0
                        • D
                          Davey92
                          last edited by

                          All i did on my retropie was enabled ssh and 1 wire turned on network discovery on my pc and it worked! With a cat 6 ethernet cable

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post

                          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.