I have a legacy application that I honestly do not know a whole lot about running on Windows 2000. Sometimes printing is slow. It creates a file at a remote location (I will call this location B) and then prints it. In order to create this file, the user has to mount a network drive using a different account from the legacy domain (they are not logged onto this domain).
When printing from PCs at location A, it takes about 20 seconds. When installing the application on a domain controller (of the new domain, not the old one) at Location A printing takes about half that time (10 seconds).
I have run a capture from one of the PCs (XP), (I don't have one from the Domain Controller). Most of the traffic and time seems to be used from microsoft-ds and SMB traffic. Once the client is ready to talk to the printer that doesn't take much time. Does WINs / NetBIOS maybe have something to do with it? I don't know too much about these protocols.
Any ideas on what to look for?
Neither client (the DC or the PC) have WINs or the legacy domain for
ipconfig /all. Also, when I filter based on SMB.file == 'The file created by the repot' there is more than 10 times the packets and bytes. So there is far more SMB activity for that file.