![]() ![]() When you try to ping the Routing and Remote Access server from a local computer by using the server's NetBIOS name or fully qualified domain name (FQDN), the computer tries to ping the wrong IP address. The server is not responding when client requests an update. If the Routing and Remote Access server is running ISA Server 2000, and a user on a client computer selects Update Now in the Firewall Client Options dialog box, the user receives the following error message: For example, "The page cannot be displayed" may appear in the Web browser with a "cannot find server or DNS" error message. If the Routing and Remote Access server is also running Microsoft Internet Security and Acceleration (ISA) Server 2000, you can't browse the Web from client computers on the local network, regardless of whether the computers are configured to use Web Proxy or the Microsoft Firewall Client. ![]() The Domain Name System (DNS) or Windows Internet Name Server (WINS) service is installed and configured on the server that is running Routing and Remote Access.Īfter a remote computer connects to the Routing and Remote Access server by using a dial-up or a Virtual Private Networking (VPN) connection, one or more of the following symptoms may occur intermittently:.The Routing and Remote Access service is configured to permit incoming connections.This article provides a solution to name resolution and connectivity issues on a Routing and Remote Access Server that also runs DNS or WINS.Īpplies to: Windows Server 2012 R2, Windows Server 2016 Original KB number: 292822 SymptomsĪ computer that is running Microsoft Windows 2000 Server or Microsoft Windows Server 2003 may exhibit connectivity issues if the server is configured in the following manner:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |