Network Controller Problems - HP ProLiant ML100 Series User Manual

Be sure no line interference exists. Retry the connection by dialing the number several times. If
2.
conditions remain poor, contact the telephone company to have the line tested.
Be sure an incoming call is not breaking the connection due to call waiting. Disable call waiting, and
3.
then reestablish the connection.
AT command initialization string is not working
Action: Use the most basic string possible to perform the task. The default initialization string is
AT&F&C1&D2&K3.
Connection errors are occurring
Action:
Check the maximum baud rate for the modem to which you are connecting, and then change the baud
1.
rate to match.
If the line you are accessing requires error control to be turned off, do so using the AT command
2.
AT&Q6%C0.
Be sure no line interference exists. Retry the connection by dialing the number several times. If
3.
conditions remain poor, contact the telephone company to have the line tested.
Be sure the modem is current and compliant with CCITT and Bell standards. Replace with a supported
4.
modem if needed.
You are unable to connect to an online subscription service
Action:
If the line you are accessing requires error control to be turned off, do so using the AT command
1.
AT&Q6%C0.
If the ISP you are accessing requires access at a decreased baud rate, reconfigure the communications
2.
software to correct the connection baud rate to match the ISP.
If this does not work, force a slower baud rate (14400 baud) with the AT command AT&Q6N0S37=11.
3.
You are unable to connect at 56 Kbps
Action:
Find out the maximum baud rate at which the ISP connects, and change the settings to reflect this.
1.
Reattempt to connect at a lower baud rate.
Be sure no line interference exists. Retry the connection by dialing the number several times. If
2.
conditions remain poor, contact the telephone company to have the line tested.

Network controller problems

Network controller is installed but not working
Action:
Check the network controller LEDs to see if any statuses indicate the source of the problem. For LED
1.
information, refer to the network controller documentation.
Be sure no loose connections (on page 58) exist.
2.
Troubleshooting 87