Windows 10 is not picking up a new IP address.

I'm not sure where to begin with this one. Problem is I can't get Bridged Network to get an IP address anymore. Shared Network gives me 10.211.55.x and does get me network access but I have software for work that scans the network and this requires I'm on the same VLAN. There were some changes to the network yesterday and this just started happening in the middle of the changes.

The last step I did was connect to my iPhone's Hotspot and confirmed Windows can acquire an IP address and access the internet. When I switch back to the home network, Windows is unable to get a new IP address.

The one commonality I see between the two working configs (Shared Network and iPhone) is that I'm getting a nice IPv6 address. My Link-Local iPv6 is the same in all three configs. IPv6 Default Gateway is blank and IPv6 DNS Server has three entries like fec0:0:0:0:ffff::1:2%1 which I presume are null. There are no entries for IPv6 Address or Temporary IPv6 Address.

Edit: I just realized the above statement about the IPv6 was pointless.

 

Hello Anthony Sbarro,
In order to investigate the issue further we need you to submit a Problem Report and provide us with its ID number. Please follow this KB article to submit Problem Report:http://kb.parallels.com/9058
NOTE: Please submit a report while reproducing the issue and provide us with generated ID number

 

Hi Antony,
What exact network changes had place? Looks like your WiFi access point indirectly forbids situation when more then one IP address is used per 1 physical MAC address. WiFi due to its nature requires that all outgoing network frames have authenticated MAC-address. So, Parallels have to use the MAC-address of the Host Mac OS. Here is instruction how to configure Cisco router:
> http://kb.parallels.com/en/117191
Also, switching to cheap router which doesn't support dhcp client identifier checking can result in this behavior.

 

Sorry, I guess I lost track of this. I continue to have this issue on random LANs. I'm working from home today so no problems now. When I get back to my office tomorrow, I know that my virtual machine needs to have it's ip address set static. We typically deploy cisco RV320 routers. Sometimes they work and occasionally they don't, in regards to acquiring a dynamic address. The router I was on when I originally posted this was something other than an RV series and I haven't been back there since. I haven't revisited this post because I had found a few instances online that suggest this is a cisco bug that has existed for over 5 years. Would love to know if anyone else is having this problem and if they'v found a work around.