RailPro > RailPro Specific Help & Discussion

Difficulty with instillation

<< < (2/6) > >>

nortoneye:
So the answer was that my ISP does not automatically assign a "static IP" and without this I could not connect with RP.  Doing this solved the issue-not sure if this will come up for anyone else, but that was my problem.


jim

G8B4Life:
That is odd. Having a static IP address is definitely not a requirement for connecting to RE's file server. I'd been connecting to RE's file server with a dynamic IP address long before residential static IP addresses became the norm. It sound's like your ISP hasn't configured their servers properly. As it goes a static IP address is not usually handed out to residential customers unless they have VOIP or ask for it, usually providing a good reason however, I'm happy to see it fixed your issue and I've filed the report away in my mind for future use.


--- Quote ---I did the port 80 test and it;s open.

--- End quote ---

Did you use the UDP Test tool to check?

- Tim

nortoneye:
i did use the tool to test port 80, it indicated it was open, the ISP folks said it was not open on their router, so they reconfigured....the ISP support folks mentioned something about cable based internet which my son has (where I could connect)...cost me an extra 10 bucks per month to have a static IP assigned...kinda frustrating.  since RE does not require a static IP, I may see if port 80 was the entire problem and see if I can save the 10 bucks

G8B4Life:
I'm glad to see someone got some use of the tool.


--- Quote ---i did use the tool to test port 80, it indicated it was open, the ISP folks said it was not open on their router, so they reconfigured

--- End quote ---

There's a couple of ways to read what they said. When they said "their router" they could have meant the CPE (Customer Premises Equipment) router if they supplied one to you for your internet (many ISP's can remotely configure CPE that they have supplied) or most likely they could have meant the router at their end. Without knowing which tests in the test tool you ran and how you ran them there's a couple of things that could be going on.

1. Your ISP blocks inbound port 80 traffic.
2. Your ISP uses carrier grade NAT (Network Address Translation) and blocks inbound port 80 traffic.

By giving you a static IP address (sometimes called a public IP address in the case of point 2) what this allows them to do is to open the port up just for you and nobody else.

You can talk to your ISP again and ask them if you do need the static IP address or not. Tell them the Ring software you use communicates outbound and inbound via udp on port 80 (and it's fixed, the ports cannot be changed). They should be able to let you know from that information whether you do or not.

- Tim

nortoneye:
Tim,

the ISP support folks indicated the fiber optic network they have connects differently than a cable based network-we did try to open port 80 and connect with a dynamic IP, but it would not connect without assigning a static IP...don't know if this will be a problem with fiber optic based networks or not..I'll mention it to Tim Ring as well--thanks for your suggestions!

Jim

Navigation

[0] Message Index

[#] Next page

[*] Previous page