You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

StigBull Author

Level 1

20 points

My network connection completely died - "failed: 49 - Can't assign requested address"

The entire networking stack on my 2012 Retina MBP died just a few minutes ago, and I was only able to get it up and running by rebooting.

First no sites in Safari worked and then I noticed when using telnet that:

[stig@Hyperion:~]$ telnet www.allthingsd.com 80

Trying 192.0.65.213...

telnet: connect to address 192.0.65.213: Can't assign requested address

Trying 192.0.65.216...

telnet: connect to address 192.0.65.216: Can't assign requested address

telnet: Unable to connect to remote host

Strangely enough traceroute and ping worked.

In the system log there is no warning untill the network is down:

Nov 12 10:28:31 Hyperion.local mDNSResponder[62]: AppendDNSNameString: Illegal empty label in name ".weblamb.com"

Nov 12 10:28:31 Hyperion com.apple.launchd.peruser.501[164] (com.onible.iTunificationStartup[65065]): Exited with code: 1

Nov 12 10:28:31 Hyperion com.apple.launchd.peruser.501[164] (com.onible.iTunificationStartup): Throttling respawn: Will start in 10 seconds

Nov 12 10:28:33 Hyperion.local PluginProcess[65047]: CoreText performance note: Client called CTFontCreateWithName() using name "Arial" and got font with PostScript name "ArialMT". For best performance, only use PostScript names when calling this API.

Nov 12 10:28:33 Hyperion.local PluginProcess[65047]: CoreText performance note: Set a breakpoint on CTFontLogSuboptimalRequest to debug.

Nov 12 10:28:33 Hyperion.local PluginProcess[65047]: CoreText performance note: Client called CTFontCreateWithName() using name "Times Roman" and got font with PostScript name "Times-Roman". For best performance, only use PostScript names when calling this API.

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111635 connectx to 88.221.96.163#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111635 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111634 connectx to 88.221.96.163#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111634 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111637 connectx to 88.221.96.163#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111637 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111636 connectx to 88.221.96.163#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111636 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111639 connectx to 173.194.32.62#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111639 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111638 connectx to 173.194.32.62#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111638 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111642 connectx to 173.194.32.62#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111642 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111640 connectx to 23.23.14.248#80 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111644 connectx to 192.237.224.183#80 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111644 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111646 connectx to 173.194.32.62#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111646 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111645 connectx to 173.194.32.62#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111645 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111647 connectx to 173.194.32.62#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111647 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111648 connectx to 173.194.32.62#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111648 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111640 connectx to 107.22.72.129#80 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111649 connectx to 173.194.32.62#443 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111649 failed to connect

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_destination_prepare_complete 111650 connectx to 184.86.224.214#80 failed: 49 - Can't assign requested address

Nov 12 10:28:34 Hyperion.local com.apple.WebKit.Networking[2157]: tcp_connection_handle_destination_prepare_complete 111650 failed to connect

I tried flushing the routes and using ifconfig to down/up the interfaces but nothing worked.

Has anybody seen anything like this?

MacBook Pro with Retina display, OS X Mavericks (10.9)

Posted on Nov 12, 2013 2:15 AM

158 replies

hvdm

Level 1

0 points

Jan 22, 2014 8:39 AM in response to parsifal_

No, I did not check the console. I gave up and did a reboot, I wanted to get some work done :-)

Nate12

Level 1

0 points

Jan 25, 2014 7:40 PM in response to StigBull

Ok. It finally happened again. Uptime was 23 days. Was running dropbox, uTorrent, and World of Warcraft.

Flushing the routes with the network down did not have any effect. netstat showed the typical behavior with lots of connections in LAST_ACK or FIN_WAIT_1.

Nate12

Level 1

0 points

Jan 25, 2014 8:07 PM in response to StigBull

Submitted another bug on this (15910265). Hoping Apple is taking notice.

Jan 31, 2014 12:42 AM in response to StigBull

I filed rdar://problem/15611799 for this, as well. It's killing my co-located server. I've also pointed to this forum in my bug report, so Apple's engineers can see everyone else who's having this issue.

ooglek2

Level 1

4 points

Feb 5, 2014 9:05 PM in response to Wil Shipley

I started having problems with this today as well. Early 2008 Mac Pro, Mavericks 10.9.1

Uptime 22 days, 5:25

621 tcp4 connections (from netstat)

339 LAST_ACK
164 FIN_WAIT_1
55 FIN_WAIT_2
43 SYN_RECD
18 ESTABLISHED
1 CLOSING
1 CLOSE_WAIT

Looking at state vs port, top 6 results:

164 LAST_ACK Port 80
124 LAST_ACK Port 443
26 FIN_WAIT_1 Port 443
25 FIN_WAIT_2 Port 80
11 FIN_WAIT_1 Port 80
6 FIN_WAIT_2 Port 443

The IP addresses span Twitter (Tweetbot), AOL (AIM), Microsoft (Skype), Dropbox, AWS, Evernote, nothing surprising. Quitting Dropbox did not release the LAST_ACK slots from netstat.

So I shut down, left it off for 30 seconds, then turned it on again. All was well with my netstat output again. I had thought it was Chrome at first, because I use Google Chrome on my Mac Pro but not my Macbook Pro. But the evidence seems to point at something broken in Mavericks. I'm guessing the port 80/443 thing is a red herring; I just visit more servers on those ports than other servers on other ports.

tixetsal

Level 1

9 points

Feb 5, 2014 9:12 PM in response to ooglek2

Someone should sniff (tcpdump) this and file it with Apple.

Nate12

Level 1

0 points

Feb 5, 2014 9:31 PM in response to StigBull

I talked with an Apple rep today. This may already be fixed in 10.9.2 beta. I don't know when the final release will be out but I will install the latest beta and see if that resolves the issue.

Feb 7, 2014 3:40 AM in response to StigBull

And again "Can't assign requested address" (uptime 22 days)

tcpdump shows no traffic is going over the wire when this situation occurs, which says (to me) there is a failure to allocate an ephemeral port for some reason or other.

uptime >= 21 days seems to be common accross these messages.

tixetsal

Level 1

9 points

Feb 7, 2014 6:48 AM in response to gary.liddle

Interesting.

trisweb

Level 1

0 points

Feb 8, 2014 7:59 PM in response to gary.liddle

Happened to me today for the 3rd or 4th time since upgrading, uptime only 16 days. But it does appear it has to be on and active for at least a week. Perhaps it makes a difference that this is a home server that doesn't sleep and has many network services running all the time...

justinwr

Level 1

0 points

Feb 8, 2014 8:48 PM in response to StigBull

I was hit by this issue for the first time today and will go file a bug report.

Like everyone else, my mid-2010 iMac is running Mavericks 10.9.1 and received all the errors and logs as mentioned previously by everyone in this thread, with a reboot solving the issue.

My iMac mainly stays awake or asleep for most of the day on an ethernet connection and isn't doing anything suspicious. All processes and logs point straight to the Ethernet driver and Kernel.

An uncommon theme however is that my iMac was running twice as long as everyone else...

Local system status:

20:01 up 48 days, 6:37, 1 user, load averages: 0.79 0.78 0.80

Hopefully this gets fixed because its a pretty serious issue. I can't have this machine die on me when I'm mobile and away from home.

justinwr

Level 1

0 points

Feb 8, 2014 9:20 PM in response to justinwr

Opened bug report #16020891

I'm sure it'll be closed as a duplicate but I'll keep harassing until it's fixed or there's better information about the problem.

ksn135

Level 1

0 points

Feb 10, 2014 3:50 AM in response to StigBull

Same issue happend to me today. Waiting for 10.9.2 ?

Feb 10, 2014 6:13 AM in response to ksn135

For the possibly-new people having this problem, I'd like to reiterate a technique I've been using that seems to work:

sudo ifconfig en0 down && sudo route flush && sudo ifconfig en0 up

Replace "en0" with your main network interface.

justinwr

Level 1

0 points

Feb 10, 2014 11:13 AM in response to parsifal_

The first time this bug happened I performed a lot of diagnostics even though I knew a reboot would solve the issue.

Bringing down my network interfaces, flushing my routing tables and bringing my network interfaces back up did not change what IPs I was receiving from DNS resolution. However, now thinking back, I did not monitor my routing table for changes or lookup misses, something I should have thought of at the time.

Reboot was my only solution... which really *****.

My network connection completely died - "failed: 49 - Can't assign requested address"