Microsoft KB Archive/193209

= Gethostbyname Not Working Correctly with Only DUN Installed =

Article ID: 193209

Article Last Modified on 11/1/2006

-

APPLIES TO


 * Microsoft Windows NT Server 4.0, Terminal Server Edition
 * Microsoft Windows NT Server 4.0 Standard Edition
 * Microsoft Windows NT Workstation 4.0 Developer Edition
 * Microsoft Windows NT Server 4.0 Enterprise Edition

-



This article was previously published under Q193209



SYMPTOMS
If your system has only Dial Up Networking (DUN) installed and you are not connected to anything, name resolution to your local host may fail.



RESOLUTION
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or 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 How to Obtain the Latest Windows NT 4.0 Service Pack



STATUS
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 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.



MORE INFORMATION
To test name resolution to your local host, perform the following steps:


 * 1) Click Start, click Programs, and click Command Prompt.
 * 2) At the command prompt type the following:

c:\ping localhost

Name resolution is successful if you get a response back that looks like the following:

  Pinging [127.0.0.1] with 32 bytes of data: Reply from 127.0.0.1: bytes=32 time<10ms TTL=128 Reply from 127.0.0.1: bytes=32 time<10ms TTL=128 Reply from 127.0.0.1: bytes=32 time<10ms TTL=128 Reply from 127.0.0.1: bytes=32 time<10ms TTL=128

Name resolution is not working if the response is:

  bad ip address

Additional query words: RAS DUN Name Resolution

Keywords: kbbug kbfix KB193209

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.