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 Not Answered
  • Locked Locked
  • Replies 24 replies
  • Subscribers 41 subscribers
  • Views 72029 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

How to install, setup, and configure XG Home on Hyper-V

Rob Moorhead

Hi,

I am trying to install XG Home Edition on Hyper-V. I followed the Virtual Appliance documentation as far as I could because it only covers VMWare. I created a VM using the minimum requirements and installed XG Home no problem. When it is up and running I see a command prompt with a menu system to use for configuration. The document says you should connect to 172.16.16.16:4444 to use the GUI but the computer hosting the VMs is running 192.168.10.xxx. I'm assuming that the IP my VM host has is incompatible with the firewall and cannot display the firewall GUI.

What do I need to do next so I can configure everything required? Is it possible to change the firewall so it uses 192.168.10.xxx so I can access the firewall GUI? Should I just do everything from the command line? What is best practice in setting up this firewall correctly?

Thanks,

Rob



This thread was automatically locked due to age.
  • 0 in reply to Rob Moorhead

    Rob Moorhead said:

    I received a reply on this port so would be the LAN port.

    By this, do you mean that you were able to access the Sophos XG web admin page? That's really the only way to know for sure that this was the LAN port.

    Assuming that was in fact what you got, any luck today?

  • 0 in reply to NashBrydges

    I didn't attempt to access the web admin page as I had ran out of time. I'm assuming that if I can ping 172.16.16.16 successfully that it will be an non-issue to access the web page. At the time I was testing, the WAN side was not connected to anything so there wasn't much point in trying until I have time to connect my cable modem to the server. I would still be able to see the web page but would be unable to do anything without internet connectivity. I could not get a ping reply on the other port so the built-in NIC must be the LAN side. I will continue when I get home after work today.

  • 0 in reply to Rob Moorhead

    Today I started up my server and began focusing on my Dell's WAN NIC. I disabled the LAN NIC and started checking for internet connectivity. I found that I didn't have internet access when I actually should. I disconnected the cables from my switches and traced everything out again. Now when I test the WAN NIC, I have internet access. When I checked the Network settings at the firewall's device console, I now had an IP address on the WAN side.

    With my laptop connected directly to the Dell's LAN NIC (enabled), I got to the web console and activated without any issues this time. I was able to synchronize my license as well and now the full console is exposed to me. So I finally made it through this step of the process.

    I created a couple of Windows clients and they are connected to the LAN switch. Each individually is able to ping the firewall at 192.168.20.1 but they cannot ping each other. Also, neither client has access to the internet. That will be a topic for another posting if I need help. There is plenty of reading to do before posting here.

    Thanks again Nash! Thanks to everyone that responded!

  • 0 in reply to Rob Moorhead

    what is the IP address of your gateway?

    XG115W - v20.0.2 MR-2 - Home

    XG on VM 8 - v20.0.2 MR-2

    If a post solves your question please use the 'Verify Answer' button.

Unfiltered HTML