The problem seems to be with direct connect connections only.If you connect using:Server: config278vm0Service:5151User:sdePwd:sdeYou won't see this issue. Workaround: In Task Manager select DesktopIndexingServer.exe and if you see its CPU constantly at 0 (typically happens after indexing and the process is hung), its safe to kill that process so the status in the dialog changes from Indexing... to Active.