I have a Windows Server 2012 r2 with 2 NICs. 1 local(169.254.1.1/24) and 1 "public"(conected to another local network, 10.0.10.47) interfaces. I have configured DNS, DHCP ONLY on the local interface, and NAT in the public. I have a pc connected to the local network and it gets a correct ip(169.254.1.20) and can make ping to the server local interface, but I cannot reach the 10.0.10.47 interface from my pc. I know there are several variables but Ive searched so much sites and didn't found any solution.
Both firewalls are disabled(just to remove some variables)
I can reach internet from my 10.0.10.47 interface, but It doesn't mather because I cannot even reach the 10.0.10.47 ip from my pc.
Just 1 default gateway configured in each host(that's not the problem), client default gateway: 169.254.1.1, server default gateway: 10.0.10.2.
All the scenary is running on Hyper-V.
The pc is running a windows 8 enterprise.
- My DNS service resolves internet names to the client, so it is working.
Also Ive followed that guides:
I have more links but cannot post it because of my low rep on this site.
(now I have some rep points, thanks) http://blog.mikejmcguire.com/2013/10/18/controlling-multi-homed-microsoft-dns-server-registration-your-eyes-can-deceive-you-dont-trust-them/
Keep in mind this laboratory is just for testing. I'll be adding more info by demand, I don't know what else data to add. Thanks in advance.
SOLVED(thanks to @joeqwerty)
I was using an invalid local ip range(169.254.1.1/24). That range is included in the range used by the APIPA protocol(169.254.0.1 through 169.254.255.254) as described here: http://www.webopedia.com/TERM/A/APIPA.html. So it means that my 10.0.10.47 was recieving the pings from the client(169.254.1.20) , but not replying because of that issue.
Here is the rfc that says that 169.254/16 range is not routable: https://tools.ietf.org/html/rfc3927#section-1.6
Just changed my local range to 192.168.1.1/24 and everything is working ok.