I simply cannot get Firefly Client to connect with my Netgear ReadyNAS from outside my own LAN.
I have port forwarded 3689 both UDP and TCP. Is there a different protocol I should be using in the router?
One time, I did finally get it to bring up the password authentication screen by entering as the server myserver.dyndns.org/rsp/db but entering the known good pw failed and I was never again able to get that far.
I am using a Mac Client running OS X latest.
The clinet works PERFECTLY to access the Firefly Media Server as long as I use the local 192.168.10.54 IP address. But using the EXTERNAL LAN IP or the DynDNS domain name always fails.
What am I doing wrong??
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This seems to be an issue with your router NAT not allowing access to the right internal IP on the right ports.
As a first step, I would verify if you can see the ReadyNAS at all from the outside. Note your "external" IP and use a browser to access http://[external IP]:3689. You should get access to the admin section of the firefly server. If you password protected it (which is recommended), you'll get a box asking for your credentials.
If this doesn't work, the firelfy client is definitely not the problem and dyndns is also out of the picture. I would guess your router config is wrong.
If this works, do the next step and use http://[myserver].dyndns.org:3689 to see if you get the same result.
If this doesn't work, it is dyndns. If it works you might really have a firefly client issue - but I doubt that.
For me, the setup via dyndns works fine. I'm listening the music right now from my office.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have opened TCP and UDP port 3689 and pointed it to the NAS and I tried you first suggestions and it will not connect. Am I using the correct protocols? Are TCP and UDP enough or the right protocols on the port or should it be some other protocols??
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No, there is nothing special. TCP should do the trick. It is not a firefly client problem. Have someone help you with your router, e.g. in an appropriate forum.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Which version of FF do you use?
I downloade one just before christmas and the defaut port in that one was 9999, and if that's tha case for you too it wont help opening up 3689.
Look at the advanced config page of FFMS
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I simply cannot get Firefly Client to connect with my Netgear ReadyNAS from outside my own LAN.
I have port forwarded 3689 both UDP and TCP. Is there a different protocol I should be using in the router?
One time, I did finally get it to bring up the password authentication screen by entering as the server myserver.dyndns.org/rsp/db but entering the known good pw failed and I was never again able to get that far.
I am using a Mac Client running OS X latest.
The clinet works PERFECTLY to access the Firefly Media Server as long as I use the local 192.168.10.54 IP address. But using the EXTERNAL LAN IP or the DynDNS domain name always fails.
What am I doing wrong??
This seems to be an issue with your router NAT not allowing access to the right internal IP on the right ports.
As a first step, I would verify if you can see the ReadyNAS at all from the outside. Note your "external" IP and use a browser to access http://[external IP]:3689. You should get access to the admin section of the firefly server. If you password protected it (which is recommended), you'll get a box asking for your credentials.
If this doesn't work, the firelfy client is definitely not the problem and dyndns is also out of the picture. I would guess your router config is wrong.
If this works, do the next step and use http://[myserver].dyndns.org:3689 to see if you get the same result.
If this doesn't work, it is dyndns. If it works you might really have a firefly client issue - but I doubt that.
For me, the setup via dyndns works fine. I'm listening the music right now from my office.
I have opened TCP and UDP port 3689 and pointed it to the NAS and I tried you first suggestions and it will not connect. Am I using the correct protocols? Are TCP and UDP enough or the right protocols on the port or should it be some other protocols??
No, there is nothing special. TCP should do the trick. It is not a firefly client problem. Have someone help you with your router, e.g. in an appropriate forum.
Which version of FF do you use?
I downloade one just before christmas and the defaut port in that one was 9999, and if that's tha case for you too it wont help opening up 3689.
Look at the advanced config page of FFMS