Today, let’s talk about one computer management console issue.
You are trying to view the information about client sessions by clicking Shared Folders -> Sessions in the Computer Management console. In some senario It could take a long time to populate the information, and the console may stop responding or just hang.
Computer management will try its best to resolve the client IP address to user-friendly NetBIOS name.
In IPv6 and IPv4 coexist environment, and clients use \\NetBIOS to access share folders. If the NetBIOS name cannot be resolved, it shows the IPv6 address immediately. However, if clients are using \\IPv4 to access share folder, the failure of resolving to the NetBIOS name causes the Computer Management console to hang.
To solve this issue, you can follow the steps below
1. Disable NetBIOS over TCP/IP.
To disable it:
2. Configure reverse lookup zone in DNS server.
Links from our forum:
Edit:We have published a Knowledge Base article for this issue: http://support.microsoft.com/kb/2454039/en-us
This did not fix the problem for me,
Wow, this totally worked for us! Windows 2003 (SBS 2003), and for ages, we haven't been able to use the "Sessions" pane of Computer Management.
Forgot to say that it was only step 1 that was needed to fix the problem. We already had the reverse lookup configured in DNS (AD integrated).
Thank you! Step 1 worked!
I have a windows server 2008 that I don't use as a DNS Server. Step 1 didn't fix the issue. Anything else?
Been stuck with this problem for a month, but with the step 1, boom, it's fix, totally worked for me.
Many Thanks for you..
What you might want to do is just access it through fsmgmt from a client machine. That's what I do since I have the same issues with 2008 and 2012. I just run fsmgmt on my Win 7 client and remote connect to that server.
I tried was you said, as well as the fix that everyone else has tried above, It still lags when I use fsmgmt.msc from my client PC. I turned off Netbios and create a reverse lookup. Nothing has worked for me. I recently moved everyones Homedirs from a 2003
server to 2012 R2 and this problem started. Please let me know if you have found any other way of fixing this. (anyone?)