in reply to Re: Socket programming Help (updated)
in thread Socket programming Help

Thank you for your help Hauke, I originally had the address 0.0.0.0 in there, but that didn't work either. The "server" computer is running Windows, but the raspberry's are running Raspbian, and they are NEVER on the same network. I have it set up for testing even that they are on an external network, so I have NEVER seen it work. :-(

The program running on Windows with ActiveState 64 bit Perl, is running fine ( no warnings or errors, even with strict and warnings on ) but the script on the raspberry's just time's out every time... It never prints "Connected to socket".

I will try the Wireshark you mentioned see if that gives any insight. Maybe it's just that sockets aren't what we need, Ideally we would want something like Teamviewer or RDP but they don't run on ARM Raspbian without extensive tweaking...

  • Comment on Re^2: Socket programming Help (updated)

Replies are listed 'Best First'.
Re^3: Socket programming Help (updated)
by haukex (Archbishop) on Apr 19, 2016 at 22:01 UTC

    Hi Kelicula,

    Ok, well two more ideas:

    Do the scripts work when both are run locally on the same Windows machine? (maybe also try running both server+client together on the RPi for good measure)

    Is the Windows firewall configured to allow incoming connections on that port?

    Regards,
    -- Hauke D

Re^3: Socket programming Help (updated)
by stevieb (Canon) on Apr 19, 2016 at 22:08 UTC

    From the Pi: telnet your_servers_external_ip_addr 7777. If that fails to connect, you've got a firewall or NAT issue.