Results 1 to 2 of 2
  1.    #1  
    Just spotted this over at www.sprintusers.com under FAQ postings and thought it worth copying...

    Error
    Displayed Message
    Definition

    Communication Errors

    201
    MIC Error #201: Server not responding. Please try again.
    NO_RESPONSE, The server is not responding to the browser's request.

    208
    MIC Error #208: Communication error. Please try again.
    CONNECTION_CLOSED. The connection to the server has been closed

    TLS Errors

    407
    MIC Error #407: Server certificate is bad or expired.
    BAD_CERTIFICATE. The secured session cannot be completed because the server's certificate is unacceptable to the browser.

    Mobile IP Error Messages (from Network)

    67
    Error Code 67 Registration failure. Your username and/or password may be incorrect. Please try again. Note: Repeated entries of an invalid password during a 24-hour period will result in a 20-minute suspension. A suspended username may not be used until the suspension expires, even when submitted with the correct password. If this problem persists, you may need to contact Sprint.
    Mobile node failed authentication, this means that the mobile failed to register with the PDSN. This could be a result of improper provisioning or a change to the users username or password.

    97
    Error Code 97 Network Error. Sign in failed. Please wait a moment and try again. If this problem persists, you may need to contact Sprint.
    Missing NAI

    106
    Error Code 106 System Error. Sign in failed. Please try again. If the problem persists, turn your phone off then turn it back on again.
    Stale challenge

    Mobile IP Error Messages (from Handset)

    1012
    Error Code #1012: Could not prepare data services. Please try again later. If the problem persists, you may need to contact Sprint.
    Client-initiated IOTA fails, general failure code for all IOTA failures.

    2048
    Error Code #2048: Network Busy. Please try again.
    Handset cannot acquire a traffic channel - This error message appears after 60 seconds of not being able to acquire a traffic channel

    3000
    Error Code #3000: Network timeout. Please try again.
    Traffic channel is open but the handset gets no response from network (analogous to a Mobile IP setup failure). This error message appears after 60 seconds of no response.

    4000
    Error Code #4000: Network timeout. Please try again.
    User has a Mobile IP connection but no socket response from the Gateway. This error message appears after 60 seconds of no response.

    HTTP Error Messages

    408
    HTTP Error 408: Server timed out. The web page or document you requested was not returned in a timely manner. Please try again. If the problem persists, it is likely that the service is incompatible with your browser.
    HTTP Error 408: The server timed out while waiting for your request. The server did not receive a complete request within a ceratain amount of time. If you are in a very slow network connection you might try the request again. If the problem keeps occuring the problem maybe due to some incompatible browser you are using.

    502
    HTTP Error 502: There is a problem with the page you are trying to reach and it cannot be displayed.
    HTTP Error 502: Bad Gateway. The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.

    503
    HTTP Error 503: Service unavailable. The web service that you requested is unavailable. Please try again at a later time. If this problem persists, please contact Sprint.
    HTTP Error 503: Out of Resources. The requested service is unavailable. The service you requested is temporarily unavailable. The service may be unavailable because the server has reached the limit of the number of requests it is willing to serve in parallel. This number depends on the type of request you were submitting. If the document you requested was a dynamic document it may be that the application generating these documents is currently not running.
  2. #2  
    Thanks for this info. This looks great for troubleshooting.
    -Mike

Posting Permissions