1

I am running into a unique issue. I have a 2003 Server handling DHCP and DNS. Windows 7 computers are not getting IP addresses. The DHCP leases show the computer has an IP, but the computer is getting private 169.x.x.x addresses.

Any idea? This began happening recently.

@Cisco

7 Spice ups
2

Do you have a firewall in the mix somewhere? I’ve heard of this issues happening with a Sonicwall in the middle.

Other than that you can cycle through the basics. Run the following commands:

ipconfig /release

ipconfig /flushdns

ipconfig /renew

Also check all switches/routers in between the client and the DHCP server for connectivity lights/error logs to make sure that those devices are not causing the issue.

Windows computers automatically receive an IP of 169.254.x.x When they cannot obtain an IP from any DHCP server (or no DHCP server responds to the request) This is known as the Networking Out-of-the-Box IP. If you have just a hub/switch with no DHCP server and you wanted to network multiple computers they could talk to each other with this IP.

1 Spice up
3

Are the leases current, or are you looking at old data?

If you delete the leases from the scope and renew from the client, does the lease repopulate in the scope?

Have you looked at both ends with Wireshark?

1 Spice up
4

I have seen this where the network card drivers have not updated correctly. When the workstation turns on the driver takes longer than normal to initialize and times out when receiving the DHCP assignment.

Try updating the network drivers on one workstation.

5

Have you checked all the physical connections?

  • Network cable is plugged into the computer and wall?
  • Switch port is active
  • Patch panel port is still going to the switch (i.e. the patch lead hasn’t been “Borrowed”)

Have you run an ipconfig?

  • What are the results?

If you delete the DHCP entry, does the PC obtain another lease?

3 Spice ups
6

169 is apipa which is just a number windows gives the pc when it fails to get one from anywhere else. Make sure your 2003 server and your win7 are both on the same subnet. Also check the gateway and make sure the DNS and ip addresses are intact. Something was most likely entered incorrectly, or the server is simply not dishing anything out.

3 Spice ups
7

I have done the flush/release/renew. Does not help. This only occurs with 7 computers. XP computers work fine. I’ve cleared out all of the leases and had them rejoin. The Win7 computers show up in the scope with a valid address, but the computer doesn’t get an address. I don’t get why XP works.

8

How long are the leases? Is the date and time correct on the Win7 computers? Is there a firewall setting via GPO for “Prohibit unicast response to multicast or broadcast requests” Enabled if so disable it.

9

7 days. I’ll check those settings.

10

The GPO Setting was not configured.

11

APIPA—

Is it only Win7 computers? Other devices obtain IPs without an issue? Can the Win7 boxes ping the DHCP server? For devices getting IPs, verify the IP of the DHCP server they got them.

1 Spice up
12

XP computers, phone, tablets all get IPs fine. My Win8 computer gets a good IP and works fine.

Once I give the Win7 computers statics, I can ping and even access the file server, which is also my DNS/DHCP server.

13

There is a setting that is causing a NACK and throwing the server, I assume, isn’t throwing the IP to the computer.

14

Did you try the driver update that David suggested?

http://community.spiceworks.com/topic/post/2001596

15

I have updated the drivers. No go :-\

16

What does an ipconfig /all produce?

Is there a conflicting IP?

What changes have happened recently?

17

Client firewall off?

18

Try and set it to disabled even though it’s not configured.

19

I’ll check on the firewalls in the AM

Thanks

20

Do you have a cisco switch ?