Tuning network performance

Hi
I would continue using TCPIP as my one protocol. I would not add a sceond protocol to my network or change to netbeuui. Use performace monitor to monitor the speed of your connections. You can also install network monitor to monitor the stream of network data.

Based on the size of your network, getting the switch was probably the biggest performance improvement you could do right now. One thing to watch is the performance of your server NIC. You've got 13 drops trying to communicate with 1 at 100 Mbps.If the switch supports it, you might want to set the server port to Full duplex and set the workstation ports to Half duplex. That way, the server gets a boost in communicating with the end user and response from the server will likely be the benchmark by which your users evaluate performance. If you're really serious, you could install a second NIC in the server and set it up for 100 Mbps Full duplex as well, but that's a little overkill for 13 users.
I also agree with Joseph...stick with TCP/IP. We had some serious problems with NetBEui a few years ago. Users were setting their machines up to share files (we had Win95 at the time) and NetBEui would happily broadcast the "server's" availability every couple of seconds. This caused havoc on hubbed LAN segments with over 150 users on it! We've since replaced all hubs with switches and have moved to NT, establishing a standard configuration for each machine and locking them down so the users can't introduce changes. Best wishes,
ck

Take a look at MS Q article 146005. I had a similar situation and needed infomation on how to che for bottlenecks. The one change that I found most usefull was toass RAM to the server. With Q146005 and Permon, you can tune your network server highly, and at the same time cheaply (Both are free).

Carlos