The Server Routing Protocol (SRP) is disconnected, and remains disconnected even after restarting BlackBerry Enterprise Server services. To diagnose the issue, perform the following tests:

1. Check that port 3101 is available.
2. Run bbsrptest.exe from C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Utility. If there is an error in this tool, determine the point of failure.
3. At the command prompt, type telnet **.srp.blackberry.com 3101 where ** is the appropriate country code described in https://www.blackberry.com/SRPAddressLookup/index.do

If these tests fail, the BlackBerry Enterprise Server will be unable to connect to the BlackBerry® Infrastructure. Troubleshoot, diagnose, and resolve any network related issues. Once you have ruled out networking issues, test the state of the SRP by doing the following:

1. Go to Start > Program Files > BlackBerry Enterprise Server > BlackBerry Server Configuration.
2. Click the BlackBerry Server tab and validate the SRP ID and key.

If this test fails, the SRP might be disabled.

• BlackBerry® Enterprise Server

The SRP might be disabled for the following reasons:

1. Most SRP ID issues are caused by network issues. For example, the BlackBerry Enterprise Server can be disconnected because of a routing rule change, which stops all BlackBerry traffic.
2. Multiple BlackBerry Enterprise Server instances are connecting concurrently with the same SRP ID. For example, a test or new BlackBerry Enterprise Server instance is implemented while the existing one is running.
   
3. A disabled SRP might be caused by the 'five in one' rule. If the SRP connection is lost and five reconnection attempts are made within one minute, the SRP ID will be disabled.
   
4. The BlackBerry Enterprise Server is using a trial or temporary SRP ID that has expired.
   
5. The BlackBerry Router is installed on a remote computer, and a communication problem exists between it and the BlackBerry Enterprise Server. If the BlackBerry Enterprise Server loses connection to the BlackBerry Router, the BlackBerry Dispatcher on the BlackBerry Enterprise Server will try to connect the SRP address itself. If the BlackBerry Router is still connecting to SRP, both the BlackBerry Router and the BlackBerry Dispatcher will connect using the same SRP ID simultaneously.
   
6. The BlackBerry Enterprise Server is connecting through a non-transparent proxy server to the Internet. The proxy server might create multiple connections to the SRP and cause the SRP ID to be disabled.
   
7. The network service between the BlackBerry Enterprise Server and the BlackBerry Infrastructure is interrupted. In this case, some data is still being transferred. For instance, the BlackBerry Enterprise Server tries to authenticate, and sends the SRP ID and authentication key to the BlackBerry Infrastructure. The request to authenticate is received, but the BlackBerry Enterprise Server does not receive a response from the BlackBerry Infrastructure, so it sends a new authentication attempt. If too many authentication attempts are sent within a short time period, the SRP becomes disabled.
   
8. Information is coming from a different host, and the BlackBerry Infrastructure terminates the original session and creates a new one. Also, some proxy servers might offer a round-robin feature for load balancing, where the source address of the proxy might change. If too many sessions are terminated and re-created within a short time period, the SRP ID might be disabled.