Article ID: 239870 - Last Review: November 1, 2006 - Revision: 1.5 RasDial Returns an Invalid Error CodeThis article was previously published under Q239870 On This PageSYMPTOMS
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.
RESOLUTIONWindows NT Server or Workstation 4.0To 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:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
(http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)
Windows NT Server 4.0, Terminal Server EditionTo 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 the Microsoft Knowledge Base:152734
(http://support.microsoft.com/kb/152734/EN-US/
)
How to Obtain the Latest Windows NT 4.0 Service Pack
STATUSMicrosoft 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. MORE INFORMATION
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:
| Article Translations
|
Back to the top
