Microsoft Reduce Customer Effort Center

Our team drives product feedback based on solid data, it drives proactive issue prevention and ultimately, drives improvements around products based on customer feedback.

Computer Management console will hang when populate the information on shared folder sessions

Computer Management console will hang when populate the information on shared folder sessions

  • Comments 5
  • Likes

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.

 

Reason:

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:

  • Run ncpa.cpl
  • Right click the NIC
  • select properties
  • click TCPIPV4
  • click advanced
  • click WINS
  • choose Disable Netbios over TCPIP

 

2.       Configure reverse lookup zone in DNS server.

 

Links from our forum:

http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2management/Thread/338F2902-5F57-4515-BBF5-3D96DBF6FEBD

 

Edit:We have published a Knowledge Base article for this issue: http://support.microsoft.com/kb/2454039/en-us

Comments
  • 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.

    THANK YOU!

  • 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?

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment