Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 26 subscribers
  • Views 6304 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Issues getting to Login Form "The requested URL was rejected. Please consult with your administrator. Your support ID is: ####################"

Amos Burkepile

Sometime in the last week I've gotten the attached message when trying to log into my credit union behind my Sophos XG firewall. I attempted to set up rules to bypass filtering/etc for the site, and have had no luck getting past it. I even set up a trial (ie old license) of UTM 9.x and as of yesterday was getting the same message with that system as well. I blew away my configuration and started from scratch and am still getting the same error, so I restored my backup (saved time with some of the other minutia of my setup). 

 

I used a simple $20 router in place of the Sophos XG/UTM and was able to get to the site just fine so I know it is not my ISP/Switches/Cookies/Browser cache. (Also I get this message across all machines, all OS's and all Browsers).

 

As you can see from the other attached picture I have my internal LAN allowed to go anywhere with IPS/Traffic Shaping/WEB Filtering/Application control turned off for my LAN.

 

What am I missing? Is there something in the way that Sophos software is doing MASQ that has broken this?

 



This thread was automatically locked due to age.
Parents
  • 0

    I forgot to mention, in case anyone else can try behind their XG device, the url is: https://homebank.psecu.com/

     

  • 0 in reply to Amos Burkepile

    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.

Reply
  • 0 in reply to Amos Burkepile

    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.

Children
No Data