Geek Help
Help! I’m having an issue that I just can’t seem to figure out… Hopefully someone here will be able to point me in the right direction. I *think* the problem is with pipes in Windows (XP SP2 specifically) but I’m not completely sure.
Basically, I’m doing this: nc 192.168.0.1 10567 < hugefile.gz on the Windows box, and the destination has been Linux, Windows XP, and OS X, all with the same result.
Hugefile is somewhere around 22GB… What happens is that seemingly no matter where the destination is, it just stops sending after a while, usually with the output file on the target machine being 23MB-24MB. This size is not consistant. I’ve also gotten these results across a pocket-sized 100MB switch, the company’s switch to which I’m connected, etc.
I really don’t know what’s up… I think it’s Windows pipes, or some sort of buffer somewhere?
Sending from Linux to Windows works just fine, as this was how I created the image. (dd if=/dev/hda | gzip -c | nc -w 15 192.168.0.2)
Does anyone have any ideas? I’m really lost…
UPDATE: A bit more info… This is what I see on the sending side:
nc -v -v -v -w 30 130.175.142.190 10567 < createdimage.gz p-p-p-powerbook.XXXXX.XX.XXX.XXX [XXX.XXX.XXX.XXX] 10567 (?) open net timeout sent 24887296, rcvd 0: NOTSOCK
And on the target side:
nc -l -v -v -v -p 10567 > createdimage.gz
listening on [any] 10567 …
connect to [130.175.142.190] from XXXXXX-notebook.XXXXX.XX.XXX.XXX [XXX.XXX.XXX.XXX] 4244
sent 0, rcvd 24215552
So, yeah. I’m running out of ideas…
You said you tried sending Windows -> * with 100% failure rate.
Linux -> Windows with 0% failure rate
I have an idea but I need to see what your results are going from * -> Windows.
ps
What version are you running?
Re: ps
What version of what?
Re: ps
What version of netcat.
Re: ps
v1.11 for NT on the Windows side… v1.11 on the Linux side, too.
Works just fine. And I got it solved… Removing the -w 30 on the Windows side has stopped it. I’m not sure why, but I’m thinking that netcat was taking more than 30 seconds to dump it’s buffer to the network, and since it had stopped taking any input, the 30 second counter tripped, closing the app. Hence the lack of error messages.
The test is imaging right now… We’ll see how it goes.