No Name Resolution with SLIP Account in Windows NT 4.0 (157891)
The information in this article applies to:
- Microsoft Windows NT Server 4.0
- Microsoft Windows NT Workstation 4.0
This article was previously published under Q157891 SYMPTOMS
When you try to access Internet resources using a SLIP (Serial Line
Internet Protocol) account with Windows NT version 4.0 Dial-Up Networking,
you may receive error messages similar to the following message:
Internet Explorer cannot open the Internet site http://<web address>
The site was not found. Make sure the address is correct, and try
again.
NOTE: The error message you receive may differ depending on the program
you are using to access the Internet resource.
CAUSE
This issue may be caused by one of the following situations:
- You have your name server addresses specified in the Dial-Up Networking
phonebook entry.
- You have enabled the Force IP Header Compression option in the phone-
book entry.
RESOLUTION
To work around this issue use one of the following methods:
Name Server Address Specified in Phonebook Entry- Double-click My Computer, and then double-click Dial-Up Networking.
- Click the appropriate entry in the Phonebook Entry To Dial box.
- Click More, click Edit Entry, and then click Modem Properties.
- Click Server, click TCP/IP Settings, and then change the Primary
DNS entry to all zeros.
- Click OK twice.
- Use the right mouse button to click Network Neighborhood, and then
click Properties on the menu that appears.
- Click Protocols, click TCP/IP Protocol, and then click Properties.
- Click DNS, click Add, enter the address for your name server, and
then click Add.
- Click OK twice.
Force IP Header Compression Option Enabled- Double-click My Computer, and then double-click Dial-Up Networking.
- Click the appropriate entry in the Phonebook Entry To Dial box.
- Click More, click Edit Entry, and then click Modem Properties.
- Click Server, click TCP/IP Settings, and then click the Force IP
Header Compression check box to clear it.
- Click OK twice.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Windows NT
version 4.0. We are researching this problem and will post new information
here in the Microsoft Knowledge Base as it becomes available.
Modification Type: | Major | Last Reviewed: | 8/10/2001 |
---|
Keywords: | kbnetwork KB157891 |
---|
|