Problem Downloading

i don't think WBS is blocking file types or you wouldn't be able to start the download in the first place, you'd just send the request and no data would return. I'm trying to think where a problem could lie... and I think it must be the caching servers. I am downloading SuSe 9.3 eval DVD ISO righ tnow as it happens, I am 1.4GB through and haven't had a problem yet.. but then again I did chuck about 8 mirrors into my download manager
 
slimothy, I think the problem is in their useless packet management system. I had the same problem, and my conclusion is that the problem is caused by some data sequence in the data transmitted. It seems that their crap system is misinterpreting the data or something so it drops that packet, so it never continues. As you can see it depends on the file downloaded, no matter where the file is coming from or what type it is.

It is one of those things that WBS did not do intentionally, it just happened due to their incompetence.
 
what packet management? if you are refering to the packet shaping, there are absolutley no rules for http, also if it was a dropped packet you request it again but I notice that the request stop and the thing just dies, I think we need to look for evidence before we can categorically state what the problem is... could be anything, for all we know its a problem with WBS' provider and not WBS.

Here's what we know for certain, its not a problem with the server so the problem lies somewhere between the server and us, could be WBS, probably is WBS but we can't be certain yet.
 
can we get one of those problematic files and wipe out (fill with zeroes) the part that causes the connection to hang, then put it on some external server and see if it works. So this way we can figure out if the problem is triggered by a data sequence in the file, which is my theory.

Actually I can do that test ... just will take me a while
 
overwriting data with nullbytes won't work either. If you did it and downloaded the file fine any reasonable person would just say, but you didn't download it fromt he same server. I see where you're going with this, you think that at that portion (actually for me the place it stalls changed) there is some data that when sent in the packet gets caught by the packet manager and causes it to stall, that idea isn't out there, and sounds sorta feasable, but if you know packet shaping software (intelligent firewalls) you will know that rather than creating 256K or more memory space checkign each and every packet sent, which is dumb because the packet manager will end up wasting resources on junk packets that don't help ot do its job, they rather grab and check the packets that are responsible for creatign and maintaining the connection, they look at packet structure as well as type of data sent and of course source port, destination port etc etc. That way they only read packets that help it do its job. So if the stall was due to the packet shaping then it would not create the connection or throttle it all the way through, not stall.

But, we all know WBS isn't above making a hiccup or two, so maybe there is something in that specific packet that gets dropped because of thier shaping rules (but again, why would they drop it and not throttle it, as far as I know WBS don't have policies to BLOCK traffic, just shape it)... but I'm sticking with the cache server thing for now.

Can someone run a packet sniffer when downloading that area of the file and paste the packets for us to see?
 
I have a different opinion - I still have ~350MB left so I am not yet capped, and my multi-threaded & multi-mirror downloads seem to stall every 15..20 minutes, the only way around it is to pause the download (only running 1 at a time now) then drop the iBurst connection in SWE2, reconnect and then resume as soon as SWE2 beeps to say the connection is re-established...:(
 
My theory proven!

I just replaced 10 KB of data with zeroes in one of the problematic files without changing the files size, name etc at all, and the file now can be downloaded just fine.

Note as well that the problem does not occur on upload! So you can upload problematic file just fine.
 
what do you mean zero's? null bytes or ascii zero's (as in the letter 0), also how did you download the file, and where did you place the zeros, what addresses? also can you paste a link so we can try download it too.
 
yeah so where did you place them, where did you upload the file, and how did you download it
 
I uploaded and downloaded via FTP

1. I have a copy of the file on my local machine downloaded via modem some time ago
2. I uploaded that exact copy to a web site to which I have FTP access
3. I attempted to download the file via FTP just after the upload finished, and it stuck at the exact same place where it did originally.
4. I modified my local file (copy of it of course), replacing couple of KB around the problematic spot with 0x00 bytes
5. I upload the new file to the same web site (renamed the previously uploaded file, so the modified one remain with its original name)
6. I downloaded the file via FTP and it got through just fine.

So you have 2 files on the same server, with only difference being couple of KB wiped out with 0x00 in the one of them, and the one works, the other doesn't ...
 
ic, so you saying that reconnecting the modem and resuming the download works fine for you? That is new. I have not tried that.
 
I see there are some Linux people here, so I am going to post a new thread with some questions I have about the UTD on linux ... please have a look in 5 minutes and any help will be appreciated
 
dude this is starting to sound like bullsh*t, ok clear this up for me real quick, WHERE did you overwrite the data, where is this "problematic spot" because I want to try, or did you just pick random places, because that wouldn't make sense, WHERE is the link to the copy you uploaded, or are we just supposed to take your word for it.
 
unfortunatelly if I post the link to the file this will reveal my real identity :-) hence the reason for not posting the link on the forum ...
 
yeah, sure, whatever, so how about answering the other questions, because this sounds like a story, where in the file did you overwrite data, and what did you use to overwrite it
 
slimothy, I can upload the files to place of your choice ... just tell me where

the problematic spot for that particular file is about 807-808 KB (the file size is 1 MB). I overwrote the data on my local pc and I uplaoded the modified version to the external server.

this is the original link to the problematic file
http://www.fxcorporate.com/FXCM/tsmulti/FXTSInstall.W03
 
I overwrote the file between 800 and 812 KB approximatelly, and used UltraEdit in hex mode for that and my finger on the 0 key for few minutes, please save your comments how dumb I am doing it in such a manual way ... I am sure there is a nice cryptic command line on linux that will do it for a blink of an eye, but I don't know it.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X