file transfer speed in a network

hai all, i am working in a network having morethan 200 windows XP sysetm,our network uses CISCO switch and router. we have a remote site which connected trhough 4MBps MAN conectivity through one off services provides frame relay.We need to connect our remote site alltime coz, our file servers are in remote site.

some time we feel our network soo slow , even it took morethan 2 min to open a 1 mb .doc file .

1,How can i rectify this issue 2,How can i check file transering speed ( any software can use for this??) 3.How it possible to check how many bandwidth is used by each off computers

i hertlly requesting all to help me for solving this problem .

Reply to
Loading thread data ...

Every version of Windows since NT3.5 has a tool called Perfmon.exe. It can monitor and count the usage of just about every aspect of the computer's operation. It can remotely monitor other windows boxes.

Your Cisco switch and router probably have network management capability which can got you usage figures for the pipe.

Various versions of netmon, a network monitering tool, are included with the different versions of Windows Server.

If your servers are *nix-based, there are lots of monitoring tools available to you.

Reply to
Al Dykes

Bipin wrote in part:

I use `ttcp` to test network speed. It avoids the disk and occasionally software bottlenecks. It measures OS & hardware. By running it as UDP, I can get an idea if TCP is mistuned. But you need access from both ends. When you can't (usually across the Internet), then hit some reliable site and see what kind of ftp throughput you get.

Usually by using a sniffer such as `tcpdump` or monitoring areas on a managed switch.

-- Robert

Reply to
Robert Redelmeier

ttcp would be ok if the file transfer mechanism is FTP. If it is SMB, (or NFS) then a request/response test would be a better match - say a netperf TCP_RR test with suitable request/response sizes to match what SMB is doing.

Be very cautious about UDP bulk transfer benchmarks (ttcp, netperf UDP_STREAM). They often have no end-to-end flow control and as such may completely saturate a bottleneck link, much to the chagrin of other users.

When diagnosing "performance issues" I often start by looking for retransmissions. Especially for request/response sorts of applications, even a single lost TCP segment can ruin the whole thing. So, check things like netstat statistics, or its platform equivalent. If you can also check link-level statistics and statistics at the switch(es) and/or the devices joining your LAN's to the MAN.

rick jones

Reply to
Rick Jones

Agreed. Even the venerable ping can be very useful.

Isn't that the idea :) but a wise precaution to limit testing, especially test uninterrupted duration.

Always a good idea. Bad/marginal cabling can easily cause bit errors that usually result in retransmits.

-- Robert

Reply to
Robert Redelmeier

move the servers to the location with the 200 clients - would be a quick fix

Reply to
developers Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.