10-23-2016 04:48 AM - edited 03-08-2019 07:53 AM
Hi,
My customer just replace their old L2 switch with Cisco 2960X. The configuration on each switch port is simple:
interface GigabitEthernet1/0/3
description Connection to End Client (Voice and LAN)
switchport access vlan 10
switchport mode access
switchport voice vlan 182
srr-queue bandwidth share 1 30 35 5
priority-queue out
mls qos trust device cisco-phone
mls qos trust cos
auto qos voip cisco-phone
spanning-tree portfast
spanning-tree bpduguard enable
service-policy input AUTOQOS-SRND4-CISCOPHONE-POLICY
This L2 switch is connected to L3 Cisco 3850 directly via trunk mode. The gateway of VLAN 10 is located on L3 switch.
After few days replacement, some random client computer can't ping to the gateway. All of client computer use static IP address. When we checked, there is an autoconfiguration IPv4 on client computer.
This happens when the user restart their PC or turn on their PC.
Does anybody ever experience this problem?
Thank you.
Regards,
Arie
Solved! Go to Solution.
10-23-2016 05:35 AM
The problem could be caused by the IP address already being in use. Make sure there aren't any duplicate addresses in your network.
Otherwise, you can turn off Autoconfiguration on your Windows client by accessing the registry on those clients. Check the link below for the procedure:
https://social.technet.microsoft.com/Forums/office/en-US/3e26affd-bb91-460a-b5fa-c7c0496c927c/how-to-disable-autoconfiguration-ipv4-?forum=winserverNIS
10-23-2016 05:35 AM
The problem could be caused by the IP address already being in use. Make sure there aren't any duplicate addresses in your network.
Otherwise, you can turn off Autoconfiguration on your Windows client by accessing the registry on those clients. Check the link below for the procedure:
https://social.technet.microsoft.com/Forums/office/en-US/3e26affd-bb91-460a-b5fa-c7c0496c927c/how-to-disable-autoconfiguration-ipv4-?forum=winserverNIS
10-23-2016 04:39 PM
Hi,
Thank you for the sharing.
Is there any other possibility which cause that?
Thank you
Arie
10-23-2016 11:29 PM
Arie,
I have been looking around and found the topic below. Although this seemingly applies to Windows 2008 server, try the procedure on your clients (make sure you run the command prompt as administrator)...
http://lyngtinh.blogspot.nl/2011/12/how-to-disable-autoconfiguration-ipv4.html
10-24-2016 12:03 AM
Hi,
Thank you for the link :)
Btw, is there any effect if the autoconfiguration IPv4 is disabled on Windows client?
Thank you
Arie
10-24-2016 12:20 AM
Not really, the 169.154.0.0/16 address space has been allocated to Microsoft and is not really useful for outside communication anyway. It is sort of a gateway of last resort for clients that cannot obtain an IP address, and to allow local communication. This here is a pretty good explanation:
http://packetlife.net/blog/2008/sep/24/169-254-0-0-addresses-explained/
10-24-2016 10:37 PM
Hi,
Thank you for the explanation. Very helpful. :)
Regards,
Arie
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide