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

ip with a strange port on the captive portal

Hi,  strange that on the login screen the displayed IP of the captive portal is 172.16.3.254:8091, but I did not define this IP anywhere, and a have a rule to allow computers to access the internet without needing to login to the captive portal



This thread was automatically locked due to age.
Parents Reply Children
  • Hi  

    Now NTLM error disappeared, Based on last snapshot it seems this server traffic is passing via identity based rule which required end server or machine to be live users. (As traffic may be getting blocked as machine is not reflecting in live user list of XG)

    As of now you may check the current rule from which server traffic of Internet is passing and if above is the case then you may create a clientless user for this server or machine IP.

    OR Another way is to create IP based rule for this server on top to allow internet traffic and confirm the status.

  •  

    As the image below shows, the rule allows traffic from the server to pass, this is a lan-wan rule dedicated only to servers and is not based on identity,  so it is strange how it behaves

  • Thank you for your attention, it is already solved, there was a rule with identity above the exit rule for servers that created this bus