Admin UI inaccessible after changing LAN IP

Question

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...

lferrara · Answer

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

Aditya Patel · Answer

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