Alistair Tonner wrote: > > I wonder ... are the boxes inside purely WIN boxes? No. I've tested mostly all combinations of servers (win/linux), clients (win/linux), client apps. (ftp/ie/leech/etc.), and the conclusion is clear: Once the connection has gone through, then the data throughput is what it is expected to be. Example: one large file takes the same amount of time, regardless of it being transferred directly vs. through the router. But many small files are considerable slower (up to 100 times slower). I have got reports that (external and internal) websites can take very long time to come up, but once it has connected to the server, then the data comes very quickly. I have got a gut feeling that this initial connection opening delay is the same we are seeing on the FTP, only its more evident on FTP. If I'm connecting to websites internally, the complete page comes up very quickly. But if I try to connect to the same page, via. the router, then the pictures takes very long time to complete. So, I'm rephrasing the question: "What can be the reason that the router is having such long initial delays on connections?" > -- What sort of outside connection do you have? 2.3MBit SDSL. The data from my router is going into a DSL router from cisco. I.e internet -- cisco dsl router -- linux router -- lan. However for the testing on this example, the data goes from lan to linux router to lan again, never via. the cisco router nor the dsl link. The linux router is sole reason for the delay! And I dont think this is a MTU issue here, as the router and the server and the client is all sharing the same network switch. If a packet from the client is received on the router addressed to the server, then it will be received on eth0 and transmitted on eth0 again. Thanks, Svein E. Seldal
