Secondary 169.254.x.x IPV4 address and routes are added after every reboot.
Posted on 2013-06-11
How can I stop this? It's causing my server to receive emails but not forwarding them to the client's mailbox. I don't know where it goes but I have GFI Mail Essentials installed and in its dashboard I could see the emails are accepted, but they don't show when I open Outlook 2007 or even login via OWA. I've even uninstalled GFI and reboot but the ipv4 & routes keep coming up after a reboot.
The same server is a DC and runs Exchange 2010 (yes I know it's not best practice but it's only my home mail server). This always worked until the last couple of days with nothing being done to the server.
I can get rid of the routes using route -delete and I can remove the ipv4 address with 'netsh interface ip delete address name="WAN" addr=169.254.101.106 but this doesn't resolve the email issue because I need to reboot and when I do that the 169.254.* addresses are back. I even tried adding the registry DWORD IPAutoConfigurationEnabled 0x00 and still it comes back. I noticed it takes a few seconds for the 2nd ipv4 to show up with ipconfig /all because if I do it right after the reboot it's not there.
Oh, and no, there is no 2nd ipv4 ip if I check the ethernet adapter. All settings are static.
I've also done several anti-virus scans using different products but they never find anything. This is running on a VM using Workstation 9.
Two nics are installed which allows me to vpn into the server (the 2nd nic is disabled in the OS).
Any ideas on what's causing it and more importantly how to fix it?