Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 44 subscribers
  • Views 2223 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

Cannot connect to Port 4444 or 443 from VLAN on Port1

Alter Tech

Hello, Have an XGS 116 with configured VLAN's on Port1. Trying to get to https://x.x.x.x:4444 or https://x.x.x.x times out when on the VLAN.  I can ping all the VLAN devices and the default network devices successfully form the VLAN and vice versa.  Device settings are to allow https and ssh in those zones. 



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

    Hi  ,

    Have you tried accessing other LAN interfaces of the firewall?

    You can also try testing the accessibility using CLI:

    • For Powershell
      • tnc x.x.x.x -port 4444
      • tnc x.x.x.x -port 443
    • Example:

    If the TcpTestSucceeded is True then the port is open and should be accessible.

    If the TcpTestSucceeded is False, kindly check any NAT rules that could be a conflict with this traffic

    • This is only an example, but usually, we have a conflict if there is a NAT configured with the service as ANY Service

    Then make sure that the device access is configured as admin:4444 and userportal:443

    We look forward to hearing from you

Reply
  • 0

    Hi  ,

    Have you tried accessing other LAN interfaces of the firewall?

    You can also try testing the accessibility using CLI:

    • For Powershell
      • tnc x.x.x.x -port 4444
      • tnc x.x.x.x -port 443
    • Example:

    If the TcpTestSucceeded is True then the port is open and should be accessible.

    If the TcpTestSucceeded is False, kindly check any NAT rules that could be a conflict with this traffic

    • This is only an example, but usually, we have a conflict if there is a NAT configured with the service as ANY Service

    Then make sure that the device access is configured as admin:4444 and userportal:443

    We look forward to hearing from you

Children
No Data
Unfiltered HTML