Not necessarily which is what I keep trying to say .. server location can cause routing issues so sometime a specific location for a server can cause issues from folders at other locations .. servers have different IP addresses - this can allow firewalls/proxies to have issues - iirc there have even been cases of av interference with comms when something related to wu trips heuristics - other times certain routing delays have caused connections to be dropped .. there are many different ways that a setup that works for most servers can have issues with others - that aren't as such the servers fault, simply more "environmental".Colonel_Klink wrote: ... and would think that I would have trouble with all servers if there was a problem on my end.
The fact that some WUs for that server get through is interesting and having PRCGs for ones that do as well as ones that don't might allow a pattern to be spotted.
That server is assigning some 3300 wus/hr and from reports so far the only person currently having issues appears to be yourself which as a data analyst (not linked in any way to fah other than as a folder) raises flags for me .. I have seen the deluge of "me to" posts when servers are having issues.
There will be something causing this issue - but it appears to be something very specific to the combination of your kit, your routing to that server, and that server ... from some of your logs it feels as if there might be a timeout/upload size pattern - which could be a server side issue - but if it is why aren't other folders reporting this?
I also seem to recall you may have had similar issues with other servers in the past (but I may well be wrong on this and haven't checked) ... again if these problems were many attempted returns to servers that otherwise appeared online and accepting wus (and not reported by other folders) these might have been linked to the current issue (even if different servers).
I honestly don't know for sure where the issue lies - if I did then it could be solved !! ... I am just very wary at saying it is an issue with the server that needs to be solved given the lack of any other reports - especially as if there isn't an issue with the server then it will never get resolved that way
The more data you can collect re WUs (prcg values, upload sizes, number of attempts before uploaded) that do upload and those that don't the more likely the cause can be tracked down and a solution found ... identifying if it is some form of time or size related pattern will also help
If you can manage to monitor the comms connections (I am not a networking specialist but I know some people are good at tracing routes and monitoring comms protocols) and see what is dropping the connection that might help (although that might be easier from server end depending on toolsets available).
I actually want this to be server side issue - and I so want to be wrong - as it will be possibly be easier to track down if it is ... but the silence of the masses makes my gut tell me otherwise
... Hopefully this wont happen again and it will just be one of those "unresolved mysteries" of the past
.