Al,

I tried just about every configuration there is and because it is being tested on several different networks, I think a bad ethernet card is out. I found an interesting cause and effect though...

When 1 Win98 pc hits the app on the NT server, the cpu utilization on the server stays around 2-4 % during my testing. When I add an NT pc to the app and search again on the Win98 pc, the cpu % jumped to 22. When I run the test on NT pc cpu % did not change on the server. What could make the cpu work harder for the Win98 pc when another user is in the app than when the Win98 pc is in the app all by itself? If I get in the app with just NT pc's 3,4, or 5 pc's the test does not cause the cpu utilization to jump at all.

Again, I really could use some help in figuring this out, MS is involved but the more help the merrier!

John Brooks


>>>Is your NT server set up with a proxy server (e.g. WinGate) so that all LAN users can access the Internet through its (shared) modem? If so, there typically is a setting in the proxy server that tells it not to act as a proxy for addresses on the local subnet. If this has NOT been set, the proxy server will slow down local traffic by acting as a proxy for all local LAN communications over TCP/IP.
>>
>>The LAN has no proxy server, pretty much it is a straight NT 4.0 server with 4 workstations attached via a hub.
>>
>>John Brooks
>
>Hmmm... you may have already tried this, but I'll mention it anyways... have you confirmed the problem occurs with ANY 2 workstations as opposed to ANY 1? That is, if you ran the test with PC #1 and added PC #2, you then tested with PC #3 and added PC #4 (etc. etc.) Also SWITCH OFF any workstations not directly involved in the testing.
>
>You could also try running the second instance of the program on the server console, or as another instance on a workstation.
>
>I would hate to think that a jabbering network card in 1 PC was causing all this.