@Dashrender said in Hyper-V Guest - Unidentified Network:

@pchiodo said in Hyper-V Guest - Unidentified Network:

@Dashrender I totally agree, and if this was a required production server, I'd be right on board. This particular server is not required for production, and I have moved its load to another Hyper-V server. Yes, I would like it back in the mix for load balancing and as a backup, but I still would like to take a little time to try and nail down the exact issue and solution before I just wipe it and reload.

Right - but you missed the part about how this is possibly not beneficial to your company.

Like you, my 2003 server isn't in production either, I'm trying to make a CYA fully working/tested backup to put into the safety deposit box. Fixing the boot problem fully doesn't really help my company in any way since I have a usable solution for the boot issue. Fixing it takes me away from doing something of real value for my company, the same goes for you and solving this issue.

In the end, you and I both personally gain by having additional knowledge we didn't have before, but what we don't know is if that knowledge will have any outward value in the future. While your situation has a higher likeliness of having future value, people are still deploying Hyper-V 2012, and it's likely a very similar setup probably exists in Hyper-V 2016. My situation is completely different in that 2003 is old, does booting in a completely old manner - using P2V that's a mostly dead situation (very little P2Ving done anymore, most of it was already done), so I have very little chance of ever using this knowledge in the future.

Agreed! In my particular case, I can see this happening again. We will likely not move off Server 2012 for the next 2-3 years depending on how fast our 3rd party apps adopt server 2016. This being the case, having a solution that takes minutes vs hours would be very valuable.

@Dashrender I totally agree, and if this was a required production server, I'd be right on board. This particular server is not required for production, and I have moved its load to another Hyper-V server. Yes, I would like it back in the mix for load balancing and as a backup, but I still would like to take a little time to try and nail down the exact issue and solution before I just wipe it and reload.

@JaredBusch That's really using a sledgehammer when a scalpel should be sufficient. I'd really like to find a resolution in case this comes up again. nuke and reload is a last resort IMHO.

I'm back to this problem. I moved the load from this server to another server so I could further investigate. I think I found the issue, but not a resolution.

In Device Manager, I still have two rogue entries:

Hyper-V Virtual Ethernet Adapter
Microsoft Hyper-V Network Switch Default Miniport

Both of these have the following error:

This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)

An object ID was not found in the file

In PS the Get-VMNetworkAdapter - ManagementOS and Get-VMSwitch both come back with no results, yet they are listed in Device Manager. I can disable them in DM, but it does not resolve the issue. DM does not let me remove them, and Remove-VMSwitch and Remove-VMNetworkAdapter have no effect.

Any ideas?

VMQ has already been disabled. That was a standard when I loaded these boxes.

As soon as I remove the virtual switch, NIC2 comes back online, and can be pinged from the network. It appears this issue is on the host level.

OK, so now I have dissolved the team again, removed the virtual switch, configured one of the physical adapters with a static IP and then have created a new virtual switch with only the one NIC. So as it stands, the management NIC is NIC1 and the Virtual switch NIC is NIC2.

When I set the static on NIC2, it immediately connected to the network as normal.

As soon as I recreated the virtual switch, NIC 2 on the physical box changed to Unidentified network, and of course, the VM has the same issue.

So when NIC2 bound the host to the virtual, something went haywire.

Still struggling..... ugh

@pchiodo said in Hyper-V Guest - Unidentified Network:

Yeah... I've tried all of the above, and the VMs still come up with Unidentified Network. I have a number of other HV Hosts configured the exact same way, and none of these have this problem.

I've rebooted the host several times, and had already changed NLA to delayed start on both the host and the guests.

At this point, I'm dissolving the team and removing the virtual switch, I'll then recreate the team and the virtual switch and reattach the guests, and see where I'm at.

Well, that didn't pan out. Same problem...

Oh, and I have 2 DCs, so it should see one of them almost immediately

Yeah... I've tried all of the above, and the VMs still come up with Unidentified Network. I have a number of other HV Hosts configured the exact same way, and none of these have this problem.

I've rebooted the host several times, and had already changed NLA to delayed start on both the host and the guests.

At this point, I'm dissolving the team and removing the virtual switch, I'll then recreate the team and the virtual switch and reattach the guests, and see where I'm at.

I have a Hyper-V Host server with 4 NICS running Server 2012 R2

1 NIC is reserved for host management and the other 3 are configured in a NIC Team used exclusively for VMs. This config has been working just fine until this weekend when we had an extended power outage.

After bringing the host server back online, I restarted the VMs, but now they all get an Unidentified Network error and cannot see the LAN.

The host server is fine and has full connectivity.

These VMs are setup with static IPs and this particular LAN does not have a DHCP server.

My googlefoo has failed me and I cannot find a solution.

Let me know what other info might help in determining the problem. Any help you all can provide is greatly appreciated.

Thanks!

OK, after dealing with real work issues, I was able to get back to this. Installed per Scott's instructions and everything is working as expected.

Thanks for the help! I'm sure I'll need more as I delve into the Linux world.

@scottalanmiller said in Rocket Chat on Ubuntu - Help please:

First thing, I would not use Ubuntu 16.04. That's not horribly old, but it is not current. Ubuntu 16.10 is current and what we have just tested this install on two weeks ago and had it work. It's unlikely that 16.04 is the issue, but there is no reason to be troubleshooting that on top of everything else. With Ubuntu you always want to run current as they don't have an LTS product (they have LTS labels, not LTS products.) So for production, you always need to be on current if you need full support unless you are dealing with software that only locks to semi-random old versions (which is an indicator to avoid those products on Ubuntu in general.)

Upgrading now - stay tuned

@scottalanmiller said in Rocket Chat on Ubuntu - Help please:

That address is the loopback. So it will be pingable even if the networking stack is offline.

I'm pinging it from another WS on our LAN and getting a response.

A little background - I am a Linux N00b, so this is all new to me.

Here's what I've done so far:

Setup a new VM running Ubuntu 16.04.1 LTS, and this all seems fine. I have been able to login and take root control.

I then attempted to do a snap install of the rocketchat-server, and get the following error after the installation process completes:

error: cannot communicate with server: Post http://localhost/v2/snaps/rocketchat-server: dial unix /run/snapd.socket: connect: connection refused

and leaves me at the prompt

I have configured a static IPv4 address, and can ping the address

Any ideas on how to address this issue?

Thanks!

@scottalanmiller said in DuoLingo Challenge:

The clock is in my wallet??? How would anyone even get a clock in their wallet? How is this even helpful? LMAO

I think this is just another sign that SW as a whole is ailing. Time will tell, but I would guess their market penetration won't improve, and will likely diminish, especially in Europe.

@JaredBusch

If I'm reading this right, you're out of pocket for over $20,000 a year if you have something major? WTF - How can they expect anyone to be on the hook for $20K/year for medical. unless you needed major surgery, you could get a heck of a lot of preventive, and incident based care for those dollars. Extrapolate over 5 years, and my god man, that's a house!

@mlnews

I'm ready now:

Getting ready for 2017 Budget Review - Woo Hoo /s