How is your host machine network adapter configured?

[Sonic007]

Hi,

 

I'm hoing someone can point me in the right direction...

 

So I have my domain controller and Sims server as HyperV servers.

These connect to the Internet via a virtual switch in HyperV, which uses the Host machines NIC.

These virtual servers connect to the domain and the Internet works fine.

 

What do you guys do with your host machine? Do you have it connected to the domain as well or leave it off domain?

 

I have always kept it off domain.

 

The problem I am having is getting the host updated with updates.

 

NIC1 on the host machine is set to DHCP.

If I try to change the hosts NIC1 to a static IP with correct default gateway and DNS I get a message saying "Warning- Multiple default gateways are intended to provide redundancy to a single network. They will not function properly when the gateways are on two seperate disjoint networks".

 

What is the best thing to do here?

 

 

Many thanks.

[mavhc]

If you do ipconfig on your host, what do you get?

 

Being on the domain is completely different to being on the same LAN

[Aprice]

I have hosts either on their own domain if using Hyper-V with S2D or if it just needs a domain.

 

Single hosts I would leave on a workgroup, off domain.

[slugshead]

Multiple adaptors in Lenovo hosts.

 

1 x IMM/xClarity whatever you want to call it on the motherboard

2 x 4 sfp+ cards

 

1 x with an internal IP (management)

2 x Bonded and switch end configured as trunk

1 x spare if I ever need it

 

2 x 2 bonded into SAN switches

 

Hyper-V virtual switch enabled, configured to use the lag group and VLANS set per VM

[Sonic007]

If you do ipconfig on your host, what do you get?

 

Being on the domain is completely different to being on the same LAN

 

 

Thanks mavhc.

This is what I get on the host's ipconfig:

 

Ethernet Adapter NIC1:

ipv4 address: 10.2.160.2

Subnet mask: 255.255.252.0

Default gateway: -

 

Ethernet adapter vEthernet (Virtual_switch_1)

Autoconfiguration IPv4 address: 169.254.189.169

Subnet mask: 255.255.0.0

Default gateway: 10.2.160.1

[DalekSec]

2 x 1GB Integrated NICs Teamed to 1 IP on our Host VLAN

3 x 10GB Add-In NICs Teamed to 1 IP on our Server VLAN

and another 3 x 10GB NICs Teamed to another IP on our Server VLAN

 

(3 x 10GB NIC Cards, each card has 1 Port in each team in case 1 card dies)

 

All cat 6a

 

Domain joined

[mavhc]

Thanks mavhc.

This is what I get on the host's ipconfig:

 

Ethernet Adapter NIC1:

ipv4 address: 10.2.160.2

Subnet mask: 255.255.252.0

Default gateway: -

 

Ethernet adapter vEthernet (Virtual_switch_1)

Autoconfiguration IPv4 address: 169.254.189.169

Subnet mask: 255.255.0.0

Default gateway: 10.2.160.1

 

Hmm, does the virtual switch itself need a gateway? Unlikely as it doesn't even have a real IP. Test that when no one needs to use the VMs

 

Do you have VLANS?

[Sonic007]

Nope, no VLANS. Small Primary school with just one host machine running a domain controller VM and Sims VM in HyperV.

[Davit2005]

It looks like you have gateway on wrong interface

 

vSwitch has self assigned IP but a specified gateway for the other interface somehow.

 

Ethernet Adapter NIC1:

ipv4 address: 10.2.160.2

Subnet mask: 255.255.252.0

Default gateway: -

 

Ethernet adapter vEthernet (Virtual_switch_1)

Autoconfiguration IPv4 address: 169.254.189.169

Subnet mask: 255.255.0.0

Default gateway: 10.2.160.1

Edited April 27, 2022 by Davit2005

[Sonic007]

Thanks everyone for your replies so far.

 

So there shouldn’t be a gateway set on the virtual switch?

 

I don’t want to mess anything up as at the moment both hyper v virtual servers are connecting to the internet fine.

 

But I do need to sort out the host somehow so it too can connect to the internet.

[TwistedHelixis]

I have a very similar setup to you. Host is not domain joined, no vlan, no nic teaming etc. I can check the settings on my server tomorrow for you and post back if you want.

[Sonic007]

That would be great. Thankyou.

[Davit2005]

Thanks everyone for your replies so far.

 

So there shouldn’t be a gateway set on the virtual switch?

 

I don’t want to mess anything up as at the moment both hyper v virtual servers are connecting to the internet fine.

 

But I do need to sort out the host somehow so it too can connect to the internet.

 

Is this a typo It looks like you have gateway on wrong interface, NIC1 has network of 10.2.160.0/22 but no gateway, virtual switch has APIPA assigned address but gateway is not needed, apipa addresses are not routable.

 

vSwitch has self assigned IP but a specified gateway for the other interface somehow.

 

Ethernet Adapter NIC1:

ipv4 address: 10.2.160.2

Subnet mask: 255.255.252.0

Default gateway: -

 

Ethernet adapter vEthernet (Virtual_switch_1)

Autoconfiguration IPv4 address: 169.254.189.169

Subnet mask: 255.255.0.0

Default gateway: 10.2.160.1

 

If it is a typo and you have the correct gateway on the Ethernet Adapter NIC1 then you could try pinging the gateway, pinging a upstream router, try pinging Google and see it it resolves IP etc.

Edited April 28, 2022 by Davit2005

[TwistedHelixis]

On my servers adapter settings

 

NIC 1 has fixed IP, subnet, gateway, DNS addresses

 

NIC 2 (Virtual_switch) doesn't have IP4 or 6 ticked in adapter settings, it just has LLDP & Hyper-V switch ticked.

[Sonic007]

On my servers adapter settings

 

NIC 1 has fixed IP, subnet, gateway, DNS addresses

 

NIC 2 (Virtual_switch) doesn't have IP4 or 6 ticked in adapter settings, it just has LLDP & Hyper-V switch ticked.

 

I think this is in fact where I've mixed things up.

The hosts NIC is set to DHCP whilst the Virtual Servers ipv4 is setup with IP, subnet and gateway.

 

What I will do is untick ipv4 on the virtual switch and give that IP address to the physical host's NIC. So long as I have LLDP & Hyper-V switch ticked in the virtual switch's properties then all should be ok I assume?