• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4043
  • Last Modified:

WinServ2k8r nic getting APIPA when changing it to static

I have a Windows 2008r2 virtual server within a VMWare environment that is having a weird networking issue. When you set the NIC to a static address and put in all of the appropriate addresses, it cannot get out to the network. When you run ipconfig, it returns 169.x.x.x.

If you change the nic back to dhcp, it gets an address and can get out to the network. If you change it back to static, you get the apipa address again.

I tried adding another Vmware nic to the vm and the second vnic had the exact same behavior.

Thoughts?

I know I could probably setup a DHCP reservation for the IP address I want for the server but I would rather have a fix than a workaround.

Thanks!
0
Schuyler Dorsey
Asked:
Schuyler Dorsey
  • 3
  • 2
1 Solution
 
Darius GhassemCommented:
What type of virtual network are you running?
0
 
Schuyler DorseyAuthor Commented:
It may or may not be an IP address conflict. After changing the nic to x.21, I can still ping the old IP address of x.12. The strange part is that i can run a ping -a and it returns the host name of this virtual server. I checked DNS and it had x.21 listed and not x.12. I also ran a ipconfig /flushdns on the machine I am pinging from.

I ran an arp -a and for .12 ip, I get a mac address that is NOT a vmware mac address. it appears to be a Netgear mac address. But it does not respond on port 80 or 443. There are no DHCP leases for that address so it would have to be hard coded.

But like I said, running the ping -a returns the host name of this virtual server.
0
 
Darius GhassemCommented:
See if you can find the address .12 in DNS.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
Nagendra Pratap SinghCommented:
Possible to post IPCONFIG /ALL here?
0
 
Schuyler DorseyAuthor Commented:
It ended up being a switch. There was a NetGear GS108e switch on the network. When these switches power on, they pull an address from DHCP. The NetGear was assigned the .12 address (same as sql box) because whomever setup the dhcp server did not set an exclusion range for the servers.

After the DHCP lease expires, the Netgear switch does NOT attempt to renew the lease, it basically takes the DHCP assigned address and sets it as the static address on itself. I downloaded the Netgear utility to manage the switch, changed the address and all is well.
0
 
Schuyler DorseyAuthor Commented:
It was the answer.
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now