• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Hyper-V is puking

narzy

narzy

Elite Member
Oh please tell me someone can help.

We run a hyper-v server for labs and currently it is puking all over the place with remote users.

It works fine on the local network but VPN users can't connect to the machines when we try to load the hyper-v manager we get the following error. I've done some internet sleuthing but can't come up with anything relevant.

VPN users are set up to be on the exact same network as the internal network.

itvserror.png
 
patch tuesday but it worked fine last week. there were changes made to the server that broke it. we're trying to figure out what is wrong with the server and I'm trying to see if anyone has some ideas.
 
narzy said:
patch tuesday but it worked fine last week. there were changes made to the server that broke it. we're trying to figure out what is wrong with the server and I'm trying to see if anyone has some ideas.
Click to expand...

There is a fix for it available here :awe:
 
no haven't found the solution yet, checked the switches and firewalls doesn't seem to be any issues there. I don't have access to the event viewer I will see if the instructor will let me take a look there too.

We'd revert the changes if someone would have documented what they had done but the person who screwed it over doesn't know exactly what he did.
 
Strange problem. It may be better to restore from backups or re-do the Host OS install.

Are there other Hyper-V servers on the same network? Are these working OK?
If there aren't other Hyper-V servers, you could likely rule out external influences (router problems and such) by putting Hyper-V on a test computer and seeing if Remote Management works over the VPN to that second machine.
 
That error message is a generic message telling you that something interrupted network communication with your Hyper-V host.

Considering that this is only happening to VPN clients, my guess is that routing between the Hyper-V host and the VPN may be broken somewhere, or the VPN client is resolving the wrong IP for the Hyper-V host.

You can confirm this by running a network sniffer on your VPN client, and, if possible, on the Hyper-V server.

You may want to check the event logs on the Hyper-V server as well, but I doubt that they contain anything useful.
 
SolMiester said:
Snapshots before changes to VM's?, if still issue then the host. Any other VM's on same vSwitch?
Click to expand...

There are about 200 VMs on the server

Strange problem. It may be better to restore from backups or re-do the Host OS install.

Strange indeed. I don't think reinstalling the host is an option right now there are is a LOT of configuration that would need to be redone.

Are there other Hyper-V servers on the same network? Are these working OK?

There is another hyper-v server on the network but I don't have credentials to use it.

Snapshots before changes to VM's?, if still issue then the host. Any other VM's on same vSwitch?

Snapshots would restore the OS state but not the AD or ISA settings that were changed. Also this happened during a migration to new servers I don't even know if it is possible to revert all the changes that were made.

That error message is a generic message telling you that something interrupted network communication with your Hyper-V host.
I will run a network trace and see if I can see where it is breaking. We've looked at the DNS a bit but probably need to dig a little deeper. When we nslookup on the VPN to the hostname of the hyper-v server it resolves to the correct address.

You may want to check the event logs on the Hyper-V server as well, but I doubt that they contain anything useful.

You're right, we did look at the event log and they were pretty much useless. As would be expected if the line is broken between the VPN host and the hyperV server
 
no idea what their procedure was for the migration 🙁

what can I do to trouble shoot this to find out where it is failing.
 
narzy said:
no idea what their procedure was for the migration 🙁
Click to expand...
Nevermind. It doesn't really make any difference. The problem is either with the configuration of your Hyper-V host or with the networking external to the host.

As I noted earlier, you could test the external networking by throwing together a new test Hyper-V host.

Your statement about the migration implies that this new Hyper-V host NEVER worked with a VPN remote management connection, so it's not a matter of something having broken. It sounds like it didn't work from the start (after the migration). Is that correct?
 
Last edited:
I was under the impression that it worked for a short period but something else was terribly wrong with the network, I don't know what, but that had to get resolved. after that happened things went to hell and back.

I'm a lowly user I don't have access to the fancy stuff. I'm e-mailing back and forth with the instructor who is trying to work through the issue and providing some ideas and suggestions. A lot of what has been posted has been helpful it just hasn't nailed down the problem yet.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top