So, I've been dealing with an extremely frustrating problem (probably have 3-4 hours already sunk in this so far and not much to show for it). I'm trying to bring the first Vista (Business) PC up at a customer location and we immediately noticed a big speed problem when accessing processes on a network share. Unfortunately, our server is still an old NT 4 server, but we're really not having any other problems with it (which is why it's still around -- though we do have plans to move off of it soon, just not soon enough for this particular problem). We mostly have a mix of Win2k and WinXP clients, none of which exhibit this problem. I've narrowed the situation down to running a certain very small (8k) command line application in a shared (mapped via UNC) directory on this NT 4 server. When I call this application when it's in its normal directory (with around 500 files -- other apps, etc.), it takes a good 2 - 3s to execute. Normally, the load time for this program is almost zero. As in 0.04 - 0.10s -- not even noticeable. 2-3s is *hugely* noticeable and very disruptive when trying to run any kind of process which makes use of many network-shared utilities (which is about all of our processes). I've also done some testing to notice that it seems to scale up proportionately with the number of other files in the directory. It's almost as if Vista is performing some (unnecessary) operation on each file in the same directory. This behavior even happens if I apply an explicit full path to the 8k test program, so I don't think Vista should be legitimately doing any kind of directory search, etc. I've also dusted off Wireshark and done some packet sniffs on the situation and it definitely appears that Vista is doing some sort of "FIND_FIRST2" and "FIND_NEXT2" call requests, the summary of which looks like: 46 0.017291 192.168.1.174 192.168.1.6 SMB Trans2 Request, FIND_FIRST2, Pattern: \WINDOWS\* ... 66 0.615356 192.168.1.174 192.168.1.6 SMB Trans2 Request, FIND_NEXT2, Continue: $NtUninstallKB936782_WMP9$ and then later I see some responses like this: 95 1.217526 192.168.1.6 192.168.1.174 SMB Trans2 Response<unknown>[transact continuation] Note, in *this* case, I had my 8k app location in C:\Windows (on a different PC on the network (an XP one)), but I've had it in many different directories, and I don't think the actual directory has much to do with it. It seems like any location, at least on the network, will elicit these issues. To clarify, I should point out that this does *not* seem to be an NT 4-related issue, because very similar behavior is exhibited when the test program is run on an XP machine via a network share. This seems to be a Vista issue, or at least something this particular machine is doing. I've got SP2 installed on the Vista machine. I have tried many different fixes, including the typical things people have mentioned as problems with slowed network access, but I think my issue isn't directly related to that (e.g., I tested one large file copy that was running at around 250Mb over my Gigabit link). Does anyone have any suggestions for something else for me to try? Does this sound familiar? Thanks, John Lawler

Still have this problem -- does anyone have any ideas or any other troubleshooting steps to try?