2
I tried using ncat (a “much-improved reimplementation of netcat”) to chat with a friend (and ultimately want to send a large file, but I know I can get that working once I get chat to work).
We both have Windows.
On my end I typed:
ncat -l 3333
On his end I had him type:
ncat [my public IP] 3333
Nothing happened on my end, while his completed with "Ncat: ." and returned to the prompt.
I couldn't figure out what to do to fix this, so I decided, while he's busy, I'll test this out on two of my own laptops (one with Windows, the other with Linux, not sure if it should matter).
I found the same results ("Ncat: ." then back to prompt) only when I issued
ncat -l 3333
from Linux and
ncat [my public IP] 3333
from Windows.
The only scenario in which the chat/file-transfer did work was when I listened from Windows and did ncat [my public IP] 3333
from Linux.
Any ideas why this is happening, and what I can do to fix it?
You did not tell wether it's working or not. At the moment, you don't like the blinking cursor. That's all you've told. Please give us more information of what works and what doesn't. And I suggest you portforwarding, if the connection could not be established. – Peter – 2013-03-05T07:50:34.477
@Peter: Read it again. He’s saying that the client process exits immediately upon being started. – Scott – 2013-03-05T20:53:17.037
Emil: Have you tried
-v
(and-vv
and-vvv
)? Do you have a sniffer (e.g., ethereal, Wireshark, tcpdump, …)? Can you see what is happening on the wire? – Scott – 2013-03-05T20:54:08.363yes, I have Wireshark. I can try taking a look, but it is a little overwhelming, and I'm not sure what to look for. I took my first Routing/networking class last semester, so I'm new to this.
I'll check though and see if anything looks...::ahem:: familiar – Emil – 2013-03-06T03:18:05.930