Forum Discussion

lojelo5's avatar
lojelo5
Superfast
12 months ago

Network card won't reconnect after update

Last night at around 12:55 hub5 rebooted it did a software update and since that update my akasa 2.5gb network card will not reconnect.

I have tried everything bar a pinhole reset but all I keep getting are these 2 errors

Now putting the Ethernet straight into the motherboard everything is fine, this only happened after the software update. I will phone VM later on to see if there are any issues within the network because no matter what I do the 2.5gb card will not acquiring a new IP or default gateway.

 

 

[MOD EDIT: Subject title changed for clarity]

  • lojelo5's avatar
    lojelo5
    Superfast
    12 months ago

    Just an update 

    I thought I would give this ago and it worked.

    I copied a few things over from the working Ethernet on the motherboard over to the properties on the akasa adapter i.e IPv4 address, Subnet mask and IPv4 default gateway at this point my PC blue screened so it could be an issue with either the motherboard or the adapter but after it rebooted it is now working again, bit of strange one though.

  • Client62's avatar
    Client62
    Alessandro Volta
    12 months ago

    When 1 computer does not work and all else does, it is the 1 computer that needs a Restart to force a cold boot causing a fresh DHCP request.  Be aware a pin hole reset of any VM Hub risks it reverting to the original firmware.

    • lojelo5's avatar
      lojelo5
      Superfast
      12 months ago

      @ Client62

      I know how it works hence me rebooting system right away but that did not work.

      No matter how many times I rebooted the PC or hub it wouldn't acquire a new IP like I have shown in the screenshots above. I tried many things but none worked, manually inputting the details was the only way. 

      The Ethernet port on the motherboard was fine that would connect no problem, it was the akasa 2.5gb network card that's the issue. I will remove all the details I put in manually and see if it acquires the details by itself if not there is a problem with the card hence it blue screening my PC after I entered the details.

  • cossie1's avatar
    cossie1
    Tuning in
    12 months ago

    Had the exact same issue (using Realtek 2.5Gb card).

    Tried rebooting the PC about 10 times, disabling / re-enabling the network card, rebooting the Hub 5, none of this worked.

    In the end I resorted to factory resetting the hub 5, now it is working again.

    Stuff like this should be fully tested before any updates are pushed to the Hubs

  • lojelo5's avatar
    lojelo5
    Superfast
    12 months ago

    @ cossie1

    I don't think they really care about the odd person having problems. It looks like it's sorted itself out I removed the manual settings and set it back to Obtain an IP address automatically rebooted the PC and it's connected perfectly fine again.

    • cossie1's avatar
      cossie1
      Tuning in
      12 months ago

      That wouldn't work for me, the only option was to reset to factory default settings and configure everything again.

      • lojelo5's avatar
        lojelo5
        Superfast
        12 months ago

        Don't worry I will be watching this. I have had a look inside system event viewer and there's quite a few errors within the network card drivers for some strange reason the driver had changed a couple of times. It started with a driver from 2019 then I found another event log with a driver from 2015!! then it reverted back to 2019 I have only had this device for just over a year so why would windows install an older driver over a newer one is beyond me.