I have a running Sophos XG Home with FW v17.5.13_MR-13 on Windows 2012 Hyper-V that I use to evaluate XG. It's working well without issue.
When v18.0.1_MR-1-Build396 went to GA, I decided to update. The update went well and successfuly converted the configuration to v18.
What I noticed immediately was I can't ping 172.16.16.16 and can't access the web admin portal; but DHCP server service is working as my test workstation was able to get an IP address from it, 172.16.16.17.
So I went to the console and did some ping test. Ping to the workstation from XG via PortA failed, the same also with ping test to the router (GW) via PortB. I also tried other troubleshooting suggestion in the forum but nothing seems to work.
So to eliminate the possibility of a configuration conversion issue resulting to my problem, I downloaded the Hyper-V VHD of v18.0.1_MR-1-Build396 and created a new VM from it (still using my Windows 2012 server) and I got the same result/issue.
Then I tried to do it again but now on my Windows 10 Pro workstation. Created a new VM (Gen 1) using a copy of the same v18.0.1_MR-1-Build396 VHDs but this time it worked. I can ping and able to access the web admin portal.
I also tried to create a fresh VM using v17.5.13_MR-13 VHD on the Windows 2012 Server and it's OK.
So it appeared that there are compatibility issue with Windows 2012 server and v18.0.1_MR-1-Build396.
Can anyone from Sophos can confirm this?
This thread was automatically locked due to age.
