There’s such a problem : we have a Win32-application that should be launched from remote share resource (for instance, from locally mapped G: \\SERVER\SHARE) (BTW, doesn’t matter whether is it mapped or not – problem is the same)
In all possible (but the one described lower) environments, this application requires approx. 15 M of incoming local traffic to get loaded (measured through “netstat –e” before and after the launch)
But in the problem environment (client PC’s are Win2000-based, SERVER (where share resides) also)
It takes nearly 40 M to get loaded !!! And all the meg’s are get by “microsoft-ds” (445/TCP) and by this exact application (tested with “windump” and “filemon” tools)
If the share is on the other Win2K server – the problem is the same ! If the client is XP based – the problem is GONE ! (15M again)
It’s evidently issue of Win2000 and most possible – on client side [only].
Filemon logs give some info for analysis – along with the necessary 15M traffic, the problem sessions for some reason GET nearly TWICE th body of application from direct share (UNC) path, instead of using G: (like \\SERVER\SHARE\APPLIC.EXE)
If anyone has some ideas, how to handle this, I’d be quite appreciate to see those ideas !