05-31-2009, 08:38 PM
Quote:Did the netstat -n command. Here is what it says:Posting the full details is probably unwise, but you truncated a bit too much. Please try again and do not leave out the parts that you replaced with "blah." You can omit the local address, which is the only sensitive part.
Proto Local Address Foreign Address State
TCP (all columns) Is it safe for me to post this here? 169.229.blah Close Wait
203.73.25 blah Close Wait
63.240.202 blah Established
63.240.202 blah Fin_Wait_1
That's all. So any help would be appreciated.
Guessing based on socket state and the part of the IP address you did post, it looks like you're connecting successfully. That's not good, because it means the most common problems aren't the issue here.
NAT = Network Address Translation, a technique often used by home routers because ISPs don't want to issue enough IP addresses to cover the systems you actually use (or if they do, they charge exorbitant prices for them). You probably are using this, but since you established the TCP connection, NAT is not likely to be the culprit.
P2P = Peer-to-Peer, often used for filesharing. It's only of interest here because badly tuned P2P clients can soak up all your upload bandwidth, causing other outbound traffic to be delayed. If the delayed traffic was important, such as the packets for establishing a new connection, that delay could mean the difference between a prompt success and an eventual failure.