Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

only getting onto remote slingbox from client running your server.exe in another state #63

Closed
sp222222 opened this issue Sep 13, 2022 · 5 comments

Comments

@sp222222
Copy link

It has been working for days (eight) and then it worked fine Friday night thru Sunday night.
(watched both NFL and then Men's USOpen tennis immediately after yesterday).
We added the script (friday evening) to boot up with PR and it worked all weekend.

So today I come home from work and the one slingbox that is not on my home network won't connect from my laptop downstairs.
I rebooted both my router and the remote (out of state) router. Now, I can only connect to that out of state slingbox using the desktop I have upstairs that is the server for all the slingboxes. I've changed nothing in 3 days. (Wasn't even home to change things anyways). I'm seeing no errors on slingserver python script when it starts on my desktop server. This is very confusing why it works on only one client.

Any ideas Gerry?

@sp222222
Copy link
Author

it works now again. not sure what changed.

@GerryDazoo
Copy link
Owner

Weird, firewall/routing issue? Do you have the program output from when it failed? I'd like to take a look.

@GerryDazoo
Copy link
Owner

Did you have your VPN turned on?

@sp222222
Copy link
Author

sp222222 commented Sep 13, 2022 via email

@GerryDazoo
Copy link
Owner

If there were no errors it means that the sever could talk out to all the slingboxes. So it would seem like something was blocking the incoming connections to the server. If only your parents was accessible then I would guess the firewall was allowing that port and blocking the other server ports. Double check you firewall that you have rules to allow connections for all your server ports.

You can verify the SSH connection is up by logging into either router and doing a
"netstat -an | grep ssh_port_number (whatever that was 39???)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants