This article was previously published under Q239870
This article has been archived. It is offered "as is" and will no longer be updated.
When you are dialing with RasDial, you may receive error code 676 ("The line is busy") instead of code 680 ("There is no dial tone") if your telephone cable is unplugged or you are using a bad phone line.
Windows NT Server or Workstation 4.0
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
152734how to obtain the latest windows nt 4.0 service pack
For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition.
This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.
The error status returned to the callback routine in code that calls RasDial is inaccurate. Despite the true cause of the issue, RAS returns error code 676 ("The line is busy") for line-related issues. Specifically, the following conditions result in error code 676:
Phone line not plugged into the modem
No carrier (voice, fax, and so on)
The proper RAS error codes for these conditions are 680, 678, 679, 677, and so on.