Guest User!

You are not Sophos Staff.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 9 replies
  • Answers 2 answers
  • Subscribers 27 subscribers
  • Views 19191 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

Admin UI inaccessible after changing LAN IP

Per-OlofLitby

So I installed XG as a VM, activated and registered and everything looked okay. I then logged in via SSH and changed the LAN IP to be on my local subnet and now the web admin interface is unreachable.

It responds to pings and I can log in via SSH and the system has come up with the new IP address:

PortA     Link encap:Ethernet  HWaddr 00:50:56:B4:89:F7
          inet addr:192.168.2.250  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::250:56ff:feb4:89f7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:15013 errors:1 dropped:1 overruns:0 frame:0
          TX packets:1625 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1123238 (1.0 MiB)  TX bytes:142087 (138.7 KiB)
          Interrupt:19 Base address:0x2000

But I can't get to the web UI. I've tried restarting the Tomcat service as well as a reset to factory defaults but it does not help. A port scan shows it's not listening to any ports other than 22, 25 and 53, i.e port 4444 is not up.

Is there anything I can do short of a reinstall? I'd hate to have to go through the kludgy activation procedure again...



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

    Per-OlofLitby

    try to enable the system access from console using the command:

    system appliance_access enable

    Then try to access the UI. If it works, change the IP from UI.

    Regards

  • 0 in reply to lferrara

    Unfortunately that didn't help. I performed a factory reset and then issued the command you suggested but it's not responding on 172.16.16.16 either.

  • 0 in reply to Per-OlofLitby

    Hi Per-OlofLitby, 

    You may need to check if its the issue with the device or network setup. 

    Steps to troubleshoot your issue.

    1. Connect the console cable to the device or if it's a VM access the console directly. Please refer KB 123197

    2. Check the network configuration,  Go to option  4 console> show network interfaces 

    3. Connect the interface/adapter of the XG and configure your LAN port of your system onto the same network as the Xg's interface address

    e.g. XG LAN ->172.16.16.16/24 | System LAN --> 172.16.16.18/24 GW 172.16.16.16

    4. If you wish to connect via WAN , by default it is disabled and can be enabled by the command console > system appliance_access enable

    Access it /configure it then you may disable appliance access again using the command console>system appliance_access disable

    5. Check the traffic on the XG if it is able to receive the traffic from your system address..

    command console> tcpdump 'port 4444

    If there is no incomming traffic while accessing the device then try with another port and try again. You may manually configure the port using option 1.

    6. If there is a traffic but the device did not respond then you may need to provide the dumps to troubleshoot further. 

    Let me know this does not work out for you

     

     

  • 0 in reply to Aditya Patel

    Thanks

    There is definitely something fishy going on and it makes me pull my hair out in frustration. Here is some more information which may help.

    Host: HP DL360e gen8, ESXi 6.0, 2 of 4 built in NICs assigned to XG VM as E1000E adapters.

    XG;

    LAN 192.168.3.1 connected to Unifi switch

    WAN connected to Mikrotik router DHCP server. IP 192.168.2.212. Output from ifconfig:


    SFVH_VM01_SFOS 16.05.4 MR-4# ifconfig
    GuestAP   Link encap:Ethernet  HWaddr F2:B4:E4:F1:96:97
              inet addr:10.255.0.1  Bcast:10.255.0.255  Mask:255.255.255.0
              UP BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

    PortA     Link encap:Ethernet  HWaddr 00:50:56:B4:09:BD
              inet addr:192.168.3.1  Bcast:192.168.3.255  Mask:255.255.255.0
              inet6 addr: fe80::250:56ff:feb4:9bd/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:7827 errors:0 dropped:0 overruns:0 frame:0
              TX packets:714 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:804756 (785.8 KiB)  TX bytes:185079 (180.7 KiB)
              Interrupt:18 Memory:fd4a0000-fd4c0000

    PortB     Link encap:Ethernet  HWaddr 00:50:56:B4:A0:5E
              inet addr:192.168.2.212  Bcast:192.168.2.255  Mask:255.255.255.0
              inet6 addr: fe80::250:56ff:feb4:a05e/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:7571 errors:0 dropped:10 overruns:0 frame:0
              TX packets:704 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:1091827 (1.0 MiB)  TX bytes:91520 (89.3 KiB)
              Interrupt:19 Memory:fd3a0000-fd3c0000

    imq0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
              UP RUNNING NOARP  MTU:16000  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:11000
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

    ipsec0    Link encap:Ethernet  HWaddr CE:D3:11:2A:15:82
              inet addr:169.254.234.5  Bcast:0.0.0.0  Mask:255.255.255.255
              inet6 addr: fe80::ccd3:11ff:fe2a:1582/64 Scope:Link
              UP BROADCAST RUNNING NOARP MULTICAST  MTU:16260  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

    lo        Link encap:Local Loopback
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:65536  Metric:1
              RX packets:26823 errors:0 dropped:0 overruns:0 frame:0
              TX packets:26823 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:15306739 (14.5 MiB)  TX bytes:15306739 (14.5 MiB)

     

    I can successfully ping and connect via SSH to the LAN address but the web UI on https port 4444 doesn't respond.

    I have enabled access using the command mentioned in post #2 but no response on https port 4444 via the WAN address.

    The device is not listening on port 4444, as shown by a port scan.

  • 0 in reply to Per-OlofLitby

    Per-OlofLitby

    why you are not accessing XG from PortA?

    On WAN side, Web interface is disabled so you wont connect to XG. Connect to LAN ip and then enable the HTTPS service on wan zone from Administration > Device Access.

    Regards

  • 0 in reply to lferrara

    Er, if you had read my post you would have seen that the web UI is not responding on any port. Only reason I tried port B was to determine if the web server is even running, which it apparently is not. Unless 4444 is hidden from port scans.

  • 0 in reply to Per-OlofLitby

    Per-OlofLitby,

    web UI is not allowes on WAN zone by default.

    Try to reset the configuration, enable https even on WAN side and change the IP from UI.

    If necessary, recreate/redeploy the VM.

    Regards

  • 0 in reply to lferrara

    Luk,

    I hate to be sounding like a PITA but you aren't being helpful. Again, please read my posts and you will find that I have already done all of what you suggest. Why bother responding if you aren't offering anything new?

    And yes, for the heck of it I have already redeployed twice, first from the ISO and then from an OVF - and in both cases I could not even access the basic pre-activation page.

    No question that this is somehow related to my environment but I fail to understand how. I had an activated VM which I simply vMotioned to a different host and that borked the admin UI. None of the other VMs on the host are acting up, yet it must be something in the new host that causes this.

  • 0 in reply to Per-OlofLitby

    Per-OlofLitby said:

    Luk,

    I hate to be sounding like a PITA but you aren't being helpful. Again, please read my posts and you will find that I have already done all of what you suggest. Why bother responding if you aren't offering anything new?

    Just few words: DO NOT FORGET this is a community forum where normal users give their help each other. Also I read all the time the forum before giving any answer.

    Check tomcat logs from advanced shell and open a ticket with Support.

    Reply here the status of the ticket and what the resolution is.

    Kind Regards

Reply
  • 0 in reply to Per-OlofLitby

    Per-OlofLitby said:

    Luk,

    I hate to be sounding like a PITA but you aren't being helpful. Again, please read my posts and you will find that I have already done all of what you suggest. Why bother responding if you aren't offering anything new?

    Just few words: DO NOT FORGET this is a community forum where normal users give their help each other. Also I read all the time the forum before giving any answer.

    Check tomcat logs from advanced shell and open a ticket with Support.

    Reply here the status of the ticket and what the resolution is.

    Kind Regards

Children
No Data