Jump to content

14 posts in this topic

Posted

Hello,

 

I have just noticed something strange on one of my servers - each NIC has the normal assigned IP addresses that I have configured, then there is an extra one, which always ends up one of the 169.x auto-configuration addresses. I have looked through the configuration and there is definitely only one IP address assigned to each NIC.

 

Any ideas? This is the output from ipconfig:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Administrator>ipconfig

Windows IP Configuration


Ethernet adapter VLAN5 Wireless:

   Connection-specific DNS Suffix  . : thegellfamily.internal
   IPv6 Address. . . . . . . . . . . : 2001:470:6a2d:2:ccdb:3750:3d83:eb1
   Link-local IPv6 Address . . . . . : fe80::ccdb:3750:3d83:eb1%16
   IPv4 Address. . . . . . . . . . . : 172.16.32.13
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   IPv4 Address. . . . . . . . . . . : 169.254.227.68
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . : fe80::20c:42ff:fea8:758%16
                                       172.16.32.1

Ethernet adapter VLAN4 Data:

   Connection-specific DNS Suffix  . :
   IPv6 Address. . . . . . . . . . . : 2001:470:6a2d:1::ffff
   IPv6 Address. . . . . . . . . . . : 2001:470:6a2d:1:713e:dd8a:93c9:5143
   Link-local IPv6 Address . . . . . : fe80::713e:dd8a:93c9:5143%13
   IPv4 Address. . . . . . . . . . . : 192.168.32.239
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   IPv4 Address. . . . . . . . . . . : 169.254.190.36
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . : fe80::20c:42ff:fea8:757%13
                                       192.168.32.1

Thanks in advance,

 

Tony

Share this post


Link to post
Share on other sites

Posted

169.254 is APIPA -- can you please post output of ipconfig /all

like this

C:\Windows\System32>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : i5-w7
   Primary Dns Suffix  . . . . . . . : local.lan
   Node Type . . . . . . . . . . . . : Broadcast
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : local.lan

Ethernet adapter Local:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
   Physical Address. . . . . . . . . : 18-03-73-B1-0D-D3
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:470:snipped::666(Preferred)
   Link-local IPv6 Address . . . . . : fe80::1a03:73ff:feb1:dd3%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.100(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 2001:470:snipped::1
                                       192.168.1.253
   DHCPv6 IAID . . . . . . . . . . . : 236454771
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-39-96-D8-18-03-73-B1-0D-D3
   DNS Servers . . . . . . . . . . . : 192.168.1.253
   NetBIOS over Tcpip. . . . . . . . : Enabled

C:\Windows\System32>

Share this post


Link to post
Share on other sites

Posted

  1. Output of ipconfig /all
    C:\Users\Administrator>ipconfig /all
    
    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : Server
       Primary Dns Suffix  . . . . . . . : thegellfamily.internal
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : thegellfamily.internal
    
    Ethernet adapter VLAN5 Wireless:
    
       Connection-specific DNS Suffix  . : thegellfamily.internal
       Description . . . . . . . . . . . : vmxnet3 Ethernet Adapter #3
       Physical Address. . . . . . . . . : 00-0C-29-19-AA-85
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:470:6a2d:2:ccdb:3750:3d83:eb1(Prefer
    red)
       Link-local IPv6 Address . . . . . : fe80::ccdb:3750:3d83:eb1%16(Preferred)
       IPv4 Address. . . . . . . . . . . : 172.16.32.13(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : 03 July 2013 19:07:54
       Lease Expires . . . . . . . . . . : 06 July 2013 21:48:56
       IPv4 Address. . . . . . . . . . . : 169.254.227.68(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . : fe80::20c:42ff:fea8:758%16
                                           172.16.32.1
       DHCP Server . . . . . . . . . . . : 192.168.32.239
       DNS Servers . . . . . . . . . . . : 192.168.32.239
                                           192.168.12.240
                                           192.168.32.1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Ethernet adapter VLAN4 Data:
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : vmxnet3 Ethernet Adapter
       Physical Address. . . . . . . . . : 00-0C-29-19-AA-7B
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:470:6a2d:1::ffff(Preferred)
       IPv6 Address. . . . . . . . . . . : 2001:470:6a2d:1:713e:dd8a:93c9:5143(Prefe
    rred)
       Link-local IPv6 Address . . . . . : fe80::713e:dd8a:93c9:5143%13(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.32.239(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       IPv4 Address. . . . . . . . . . . : 169.254.190.36(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . : fe80::20c:42ff:fea8:757%13
                                           192.168.32.1
       DNS Servers . . . . . . . . . . . : 2001:470:6a2e:1::ffff
                                           2001:470:6a2d:1::ffff
                                           192.168.12.240
                                           192.168.32.239
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Tunnel adapter isatap.{A884C28C-8F4D-45F3-A20A-14AA09850EDD}:
    
       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 Local Area Connection* 9:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    
    Tunnel adapter isatap.thegellfamily.internal:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : thegellfamily.internal
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    
    C:\Users\Administrator>
    

Share this post


Link to post
Share on other sites

Posted

Failover Cluster Node ? This is normal for active/passive clusters.

Share this post


Link to post
Share on other sites

Posted

So this is a vm then "vmxnet3"

So I see dhcp is enabled

DHCP Enabled. . . . . . . . . . . : Yes

Is the IP set static that your wanting vs the 169 address? I see you got a lease

Lease Obtained. . . . . . . . . . : 03 July 2013 19:07:54
Lease Expires . . . . . . . . . . : 06 July 2013 21:48:56

from
DHCP Server . . . . . . . . . . . : 192.168.32.239

Also why would you have 2 default gateways setup?? I see you have default gw on both your interfaces - this is RARELY a good idea!!! To be honest multihomed like what you have is odd setup as well generally.

Share this post


Link to post
Share on other sites

Posted

Failover Cluster Node ? This is normal for active/passive clusters.

So this is a vm then "vmxnet3"

So I see dhcp is enabled

DHCP Enabled. . . . . . . . . . . : Yes

Is the IP set static that your wanting vs the 169 address? I see you got a lease

Lease Obtained. . . . . . . . . . : 03 July 2013 19:07:54
Lease Expires . . . . . . . . . . : 06 July 2013 21:48:56

from
DHCP Server . . . . . . . . . . . : 192.168.32.239

I just checked and the clustering components are not installed.

 

Yeah it is a VM. On the VLAN4 NIC, it is set to a static IP and VLAN5 is DHCP. It is the extra 169 address per interface that I want to try and get rid of, or find out why it is there.

Share this post


Link to post
Share on other sites

Posted

Do you have host only network setup or something on these VMs? What mode do you have them in NAT, Bridged, etc. in your VM software? Is this ia esxi box or vmplayer, some other vmware?

Need some details of how you have this vmsetup.. And are you really doing vlan tagging? Or are these different physical networks and your just calling them vlans?

So in your vmware you have tagging turned on in the vswitches? In your physical network your using what for your switch that handles vlans?

And not related to your issue - but how do you think your using default gateways on these interfaces? This is almost always 99.999% a broken config!! Do you really have 2 different paths to the internet? Or lots and lots of other networks?

Share this post


Link to post
Share on other sites

Posted

Do you have host only network setup or something on these VMs? What mode do you have them in NAT, Bridged, etc. in your VM software? Is this ia esxi box or vmplayer, some other vmware?

Need some details of how you have this vmsetup.. And are you really doing vlan tagging? Or are these different physical networks and your just calling them vlans?

So in your vmware you have tagging turned on in the vswitches? In your physical network your using what for your switch that handles vlans?

And not related to your issue - but how do you think your using default gateways on these interfaces? This is almost always 99.999% a broken config!! Do you really have 2 different paths to the internet? Or lots and lots of other networks?

I'll get some screenshots in a minute. Each NIC is linked to a different VLAN in ESXi 5. Tagging is done by ESXi. The physical sewitch has 4 VLANs tagged for that port, and an unused VLAN for the PVID. It is a Netgear GS110TP.

 

For the two gateways configured problem - I have set the VLAN5 interface metric manually to 200 so that it will never be used as the default gateway (unless VLAN4 goes down). It would be OK to use this route if it did failover.

 

I will re-post with screenshots in a few minutes.

Share this post


Link to post
Share on other sites

Posted

[attachment=337432:esxi-network.png]

[attachment=337434:esxi-vm-config.png]

[attachment=337436:vlan4-settings.png]

[attachment=337438:vlan5-config.png]

Share this post


Link to post
Share on other sites

Posted

Dont forget to check your alternative configuration, you can assign multiple ips per nic with that.

Share this post


Link to post
Share on other sites

Posted

Dont forget to check your alternative configuration, you can assign multiple ips per nic with that.

Nothing configured in Alternate Configuration tab for VLAN5. Tab not displayed on VLAN4 as it has static IP.

Share this post


Link to post
Share on other sites

Posted

I would guess your issues is related to this

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2012646

So fix the registry for this nic, or you could prob just delete and reinstall the nic.

Your post got me looking through that part of the registry, and somehow there were two GUIDs referencing the same IP address under tcpip\parameters\interfaces . One GUID has the static IP set, and is correct. The other GUID had DHCPClient set to 1, but the IP address fields were already filled with the same details as the static entry e.g. 192.168.32.239.

 

It appears the one with the DHCPClient set to 1, is infact a ghost entry which has no physical network access, but still binds to the VLAN4 interface. Hence the autoconfiguration IP address 169.x .

 

Very VERY strange - something I have never seen before. I will post screenshots that hopefully clarify what had happened.

 

Thank you all for your help,

 

Tony

 

EDIT: It didn't fix it. Doh!

Share this post


Link to post
Share on other sites

Posted

What didn't fix it - did you delete the entry?

Can you post up the export of your reg entries?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.