Perhaps I am mistaken on the underlying KiX technology, but essentially a net use function is taking place by KiX initiating a command of some time for Windows to use the shared resource (perhaps simply executing NET USE - notice the KiX syntax USE H:, USE H: /DELETE which closely mimics NET USE command structure ).

In another example, try a KiX COPY command, and compare the speed with a Windows COPY command. Would you expect one command to perform faster than the other? I would not.

Alex's suggestion may provide some performance improvement. I can not say as I have never tested. I recommend you attempt some timing tests to see if in fact there is significant performance improvement.

Additionally, you likely would need to look at where the login script resides when executing - on the client, or on the server. You certainly want the DLL's on the clients. As for the script(s) on the client, well, that is not a solution I would put in place yet.

Regardless, each network admin must decide the acceptable performance of the systems connecting to their network. I am comfortable telling my end users they will suffer a performance lag via dial-up. They in fact are quite prepared to accept that a dial-up 56/33/28kbps connection will never perform any network functions at the same speed as the 100mbps LAN. Should such timing differrences translate into a material impact on business operations, then of course one should consider revisiting it.

Bill