Direct Connection doesn't work
The direct modem connection requires that the communication between the communications port and the modem works smoothly.  Given the wide variety of modems and computers installed getting the settings correct may at times require some extra attention. This section includes points to look at if the Direct Modem connection fails to dial and synchronize with the NIST timeserver.

Modem Fails to Dial

• Phone line  or extension is not set up to dial out.

• Check that phone line is set up to dial a long distance number.

• Turn handshaking on or off. Some modems require that handshaking be set to allow the modem to dial. Settings can be first tested by using the Modem Test Screen. Try turning the RTS and DTR enable on or off, adjust both the Type Handshake to None or RTS.

• Try a different Attention string. If the Attention string is invalid for the modem in use, then the modem will not be able to continue. Try the different Attention strings available in the Templates on the Direct Modem Connection form.

Modem Dials NIST but Doesn't Synchronize

• Try turning RTS handshaking off (if it is on). The modem might be waiting for a change in state from the communication port that never comes.

• Try turning off Flow Control and/or MNP data compression in the modem. An Attention string of AT&K0%C0 will often do both on many modems. Try the different Attention strings available in the Templates on the Direct Modem Connection form.

• Force the modem to transmit with a maximum link speed of 2400 baud.  Some modems have a command that limits the maximum speed the modem will converse in. ( V.34 modems sometimes use AT&N3)  Some V.90 modems allow you to force the modem into Bell V.22, 2400 baud modem (try AT+MS=V22B,0,2400)

Modem Hangs after Call

• If the call is successful but the modem is 'stuck' after calling the NIST try turning off DTR. Sometimes DTR will cause the modem to hang-up prematurely.