Testing needed bandwidth on Windows 2000 network
Posted on 2004-09-03
I have a legacy database that runs on a windows 2000 member server. The database is all on the server, and the client has a terminal type window to it. This is not like using access and SQL were some of the processing is done on the client. This is all done on the back end.
We want to set up a laptop at an offsite location to access this database, but dial up is absolutely ludacris. The local cable company can offer us either a 128k or 256k line. I need to justify if either would be appropriate.
So I set up a systems monitor to monitor the "bytes total", "bytes sent", and "bytes rec'd" for the NIC of this server. So far the avg total is around 30,000 bytes or 30K. Did I do this properly, am I right in deciding that the 128k line should be enough for this one laptop. Granted it does not have to have the error checking that the POTS lines would. I know one other person who uses ISDN (both channels) and says that it is fine.
I just want to know if I'm leaving anything out. I know there is the whole bits bytes deal where the leased line would be kilobits, not bytes...
Any help is appreciated,