I would definitly have your NT administrator check the configuration! On that small of a system you should not have any performance problems. Unless there is some other necessity for it, I would drop NetBUI and just run straight TCP/IP. I don't remember the reason why, but I believe NetBUI will slow down your network. The only other thing I would suggest is checking your locking strategy, but if everything runs fine on the Novell network that probably isn't it.

If it wasn't for NT's integration with so many products, I would still be using Novell. For file and print services, it still beats the pants off of NT and does not keep connections to a file open even after a workstation has been properly logged off and shut-down. I have had a workstation properly shutdown and powered off for up to 20 minutes with NT still showing a connection to a file!
>David,
>
>This is a small LAN that is having the problem, NT server, 1 hub, 4 pc's with ethernet for all. TCP/IP and NetBUEI protocols. When the 2nd user gets in performance drops by 300% and stays that way until the everyone gets out and the 1st user can go back in, then user operates at normal speed.
>
>A similar network setup with Novell and IPX protocol shows no problems no matter how many workstations are in the app.
>
>John Brooks
>
>>John,
>>I would check your NT administrater and possible how your handling data across the LAN/WAN. I was running a 35 (10 people on local segment) person multi-user system across a T1 WAN with very little performance degradation. There was a large volume of transactions going across the T1 due to it being a real-time perpetual inventoring system.
>>
>>Thing that I did that helped:
>>1) Create a normalized database.
>>2)Placed executable and supporting file on an NT server on the other side of the T1.
>>3) Loaded small (50 records or less),static, look-up information that is used through-out the application at start-up time.
>>4) Used local view with table-buffering making sure to only read and write data when absolutely needed.
>>5) utilized transaction processing.
>>6) Used SYS(3051) to optimize SQL statements used in local views.
>>7) Created supporting indexes on table to help optimize SQL statements.
>>
>>Hope this helps
>>
>>Dave.
>>
>>>Hi,
>>>
>>>I've posted this before but I'm really curious if anyone with mutli-user apps running on an NT 4.0 server and using Win95/98 workstations has seen large performance slow downs when multiple users are in the application.
>>>
>>>If you run TCP/IP protocol and more than one user is in the app performance drops by 300%. It looks like the problem is in the TCP/IP protocol.
>>>
>>>I really could use some help on this.
>>>
>>>Thanks,
>>>
>>>John Brooks