Ronage
06-22-2002, 04:13 PM
I have recently set up two completely separate networks consisting of only a few machines with <very> little traffic.
One is straight Win NT4.0, the other is straight Win2K with no mixing of OS's.
In each case I am observing the same problem...
When using TCP/IP vs. NetBEUI (Win2K) or IPX (NT) there is a SIGNIFICANT response lag when accessing shared/mounted directories.
Although the actual transfer rates for copying files etc. are solid across the board (all machines have 100MBps NIC's), when it comes to simply listing the directory contents on a drive connected via TCP, it can take 10,30 even 60 seconds depending on the file count to list the contents.
If I bind IPX or NetBEUI to MS Client instead of TCP IP the sme directories list almost instantaneously.
Are there performance issues with TCP/IP or am I missing something here???
Thank you very much for any input here!!
One is straight Win NT4.0, the other is straight Win2K with no mixing of OS's.
In each case I am observing the same problem...
When using TCP/IP vs. NetBEUI (Win2K) or IPX (NT) there is a SIGNIFICANT response lag when accessing shared/mounted directories.
Although the actual transfer rates for copying files etc. are solid across the board (all machines have 100MBps NIC's), when it comes to simply listing the directory contents on a drive connected via TCP, it can take 10,30 even 60 seconds depending on the file count to list the contents.
If I bind IPX or NetBEUI to MS Client instead of TCP IP the sme directories list almost instantaneously.
Are there performance issues with TCP/IP or am I missing something here???
Thank you very much for any input here!!