Still can't access default IP!

Just to keep this going to the extent it helps the OP, I am having the exact same issue, and it's driving me a little batty...

Circumstances: (1) installed current version of firewall software successfully (as denoted by final line "password" after install sequence, and first boot and install of default config)... I've repeated this several times with bootable USB's from OSX, Windows and Ubuntu; (2) hardware being used is a Jetway Intel dual NIC Celeron N2930 Quad Core w/ 8GB RAM and a Crucial 250GB mSATA drive (tested and runs a variety of linux distro's just fine); (3) other data points: (i) it successfully configures the client connected to it with the DHCP server at 172.16.16.17 every time; (ii) I can SSH admin@172.16.16.16 w admin password indicating I've accessed the firewall, however I have to login to the https page to sign the license; (iii) I can successfully ping 172.16.16.16; (iv) confirmed gateway and DNS are 172.16.16.16 on the client; (v) have tried swapping the ethernet ports but connection fails from client; (vi) have tried accessing the https://172.16.16.16:4444 from Mac, Windows and Linux and failed every time and on every platform; (vii) have tried direct ethernet connection from Jetway/Sophos to the client and through a network LAN bridge; (viii) I've left it running for hours at a time to clear the "4 hours" referenced here multiple times; (ix) reviewed settings in BIOS of Jetway and all seem fine although open to brainstorms here on the CSM settings; (x) when an internet source is plugged into the second NIC ethernet port it passes internet traffic through to the DHCP client while still preventing access to the default admin IP.  I've read other reports of Jetway setups working with the Sophos XG firewall.

So what am I missing....  

Just to keep this going to the extent it helps the OP, I am having the exact same issue, and it's driving me a little batty...

Circumstances: (1) installed current version of firewall software successfully (as denoted by final line "password" after install sequence, and first boot and install of default config)... I've repeated this several times with bootable USB's from OSX, Windows and Ubuntu; (2) hardware being used is a Jetway Intel dual NIC Celeron N2930 Quad Core w/ 8GB RAM and a Crucial 250GB mSATA drive (tested and runs a variety of linux distro's just fine); (3) other data points: (i) it successfully configures the client connected to it with the DHCP server at 172.16.16.17 every time; (ii) I can SSH admin@172.16.16.16 w admin password indicating I've accessed the firewall, however I have to login to the https page to sign the license; (iii) I can successfully ping 172.16.16.16; (iv) confirmed gateway and DNS are 172.16.16.16 on the client; (v) have tried swapping the ethernet ports but connection fails from client; (vi) have tried accessing the https://172.16.16.16:4444 from Mac, Windows and Linux and failed every time and on every platform; (vii) have tried direct ethernet connection from Jetway/Sophos to the client and through a network LAN bridge; (viii) I've left it running for hours at a time to clear the "4 hours" referenced here multiple times; (ix) reviewed settings in BIOS of Jetway and all seem fine although open to brainstorms here on the CSM settings; (x) when an internet source is plugged into the second NIC ethernet port it passes internet traffic through to the DHCP client while still preventing access to the default admin IP.  I've read other reports of Jetway setups working with the Sophos XG firewall.

So what am I missing....  

I have the same problem as silverlight - I have a little micro PC, runs Windows 7 fine, just blew it away and loaded on Sophos XG.

I read about this 172.16.16.16 thing, thought it was a little odd but just thought "no worries, I'll just plug it into my layer 2 switch here, just add a secondary address on my old XP VM at 172.16.16.10 then log in and change the IP address..."

First thing I didn't realise was that it runs a DHCP server so after about 15 mins my wife gets cut off the VOIP conference call she was on (with people in the US, Asia and Australia!), loses her VPN and everything starts hanging. Turns out she just picked up an IP off this effing firewall and she's really mad at me. So I pulled out the network cable and got her sorted with an ipconfig/release&renew. Now I plugged my PC directly into the first port, got an IP, I can ping 172.16.16.16 fine but can I get to https://172.16.16.16:4444? Chrome just says unable to access the network.

Now I understand people might be blaming the NICs but Windows was running fine on this little thing and I can ping it fine. I just cannot believe Sophos make you jump through this stupid EULA acceptance thing via the web URL, why can't I do this at the console then set some "sensible" network parameters, if you are going to use something as stupid as 172.16.16.16 at least let me change it.

If I get this working, can I change the network config before doing the license activation, because trying to get this thing to talk to the internet means I'm going to have to configure a vyos router and plug it into my vmware lab? I mean this just seems really retarded to do it like this.

Anyway I'm getting to the point now where I'm just going to reformat and load on Smoothwall or something else and just not bother with this.

Has anyone got a fix for this?