Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sorry for the vague title, I'm finding it hard to describe the problem accurately in a few words (but that's probably because of me, English is not my native language).

I'm trying to send a file from one computer to another via TCP. My server/reciever is directly connected to the internet (at least, that's what I suppose, I'm hiring this room and the internet is included, I have no idea about the set-up, it's really plug-and-play for me), the other one is connected to a WLAN (from the wireless router of one of my housemates, so my housemates also have acces to this network). The first three bytes from the IP-adresses are the same (I checked via whatsmyip.com).

I send and recieve in a blocking way (so non-asynchronous). When I try to send a short message, the sender/client crashes with a timeout error. I then tried to ping the other IP adress, but this one times out too! Even more surprising (to me, at least) was that the ping the other way around works fine (so from the machine that is directly connected to the internet, to the machine that is connected to the WLAN). If anything, I would expect it the other way around (because I understood that it could be a bit of trouble to connect to anything behind a firewall/router).

So: ping from WLAN -> directly connected machine (what is the right term for this?) times out, but directly connected machine -> machine on WLAN works fine.

As you may have understood (by analyzing my usage of terms), I really have no clue about networks. I followed a course (I'm a computer science student) two years ago (half of it was on computer architecture, and half of it on networking). I've always used existing networks (my dad used to handle that when I lived at home, and now the organization where I'm hiring from). Could anyone explain to me what is going on, and possibly help me with it? (I didn't provide my source for the send and recieve programs, because I think that once I understand what is going on I am able to fix it myself).

Greetings and thanks in advance to anyone who takes the time to help me! :)

share|improve this question

migrated from serverfault.com Jan 24 '13 at 0:21

This question came from our site for professional system and network administrators.

1 Answer 1

up vote 0 down vote accepted

I wanted to rewrite this question, and during the rewriting a possible answer occured to me. Some research showed that this is probably the correct answer.

The IP-adress is not of the computer, but that of the router. When I ping from the computer on the WLAN, you ping from the IP adress of the router and the ping back gets send to the router, but isn't transmitted to your computer (because the other computer's response can't reach your computer behind the router).

When you ping from the directly connected computer, the response that you get is actually from the router, not from the other computer. It responds even if the other computer is off.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.