Can't get my-sky.com to work

I recently signed up to get the account brew.my-sky.com. I think it has been set up on the my-sky end OK, I just seem to be missing something on my end.

My setup: my local IP address is 67.128.8.74

Router (wireless) is 192.168.1.1
Forwarding ports 80, 21, and 8245 to the Observatory Computer, 192.168.1.10.
Router runs wireless through a bridge to the observatory

Observatory Computer, running ACP, is 192.168.1.10
ACP has Web and FTP servers enabled on ports 80 and 21, respectively. ACP is running.
No-IP program (DUC v4.0.1) is running. It looks different from the ACP help page since it has moved from v2.2.1, but it seems to be running correctly. I don't see the logging widget with messages as shown in the ACP Help. It shows brew.my-sky.com as an enabled host. It is using client brew:rdenny@dc3.com. It indicates remote IP is 67.128.8.74 (my local IP address). Images attached. I assume that the computer running the No-IP program defines the target for brew.my-sky.com.

Observatory computer and my-sky.com information was set up a couple of weeks ago, plenty of time for DNS propagation.

From my home computer (192.168.1.133, on the same network as the Observatory), I can access the ACP server via address 192.168.1.10. I get the usual login screen, then the ACP web page. All normal.

From my Home computer, or any other computer, I cannot access brew.my-sky.com. I get a timeout error.
From Home Computer, ping to brew.my-sky.com times out.

From Observatory computer, DUC program, use Tools/Check Open Port Tool. This brings up a web page where I can specify my IP (defaults to my 67.128.8.74) and a port (I enter 80). The remote server somewhere then tries to access port 80. This check fails, for connection timing out. Port 21 also fails.

Don't know what to try next:(

Hi Brew,

I cannot access brightskies.my-sky.com from my inside-the-house computer either. It will connect via my LAN address. This is just what you've experienced. From my office I can connect to brightskies.my-sky.com. So I believe that when your client computer is behind the router, you have to use the LAN address 192... Someting about going out to and coming back in from the Internet is not permitted.

By the way, I could not connect to your observatory computer from my web browser, and i was not able to ping brew.my-sky.com though the DNS resolved the IP address correctly. See attached image. See if you can reach my observatory computer and get a login screen.

I use v2.2.1. On all the options screens for no-IP, I have none of the boxes or checkboxes filled in, except the one for the account, which is brightskies.my-sky.com and the password, that Bob registered.

It looks to me like you've done everything right but for that one thing - whatever that is. Is there any issue with the bridge?

Interesting. Seems like I should be able to access the system from within my home network; I don't know why that would be any different.

I cannot access brightskies.my-sky.com. I tried it typing in the address into Firefox, as well as by the link on your message. Does ACP need to be running to get a response?

I also cannot ping your site, although ping indicates it is at address 66.44.36.178.

Odd - why is your work computer able to access the site? I have tried accessing mine from outside computers with no luck. Seems like yours works like mine, except that your office computer works.

All good questions.

You probably could not access my observatory because I have recurring problems with my network adapter dropping the connection. At this time I can't access my observatory from the LAN either. I have to go out to the computer out there and disconnect and reconnect the adapter.

I have googled and tried a hundred different "fixes" for this and nothing seems to set it right. I don't know if my trouble is at the observatory end (though I think so) or at the router. Something appears to be timing out, but it's not the "power saving" feature. Oh well. You can try to connect anytime again. It'll be successful if it's up and running. And yes, ACP has to be running - it's the server.

You also might try changing the http port to some other number like 8080. Remember to change the port forwarding on your router, too.
Speaking of that, you have to address my observatory as brightskies.my-sky.com:8080. Duh! That will help.

I am on RCN.

Have a nice holiday, Brew.

I have verified that your name is resolving to the correct IP. Dick's suggestion is a good one. Remember to change the port in ACP and also the port forwarding in the router. What makes this crazy is that some routers let you cross-route ports where the publicly visible port is different from the port on the inside destination system.