I'm having major performance issues on a Windows 7 professional PC opening and saving Word, Excel and Adobe documents in the IFS of a System i (9406-520 V6R1 at 10047. All Netserver PTFs applied). I've applied the IBM recommended changes to the Windows 7 PCs - web client is starting automatically and offline files are disabled. I have seen no change in performance. If you've been able to resolve the problem, please share the solution with me. I do not have this problem with XP or Windows 2K PCs. And I have an XP PC with Office 2007 that's working fine. There's something wrong between Windows 7 and Netserver. IBM ran a trace and gave me the following response NetServer development has reviewed the trace and found that this is a case of the Windows client spending a lot of time trying to access /srvsvc. Windows attempts to open a named pipe (srvsvc) that NetServer does not support. NetServer returns a normal OPERATION_NOT_SUPPORTED error, It appears that the Windows side is doing some sort of delayed retry of an operation after NetServer returns to error on the connection to srvsvc NetServer development has also tried doing some changes in their code so that they return an access denied or file not found error, hoping that Windows 7 would handle it differently, but results did not change. Here's what I can find about srvsvc. This all came from a Google search and not from a Microsoft site, so it is word of mouth only. Srvsvc (C:WinNTsystem32srvsvc.dll) is part of SMB (Server Message Block) and CIFS(Common Internet File System) protocols used by windows. One online source says it is a 'file system driver' and that it supplies connections that are requested by redirectors on the client side and gives them access to the resources they request. It sounds like it passes both requests and data. From several traces we've seen, it appears the XP client accepts the failure to connect to srvsvc and falls back to some classic LANMAN flows to get the information it wants, whereas the Windows 7 machine does not. I would be happy to work with someone from Microsoft to try to gain insight into this problem It is valid for a file server to reject the srvsvc call as is done by NetServer and ultimately Microsoft's code, which is issuing that call, needs to better handle the failure.