I see Network 2, Network 3 under Ethernet0 - Why?

  • Thread starter ronniejorgensen82
  • Start date
R

ronniejorgensen82

Hi all,

We have just build 3 new Windows Server 2016 on our VMware environment. they are all made from the same sysprepped image.

I am trying to work out why we see "Network 2, Network 3" under Network Connections > Ethernet0 (See picture)

1399706.png

I think they are called network connection profiles but not sure why it shows up as 2??

My colleague tells me he may have put 2 out of the 3 VMs in the wrong network on the VMware side and afterwards changed them.

All 3 VMs are Windows Server 2016

All 4 VMs have the same static route added in
1399707.png

All 4 VMs have the same version of VMware Tools 10.2.5.8068406 installed

IP config of a server that shows 2 network profiles

Windows IP Configuration

Host Name . . . . . . . . . . . . : SERVER
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet0:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : vmxnet3 Ethernet Adapter
Physical Address. . . . . . . . . : 00-50-56-88-6A-32
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.0.3.12(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.3.4
10.0.3.1
DNS Servers . . . . . . . . . . . : 10.90.2.50
8.8.8.8
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{72682DC1-D00F-46DA-9DEB-BF292B2BAB2E}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6ab8:38d8:2f:f5ff:fcf3(Preferred)
Link-local IPv6 Address . . . . . : fe80::38d8:2f:f5ff:fcf3%10(Preferred)
Default Gateway . . . . . . . . . : ::
DHCPv6 IAID . . . . . . . . . . . : 134217728
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-C8-E5-3A-00-50-56-88-6A-32
NetBIOS over Tcpip. . . . . . . . : Disabled

I have tried from an elevated command prompt to run set dev_mgt_show_nonpresent_devices=1 and then devmgmt.msc and go to view show hidden devices. It only shows one vmxnet3 Ethernet Adapter

Yesterday we uninstalled that adapter and scanned for hardware changes and while the multiple network profiles got fixed it only lasted a minute or so and then the second one popped back.

Does anyone have any ideas on what is going on?

Continue reading...
 
Back
Top Bottom