Secondary 169.254.x.x IPV4 address and routes are added after every reboot.

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= 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?
Who is Participating?
maserviceConnect With a Mentor Author Commented:
I got it working, finally! Problem? As I said, smtp port 25 wasn't responding to outside of server. I kept digging and after running netstat -a I noticed it was listening for port 25 but not on the local ip, only and the ipv6 address. So I checked the Receive Connector in Exchange 2010 and it was fine, it was set to listen to "All available ipv4" addresses on port 25. But I decided to edit it and change it to listen to only to the specific local ip of the exchange server and when I did a telnet test from another pc to port 25 on the exchange server this time it responded. After this I just sent myself an email from hotmail and bingo.

I then changed it back to All available ipv4 addresses on port 25 and SMTP still responded. Talk about a glitch!

Thanks for trying to help mate. I'm glad I have this over and done with after many frustrating and relentless hours of persistence into this issue.

This can be closed.
Sounds like you have a second NIC.  This is an APIPA address that is used when a NIC is not configured for an IP or able to contact a DHCP server.

Look to see if you have one and disable it.
--- Sorry should have read your entire message --- Disregard.  

When you do an ipconfig /all what is showing.  Can you post?
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

maserviceAuthor Commented:
This is how it should look (and after I remove the 2nd ipvr address using netsh):

 Connection-specific DNS Suffix  . : ourdomain..local
 Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
 Physical Address. . . . . . . . . : 00-0C-29-60-67-0B
 DHCP Enabled. . . . . . . . . . . : No
 Autoconfiguration Enabled . . . . : Yes
 Link-local IPv6 Address . . . . . : fe80::3d58:c07e:cc93:64b9%15(Preferred)
 IPv4 Address. . . . . . . . . . . :
 Subnet Mask . . . . . . . . . . . :
 Default Gateway . . . . . . . . . :
 DHCPv6 IAID . . . . . . . . . . . : 268438569
 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-18-42-99-00-0C-29-80-67-

 DNS Servers . . . . . . . . . . . :
 NetBIOS over Tcpip. . . . . . . . : Enabled

This is how it looks after I reboot (and waiting about 4 minutes before the above changes. The network adapter icon has the circle over it for about 4 minutes before it's finally active, but then I get two ipv4 address):

Hmm, never mind. This time it wouldn't show the 2nd ipv4 but I'm still unable to receive/send external emails.

What's interesting is that in the GFI Mailessentials dashboard which shows all the incoming emails live, and when I send myself a test msg from hotmail I can see it (via the dashboard) coming in as:


then 1 second later I see:

sender:     postmaster@server03.ourdomain.local

But I don't see the bounce in my hotmail account so it's unable to send external emails.

Something appears to block it from letting exchange push it to my mailbox. Spam filtering? GFI essentials always sent me bounces before and I'd see them in my Outlook but not now so I don't know if it's now blocking it or if the Microsoft antispam is joining the act. I doubt it's gfi because even if I uninstall it the same thing happens. Antispam in EMC I disabled temporarily and still no difference.  Nothing in the queue so I don't know where these emails are ending up since I can't see them anywhere.

I tried checking the logs at: C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpReceive but it's blank. Same for \SmtpSend. Maybe that's not the right path to check? Never checked on 2008 yet, only 2003. I did find many Transport Logs however and this could be the issue too. A couple of months ago I migrated from exchange 2003 to exchange 2010 and for the two months or so it's been running fine. Now I see in the transport logs many references to my old server (which is history now). Public folder store refers to my old server. Public folder database refers to my new server.Mailbox store refers to my old server. Still, I didn't have and I don't have issues accessing my mailbox via OWA or Outlook 2007. I am connected to my exchange server (no cache mode) and I can access all emails including the public folder. I just can't send or receive external emails anymore. Internal is fine although I see the on the gfi dashboard that the sender is postmaster@ourdomain.local instead of myexchangeemail@ourdomain.local. Seems like some routing issue now but I don't know what to do from here. I already went through everything in the EMC for Exchange 2010 and I see no references to my old server anywhere and everything appears to be the same as it was when things were working. I also checked my mx records.
maserviceAuthor Commented:
Strangely, outgoing external mail works now so when I sent a test msg from an external account to my domain email I got a bounceback:

Delivery has failed to these recipients or groups:

The recipient e-mail system can't process this message now. Please try resending the message later.

Diagnostic information for administrators:

Generating server: server03.ourdomain.local
#< #5.3.5> #SMTP#

Google isn't helping much with this error.
maserviceAuthor Commented:
I've narrowed it down now to the SMTP service on port 25. It's not accessible via telnet from the outside, not even my lan. It only responds from the server itself. But even with the MS Firewall disabled I can't access it remotely. I tried an older snapshot and SMTP from outside works fine. Unfortunately I can't use that snapshot as it would take me back too far and lose some emails.

Why else would port 25 not work from another pc on the same lan with this snapshot?

Btw, the older snapshot also had the 2nd ipv4 169.x.x.x ip but after removing it with netsh and rebooting inbound and outbound emails were working fine. That snapshot is only 2-3 days old so I wonder what would've changed in such a short time that would block port 25 on its own.
Cool.  Sounds like you got it.
Have a good one.
maserviceAuthor Commented:
Found solution on my own.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.