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

No network drivers?

I was using XG Home 17 on this PC- https://www.pondesk.com/product/Intel-E3845-4-LAN-1-COM-AESNI-4G-Fanless-Firewall-Router_MNHO-073 running Intel I211-AT Gigabit Ethernet ports.

It was fine until updating to 18 home. Then it stopped routing traffic and I opted to do a clean install of 18 home - 18.0.1 build 396

However, none of the network ports respond to ping to 172.16.16.16 (I've checked my client config to 172.16.16.2/24 and also /16 for the heck of it.) 

The console goes straight to Shell prompt rather than menu.

Response to what I believe is the request of the IP configuration is...

ipconfig locate protocol error simple network protocol

...which I take it to mean that it can't identify any of the network cards.

Can anyone shed light on the problem please. Is there a BIOS configuration I have to change to get it to work?



This thread was automatically locked due to age.
Parents Reply
  • You need to be  login into your mysophos page, not the free tools each time which as you said will generate a new licence.

    If you login to the mysophos page as I included the screenshot in a previous post on this thread you do not generate a new licence.

    The logic behind the upgrade page is a bit flawed because you can get the upgrade onto your machine automatically without signing a new agreement as part of the software release program.

     

Children
  • Thank you. I've found the Firmware Updated section as you indicated, and it looks like MR2 has been released.

    I'll try it this evening and see if that solves the issue.

  • I managed to get over the UEFI boot problem and boot the 18.01 home image directly... after a bit of a fight. ... so I didn't have to go back to 17 and then upgrade from there

    Then I was able to apply the patch to 18.0.2 and it stayed running.

    I'm still not sure exactly what the cause was, as I was trying various combinations. I also still don't know why the upgrade from 17 to 18 caused the problems it did.

    At least now I'm in a position where I can move forward.

    Thanks for all the help on this. I'm not sure whether to mark it solved or not, as I'm not sure what the actual solution to this was... except a good USB stick, patience and a good supply of coffee.

  • Becareful, MR-2 was a test release and not final.

    Ian