Connection Issues to Hyper-V Based Server

[MrMDStreet]

Ok,

So Corero is hosted on a Hyper-V server.

 

when running "ping -t" the server sends a reply for about 20 packets and then times out for anywhere between 1 & 3. No other servers hosted have this issue. I have checked cables and they are all working fine. It just appears to be communication to and from this server.

 

It has been causing me a headache for 3 days now and I am constantly being hounded by our BM to get it resolved. Networking isn't my strong point so any help will be greatly appreciated. As idiot proof as possible would be awesome as well.

[plock]

Does the Corero VM use the same Virtual Network Card as the other VMs hosted on the Hyper-V Host?

[MrMDStreet]

Yes it does.

[SYNACK]

Whats Corero ?

 

Does your Hyper-V server have intel NICs, do you have the latest ones and are the virtualisation extentions turned on in them so the dodgey intel drivers can cope?

[koryo]

QOS or Bandwidth limitations imposed by the virtual switch? (a hunch - just reading the 70-410 now so may be a long shot)

[plock]

Corero is a finance package similar to FMS or Sage but far less complicated. Have you got NIC Teaming enabled and do you have multiple network connections plugged into the Host?

[MrMDStreet]

No NIC Teaming enabled and there are 3 additional connections in the host.

[plock]

Perhaps setup a new Virtual Switch with one physical connection and apply that Virtual Network Card to the new Virtual Switch... I had a similar problem which caused exactly the same thing, not with Corero specifically though. It was Broadcom adapters with teaming enabled (using Broadcom teaming software). Came down to the team needing re-creating in their software.

[MrMDStreet]

@plock It appears that the other 3 connections are part of a team so I cannot apply them as a separate switch. I have managed to attach one of the others displayed in hyper-v and the Ping has kicked up no losses so far. Now just to test it on the finance machines and other places on site.

 

I will keep you posted.

[MrMDStreet]

No such luck. There was me thinking it had worked.

[plock]

did you get this solved?

[MrMDStreet]

In the end. After 9 days of working around people to gain access to their computers and them calling in "outside professional ICT support" (who turned up on the day i had fixed it).

 

Turned windows firewall off on the server running the SQL database. Turned it off on the client machines. Made the users local administrators (at the recommendation of the outside professional ICT support) and then turned it back on for the server then the clients and it all began working again.