Now this is odd. I don't know, but it may be that my external IP has been blocked somehow. So, to get things working so my wife could do her banking, and I could have peace of mind with filtering the other networks, I decided to change the setup order/config a little. So now instead of being: Modem->XG-> Networks A, B, C, D I am set up: Modem->OnNetworks router-->XG-> Networks B, C, D, E \> Network A The XG is getting it's WAN address as part of Network A, and Network E is the old Network A, but with the schema changed as to not confuse routing. (ie Network A: 192.168.233.x, Network B: 192.168.133.x) I kept Network A in place as I have hard coded IP's on many devices inside my network and it was just easier in the long run to keep it and change the LAN on the XG. After this change I can get to the bank site on Network A, as expected and tested earlier in troubleshooting. Fired up a computer on Network E (XG LAN primary) and all of the sudden the login for the site comes up as expected as well. This leads me to believe that there may be an issue where the bank may be blocking my external IP (the ISP gave a new IP address to the OnNetwork router, but my IP with XG has remained the same for the last couple of years). All this to say, I now don't believe the issue is related to the XG at all. I just wanted to post this follow up in case anyone else comes across a similar situation.
↧