Network connection problems (2)
Reason: the ISP server did not respond because the server was turned off or the modem was not connected.
Solution: please contact the system administrator.
Reason: the line is busy.
Solution: try calling again later, or contact your system administrator.
Cause: there is a problem with the hardware.
Solution: verify that the ISDN adapter is properly installed and configured.
Cause: the phone number is not configured correctly.
Solution: in some cases, each B channel on an ISDN line has its own number, while in other cases, two B channels share one number. The telecom company can tell you how many ISDN lines there are.
Reason: if it is in the United States or Canada, the service profile identifier (SPID) is not configured correctly. SPID usually consists of phone numbers with numbers attached at the beginning, end or both ends. SPID helps switches understand the types of devices connected to the line and route calls to the appropriate devices on the line. If the ISDN channel requires SPID, but the input is not correct, the device will not be able to make or receive calls.
Solution: verify that SPID is entered correctly.
Cause: poor line conditions (for example, too much interference) cause the connection to be interrupted.
Solution: wait a few minutes before trying to dial.
Reason: you have not enabled line type negotiation or cannot connect with the selected line type.
Solution: enable line type negotiation.
Reason: ISDN switching equipment is busy.
Solution: try again later.
Reason: the digiboard card is too old.
Solution: if you do not have the latest pcimac isa digiboard card (serial number a14308 or higher), please contact digiboard for replacement.
Failed to connect using X.25.
Cause: dial pad is configured with wrong x.3 parameters or serial settings.
Solution: if the remote access server is running and you cannot connect to it directly through an X.25 smart card or an external pad, modify the dialing pad x.3 parameters or serial settings. Ask the system administrator what the correct settings are.
Cause: the new pad.inf entry is incorrect.
Solution: you can check other pad.inf entries for direct and external pads and view their comments. A line analyzer or terminal program may be required to see the pad response. For dialing pad items, use the item in pad.inf as an example, and note the comments attached to the example.
Cause: the modem is not compatible.
Solution: if the modem connected to the dial-up pad is slower than it should be, replace it with a compatible modem.
Cause: the line to the remote access server is congested. If a connection has been established, but the network drive will be disconnected, and your session will be disconnected or you will encounter a network error, the reason may be congestion on the leased line of the remote access server.
For example, if four clients connect at 9600 BPS (via dial-up pad), the server-side leased line is required to be 38400 BPS (four times 9600). If the leased line does not have enough bandwidth, it may cause timeout and reduce the performance of the connected client. This example assumes that routing and remote access uses the full bandwidth. If routing and remote access share bandwidth, fewer connections can be established.
Solution: your system administrator needs to verify that the speed of the leased line can support all COM ports to connect at various speeds used by the client when dialing in.
Failed to connect via PPTP.
Cause: TCP / IP connection problems prevent you from connecting to the PPTP server.
Solution: you or your system administrator can use ipconfig and Ping commands to verify the connection to the server.
Reason: Winsock proxy client is active.
Solution: when Winsock proxy client is active, VPN connection cannot work. Before the virtual network connection encapsulates the packets, Winsock proxy has redirected the packets to the proxy server. Ask your system administrator to disable the Winsock proxy client.
Reason: you do not have the appropriate connection and domain access rights on the remote access server.
Solution: please contact the system administrator.
Reason: if the TCP / IP protocol is used, there is no unique TCP / IP address.
Solution: please contact the system administrator.
Cause: name resolution problems prevent you from resolving names to IP addresses.
Solution: specify a fully qualified domain name and IP address in the connection.
Connection using PPP or TCP / IP utility failed.
Reason: the server does not support LCP extension.
Solution: if you cannot use PPP to connect to the server, or the remote computer terminates your connection, the server may not support LCP extension. In network connections, clear the enable LCP extension check box.
Cause: IP header compression prevents the TCP / IP utility from running. If you have successfully connected to the remote server using PPP, but the TCP / IP utility is not running, the problem may be IP header compression.
Solution: after IP header compression is turned off, try reconnecting.
A specific program has encountered an Internet connection problem, and Internet connection sharing, windows firewall, or both are enabled.
Cause: windows firewall, Internet connection sharing, or both prevent programs from successfully establishing full two-way communication across the Internet.
Solution: get internet connection sharing and windows firewall plug-ins from the program manufacturer. Internet connection sharing and windows firewall plug-in can solve any Internet connection problems encountered by a specific program when Internet connection sharing (ICS) or windows firewall is enabled. Plug ins are provided as executable files on disk or Internet. Because Internet connection sharing and windows firewall plug-ins may make your network insecure, they should only be installed if their source is trusted. For more information, see using Internet connection sharing and windows firewall plug-in.
The connection established using Internet connection sharing failed.
Cause: the wrong LAN network adapter is shared.
Solution: computers with internet connection sharing need two connections. One connection, usually a network adapter, connects to a computer on a home or small office network, while the other connects the home or small office network to the Internet. You need to make sure that Internet connection sharing is enabled on the connection that connects your home or small office network to the Internet.
Reason: TCP / IP is not installed in home or small office network.
Solution: by default, TCP / IP protocol is installed on computers running Windows XP, Windows 2000, Windows Millennium Edition, Windows 98 and windows NT 4.0. If the user on the home or small office network is running other operating systems, please check whether the TCP / IP protocol is installed on the computer.
Cause: if the user on the home or small office network cannot connect to the Internet, the TCP / IP configuration on the computer may be incorrect.
Solution: make sure the following TCP / IP settings are established on the local connection:
IP address: automatically obtain IP address (through DHCP)
DNS server: get DNS server address automatically
Default gateway: not specified
For computers running Windows 95, Windows 98, Windows Millennium or Windows NT 4.0, you can find the TCP / IP settings in network in control panel.
Reason: if home or small office network users cannot connect to the Internet, they need to modify their Internet Options.
Solution: you must modify the Internet Options for Internet connection sharing. For more information, see configuring Internet Options for Internet connection sharing.
Reason: the Internet connection sharing service was not started.
Solution: use event viewer to confirm that the Internet connection sharing service is started.
Reason: the name resolution of the Internet connection sharing computer is not configured correctly.
Solution: you may need to configure the wins or DNS name resolution service on your computer. If a computer in a home or small office network cannot resolve its name to an IP address, you can use the ipconfig command to check the name resolution configuration of the Internet connection sharing computer. There are two ways to resolve ISP configuration names
Statically assigned name server
You must manually configure the TCP / IP protocol with the IP address of the name server provided by your ISP. If you have a statically assigned name server, you can use the ipconfig command to get the IP address of your configured name server at any time.
Dynamically assigned name server
No manual configuration is required. As soon as you dial ISP, you will dynamically assign the IP address of the name server provided by ISP. If the name server is dynamically assigned, you must run the ipconfig command "after connecting to the ISP.".
Reason: if you cannot play games over the Internet, the protocol used by this application is not convertible.
Solution: try running the program from an Internet connection to a shared computer. If the program can run normally there, but not on other computers in the home or small office network, then the program may not be convertible.
Reason: if you cannot play games on the Internet, the program may not be configured on the computer running Internet connection sharing.
Solution: verify that the program is configured correctly, including the port number.
Reason: if Internet users cannot see a service (such as a web server) on a home or small office network, the service is not configured correctly.
Solution: verify that the service is configured correctly, including port number and TCP / IP address.
Reason: if users on the home network cannot access Internet sites with friendly names, there is a DNS resolution problem.
Solution: when accessing Internet resources, please let users on your home or small office network use fully qualified domain name or IP address.
There is no response when using a local connection.
Cause: there may be a problem with the network adapter.
Solution: try the following:
Check the appearance of the local connection icon. Depending on the status of the local connection, the local connection icon in the Network Connections folder will look different. Also, if the local connection media is disconnected (for example, the cable is unplugged), a status icon is displayed in the notification area. For more information, see local connection.
Use device manager to verify that your network adapter is working properly.
Cause: the local connection cable may not be plugged into the network adapter.
Solution: check that the local connection cable is plugged into the network adapter.
Some or all of the programs are not working properly when using a laptop to connect to an ISP.
Reason: when using ISP connection, Winsock proxy client may prevent the program from running normally.
Solution: if you are a mobile user and are using a laptop in a company environment, you may need to disable the Microsoft Winsock proxy client (WSP client in control panel) when you dial up to an ISP or other network using the same computer. For example, if you use a laptop in the office and use the same computer at home to connect to an ISP or other network, you may encounter problems running various applications when using an ISP connection（ For example, your program may not be able to find the required resource or server.) If this is the case, please prohibit the Microsoft Winsock proxy client (the WSP client in the control panel) from running the programs that you often run when using your laptop in the company office.
The incoming connection client does not see resources other than the incoming connection computer.