Verizon DSL black hole when trying to access isy

[paulw]

Sort of swallows you right up! Finding their commercial dsl at work is not the same as residential here at home!!!

 

Anyone have any success in getting through to the isy from a Verizon Westell 7500?

 

Generated certificate.

 

Set the isy for port 8443 (suspect verizon has 443 blocked)

Tried the 7500 forwarding 443 > 8443, and also 8443 > 8443 with the isy as the target. No joy.

 

Tried actual dynamic address:8443 no joy.

 

Tried no-ip host name set to redirect port 80 to 8443, no joy.

 

No problem with internal ip:8443.

 

Am I missing something?

[Michel Kohanim]

Hi Paul,

 

It's quite possible that IP pool assigned to you is not routable.

 

Does your Westell have remote admin functionality? If so, can you get to "it" remotely? If we can figure out that we can get to your router remotely, then the rest should be easy. If we cannot even get to your router, then unfortunately there's not much you can do except trying one of the portal partners (such as MobiLinc Connect).

 

With kind regards,

Michel

[paulw]

Michael,

 

Greetings, I appear on on that count.

 

Just tried yougotsignal.com which reported both 443 and 8443 are open ports at my address.

 

Paul

[paulw]

Verizon can be a royal pain, and their support usually much worse.

 

I'm just going to set it in bridge mode to a real router and be on with life. Will let you know if I have any other issues after doing that.

 

Paul

[paulw]

Some progress.

 

I'm able to remotely get past the router, installed the certificate and eliminated that error.

 

Now it just sits there spinning it's wheel getting no response. (looking for a response from the ddns site, ddns service is via no-ip.com)

 

FYI ISY-99 13.1.17 https port = 443

 

ISY set to port 443, accessing via https://ddns.name.xxx

[Michel Kohanim]

Hi Paul,

 

Thanks for the update. Now, please do forward to another port such as 8443. Please change ISY's HTTPS port to 8443 as well. I suspect that 443 is being used by your router's remote admin.

 

With kind regards,

Michel

[paulw]

Michael,

 

All is well. I was able to stay with 443. Turned out to be some type of issue with an air card which was on the client computer.

 

Thanks for all your help.