Link to home
Start Free TrialLog in
Avatar of darrenburke
darrenburke

asked on

NT4 slow, WIn2k fast - NetBios over TCPIP?

Firstly this happens on all machines in my environment (servers, desktops, multiple hardware types and configs)

When I copy a file across a WAN link (Cisco PIX VPN over DS3's) from a NT4,0 machine to a WIn2k or a NT4.0 the data transfer rate is very slow.  Doing the same test with the same files from W2k to W2k is dramatically faster (about 10 times faster)

From looking at sniffer tracers the file copy to or from NT4.0 machines show the protocol as NetBIOS over TCPIP, Win2k to Win2k just shows TCPIP.

We have tried changing the default MTU/RWIN settings in the registry but this only has a minor impact on performance.

So my question is

What do Win2k machine talk to one another so much master that NT4.0?

Any ideas?
Avatar of mbruner
mbruner

The transfer is faster because they don't have the extra overhead of communicating using NetBIOS.  NetBIOS operates at OSI layer 5, so it relies on the lower layers to encapsulate it and transport it across routed networks.  Since Win2K communicates primarily using TCP/IP, it doesn't get slowed down encapsulationing / decapsulationing NetBIOS packets.
Avatar of darrenburke

ASKER

should the performance difference be so different?  Was NT4.0 always that slow?

From mbruner's answer, I would guess that doing FTP across those same links would have the desired effect of increasing the performance on your NT machines.
ASKER CERTIFIED SOLUTION
Avatar of mbruner
mbruner

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
darrenburke:
This old question needs to be finalized -- accept an answer, split points, or get a refund.  For information on your options, please click here-> http:/help/closing.jsp#1 
EXPERTS:
Post your closing recommendations!  No comment means you don't care.
My answer was close to correct.  Here is a link to Microsoft's answer and explanation to this problem:

http://support.microsoft.com/default.aspx?scid=kb;en-us;279282