The former machine behind the "ESTEC's bottleneck", "grid-medialab1.estec.esa.int" (195.169.140.50), is not accessible at the moment (this is not the first case). The second one, "grid-medialab4.estec.esa.int" (195.169.140.53) is unreachable as well. I havent noticed whether someone acquired accesses to other hosts (showing the same limitations), or not, but some generally reachable "reference point" could be necessary here. If you have some info about the accesibility to mentioned machines or why/when are they down/inaccessible, please let us know or complete the info here.

There were shown some traceroute/lft outputs, but was not stated yet which part of the path appears to be the the culprit (i suspect the part between hops 8-9 because i consider the estec-esrin limitation to be global (?) for the whole ESTEC site). Anyway, additional info about ESTEC's internal network and their connectivity is still necessary (ChrisWelti asked Mr. Monleon already, if there's still no reply we will ask him again).

 6   surfnet-gw.nl1.nl.geant.net (62.40.103.98) 23.4ms
 7   PO11-0.CR1.Amsterdam1.surf.net (145.145.166.33) 26.8ms
 8   PO0-0.AR5.Leiden1.surf.net (145.145.162.30) 24.5ms
 9   esa-router.Customer.surf.net (145.145.20.6) 36.1ms
 10   [target] grid-medialab1.estec.esa.int (195.169.140.50):21 30.4ms

After obtaining better info about the ESTEC's infrastructure we would like to probe bandwidth from nodes around the problematic segment to localise the bottleneck.

-- PavelCimbal - 01 Feb 2005