ConfigMgr: Admin Console not working on Windows 7 machine

I was experiencing issues where ConfigMgr 07 console was not working from a Windows 7 machine

Everything else works great and they have no issues related to the client functionality, however when I  tried opening the ConfigMgr console it kept saying that SQL is not available. I ran through the following diagnostics and it could be worth mentioning:

If you are trying to troubleshoot the ConfigMgr console from a remote machine, please follow along and hopefully we’ll be able to get it right. Now, please note that the ConfigMgr console works like a charm if I launch it on the Site Server; It’s just the remote console which was not working.

Step 1

The first test for the SQL I generally stick to is the UDL Test. Here’s the more information on UDL Test on Faruk Celik’s blog. But the idea to do the UDL test is to make sure that we are able to connect to a given SQL instance or in other words at least our SQL services are running properly.

If you are able to connect to the SQL server or at least you see the SQL Server listed in there then we are on the right track.

Step 2

Check if we are able to ping the SQL Server , Then try tel135net to the SQL Server on the port
We enabled the 135 port on the Network Firewall and we were able to TELNET but remote console still not working.

Step 3

Also I tried connecting to the SQL Windows Management Instrumentation from WINDOWS 7 machine using the WBEMTEST but that failed with the RPC SERVER UNAVAILABLE

So this was a clear indication that the network was locked, So if you have a Network Firewall which id blocking this, follow these steps below to allow the RPC
We changed the RPC service to only pick ports from 5000-5100 by creating the registry key on the site server.

1. Add the Internet key under: HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc

2. Under the Internet key, add the values “Ports” (MULTI_SZ), “PortsInternetAvailable” (REG_SZ), and “UseInternetPorts” (REG_SZ).
In this example ports 5000 through 5100 inclusive have been arbitrarily selected to help illustrate how the new registry key can be configured. For example, the new registry key appears as follows:

3. Ports: REG_MULTI_SZ: 5000-5100
PortsInternetAvailable: REG_SZ: Y
UseInternetPorts: REG_SZ: Y

4. Restart the server. All applications that use RPC dynamic port allocation use ports 5000 through 5100, inclusive. In most environments, a minimum of 100 ports should be opened, because several system services rely on these RPC ports to communicate with each other.

5. We also ensured that the port 5000-5100 were also opened on the network firewall.

6. We then restarted the ConfigMgr server and ore remote console started working.

ADDITIONAL INFORMATION

How to configure RPC dynamic port allocation to work with firewalls
http://support.microsoft.com/kb/154596

Network ports were blocked and RPC was using the dynamic port allocation (It randomly picked any port greater than 1024)

I hope this will help.