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

NAT error: UDP OK but TCP = no route to host

I recently did a firmware update on my Airport Express and I think something has changed which is affecting file transfer speed. A NAT test shows UDP listen port 6881 is OK but when testing TCP listen port 6881 I get the following message:

NAT error: No route to host (173.19.148.196:6881)

I have Mediacom Cable and their provided modem is Touchstone Telephony Modem and my Airport Express is plugged into it to provide me a wireless connection (it has an IP address of 10.0.1.1).
I have a MacBook 4,1 Intel Core 2 Duo and run OS X v. 10.5.6. In Security settings my Firewall is OFF.

Can someone explain to me what I need to do to open the TCP port? Also, what is a UDP connection?
Thank you

macbook, Mac OS X (10.5.6)

Posted on Jan 28, 2011 11:24 AM

Reply
1 reply

Jan 13, 2014 1:59 PM in response to George McLean

i had the same problem.

and i did the following steps

on vuze program

1) vuze -> preferences -> incoming tcp listen port (example 50123)

2) set the same port on UDP



after that you have to open tcp protocol (NAT -> virtual server) ... on your router and set start port as the same port as you already set in vuze (ex. 50123)... and an end port (ex. 50124)



be careful as local ip address, you have to set the same ip in the tcp protocol settings with the ip that your macbook uses to connect to the internet. you can find the ip on system preferences --> web--> and get the information.

I hope to help you and others with the same problem!

NAT error: UDP OK but TCP = no route to host

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.