wade May 24, 2013 Author May 24, 2013 Side note: when I opened up the telnet port (23) I can see it just fine. Does that mean comcast is blocking 9900 or somehow blocking incoming requests altogether?
Brian Ward May 24, 2013 May 24, 2013 You need the Apex on the same port you opened on your router. 80 and 25 are always blocked on a home-grade internet connection (they're the ports for HTTP and SMTP). The router just forwards the request as-is. It doesn't recast the request from port 9900 to port 80. So if you opened 9900 you need to set your Apex to respond on 9900. URL will be: http://<yourdomain>.no-ip.com:9900/
wade May 24, 2013 Author May 24, 2013 I thought I had done that right, but guess not. That did it! Thanks! Now to change the admin password so someone doesn't reconfig my outlets on me. :p
Origami May 25, 2013 May 25, 2013 Did you open the port on the router, Wade, redirecting TCP packets there? It sounds like you did but maybe there's something wrong in the setup? Unfortunately, I don't have a COMCAST router so I don't know what you're facing. As for updating the dns service provider whenever there's an IP change, try a software client that runs on a PC that's always connected to your home network (if your router doesn't have additional services). Doing just a short search, this page was found on dyndns' site (oh, the irony of it all). http://dyn.com/support/clients/
Origami May 25, 2013 May 25, 2013 ^^Ha. I didn't read the rest of your thread. I'm glad that you got the port opened up.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now