To remove Dial-Up Networking
This section describes problems you may encounter in using Dial-Up Networking, virtual private networking, and Mobile Computing.
This section describes problems that you may encounter in using Dial-Up Networking and how to resolve them. Windows 98 provides a troubleshooting aid for Dial-Up Networking in Help. Try using the troubleshooting aid before taking the troubleshooting steps included in this section.
You can monitor any Dial-Up Networking session for possible problems by enabling the Record a Log File option. This produces a Ppplog.txt file in the Windows directory, which you can reference to find out the cause of a problem. For more information, see Knowledge Base Article Q156435, "How to Interpret the Ppplog.txt File."
If you cancel Setup while Dial-Up Networking is copying files and then restart the computer, you will see an error message stating that the following files are missing:
If these files are missing, Dial-Up Networking will not function correctly. You must remove and reinstall Dial-Up Networking.
To remove Dial-Up Networking
To reinstall Dial-Up Networking, follow the procedures outlined in "Installing Dial-Up Networking" earlier in this chapter.
Caution
Never remove Dial-Up Networking components using Network in Control Panel.
If you see an error message stating that Dial-Up Networking cannot find the specified modem, check the following:
If you receive an error message that the computer you are connecting to has not responded, check the following items:
In the properties for the Windows 95 or Windows 98 dial-up server, verify that the user name is in the list of users that are allowed access.
To set Dial-Up Networking Server to allow caller access options
The User name list appears only if you have chosen user-level security for the dial-up server. The type of security is selected in the Network option in Control Panel.
If the dial-up client is also running File and Printer Services for NetWare Networks, the File and Printer Sharing service automatically becomes the default server, but it cannot receive the information needed to find the remote servers.
Disable File and Printer Sharing Service for NetWare Networks when you make the dial-up connection.
Check the settings for the dial-up server type and software compression.
To verify dial-up server and compression options in Dial-Up Networking
For more information, see the troubleshooting section in Chapter 21, "Modems and Communications Tools."
The password for the Dial-Up Networking server is stored in the Rna.pwl file. However, simply deleting this file or removing and reinstalling Dial-Up Networking may not remove the password. If you set the Dial-Up Networking server to monitor for calls and then delete the Rna.pwl file, the password is not removed, because it is stored in memory. If you shut down Windows 98 at this point, the Rna.pwl file is re-created with the password in memory.
To replace a forgotten password in a Dial-Up Networking server
Note
When you first connect to the Dial-Up Networking server, an error message states that the password file is missing or corrupt for every modem device you have installed. If you have any null modem devices installed (for example, when you run Direct Cable Connection it installs a modem device for every COM and LPT port you have), this error message also appears.
If you are connected to a LAN and you make a PPP or VPN connection, you might lose connectivity to some of the servers on your LAN. Likewise, if you connect to the Internet, then make a VPN connection to another network, you might lose connectivity to the Internet itself. For information about the cause of this problem and its solution, see "Technical Notes on Dial-Up and Virtual Private Networking," earlier in this chapter.
If you entered TAPI codes, an area code, or a country code in one connection, but Dial-Up Networking does not use those codes when you use the connection, make sure that all your connections use the TAPI codes.
To verify that all your connections use the TAPI codes
This section describes common virtual private networking problems and explains how to correct them.
This is by design. Do not attempt to remove Dial-Up Networking components using Network in Control Panel. If you need to remove virtual private networking, do so using Add/Remove Programs in Control Panel.
If you cannot connect to a VPN server, you can begin to diagnose the problem by looking at the status messages that appear when you attempt to make a connection. If the connection is successful, you will see the following messages:
If the connection fails before you see the "Verifying name and password" message, you might have a problem with DNS name resolution, or the VPN server might not be responding. If the connection fails before you see the "Verifying name and password" message and gives you the error message that the other computer is not responding, a computer along the way might be filtering out Generic Routing Encapsulation (GRE) packets, which are required for VPN to work.
However, if you do see the message "verifying name and password," your PPP connection succeeded and PPTP is working, and you probably have a problem with your user name and password.
You can also check the following items.
Verify that you are properly connected to the Internet.
Make sure that your Internet connection is working properly.
To check that your connection to the Internet is working properly:
If ping succeeds, your Internet connection is working properly.
If ping succeeds, you are properly connected to the Internet, but you are not properly connected to your DNS server. You should be able to connect to your VPN server by typing its IP address instead of its host name.
– Or –
If ping fails, you might not be connected to the Internet. Contact your ISP.
Ping the VPN server.
Ping the host name or IP address of the VPN server.
If you receive a response, you are properly connected to the VPN server, and you might have entered an incorrect user name or password.
If you do not receive a response, the administrator of the VPN server might have turned on PPTP filtering. This prevents you from pinging the VPN server. Contact the administrator of that server.
Check for a firewall.
Firewalls sometimes filter out PPTP packets. Contact your ISP and the administrator of your corporate server and ask if they are using a firewall. If they are, request that they pass TCP port 1723 and IP protocol 47 (the GRE protocol).
Because PPTP is a secure protocol, adding TCP port 1723 and IP protocol 47 will not affect the security of the firewall.
Make sure your ISP is not filtering out PPTP.
Contact your ISP and ask if it filters out GRE packets. If so, request that it pass GRE protocol 47.
Check for a proxy server.
It is not possible to create a VPN tunnel that passes through a proxy server such as a computer running Microsoft Proxy Server. Therefore, if your internal network’s proxy server handles all Internet traffic, including PPTP traffic, you will not be able to create a VPN tunnel to access resources on the internal network.
If you can connect to the VPN tunnel server, but you cannot perform a domain logon to the target network, verify that you have configured the connection to your VPN server to allow you to perform a domain logon to the target network.
To verify your VPN configuration
If your VPN connection is slow, follow the procedures outlined below.
You might be able to improve your performance by changing settings in your ISP connection. Specifically, you can improve performance by deselecting the option Log on to network and by deselecting all network protocols you are not using. To do so, follow the steps outlined in the procedure in the "Configuring Options for the Server to Which You Are Connecting" section earlier in this chapter. For information about other issues you should consider when setting up a connection to the Internet, see "Configuring a Connection to the Internet" earlier in this chapter.
To check the speed of your Internet connection, ping Internet sites you can normally ping. If ping shows a response time of more than five seconds, you have a slow Internet connection. Contact your ISP.
If you do not have problems with your Internet connection, but the connection to your VPN server is still slow, the VPN server might be overloaded. Contact the administrator of the VPN server.
If you have a mobile computer that has a directly attached network adapter card that you use to access resources on your corporate network, you might have trouble connecting to some of your network’s hosts after disconnecting a mobile computer such as a laptop from your corporate network and then making a VPN connection to your corporate network. This happens because your computer is still forwarding all its network traffic to the network adapter instead of over the VPN connection. To force your computer to forward its network traffic over the VPN connection, disable your network adapter using the following procedure.
To disable your network adapter
If this procedure does not work, but you are using DHCP to automatically assign IP addresses, you can try using winipcfg to release your IP address. For more information, see Chapter 15, "Network Adapters and Protocols."
To release your IP address
This section presents problems that might occur when you are using Direct Cable Connection.
As general troubleshooting steps, verify the following:
If you cannot find the host computer using Direct Cable Connection, follow the procedures in "Using Direct Cable Connection" earlier in this chapter to make sure Direct Cable Connection has been installed correctly on the host computer and is working.
If Direct Cable Connection is working properly but you still cannot find the host computer, make sure you have Client for Microsoft Networks is installed. For more information, see Chapter 16, "Windows 98 on Microsoft Networks."
The host computer and guest computer can communicate using the TCP/IP protocol, which is generally installed by default. However, if you want the host computer to act as a gateway to a TCP/IP network, you should make sure that NetBEUI is installed as well. For more information, see Chapter 15, "Network Adapters and Protocols."
Both Dial-Up Networking and Direct Cable Connection use the same network interface (Pppmac.vxd). You cannot have more than one instance of Pppmac.vxd running at one time, so you cannot use both Direct Cable Connection and Dial-Up Networking at the same time. You must close either Direct Cable Connection or Dial-Up Networking.
Following are several factors to check as you begin to troubleshoot your infrared connection:
Try moving the devices closer together or farther apart. The devices must be no more than three feet apart, and some devices work best if kept at least six inches apart. Make sure that there are no obstructions between the devices.
Infrared devices produce an "arc" of infrared light. This arc is usually between 15 and 30 degrees. Try realigning the devices so that they fall within this arc.
Direct sunlight contains infrared light and can cause degradation of the infrared signal between devices. If this occurs, try blocking the sunlight or moving the devices closer together.
Use the Limit Connection Speed To option in the Infrared Monitor Options tab to limit the connection speed to 19.2 kbps. If this is successful, you can experiment with establishing a connection at a higher speed. This is especially important if an infrared adapter is attached to a COM port that is using an 8250 UART instead of a 16550 UART or if the adapter is connected to a relatively slow computer.
Ensure that the application you are using is configured for the virtual port, not the physical port that the infrared device is attached to. Keep in mind that, as with all communications and printer ports, only one application can use the virtual port at one time.
Open the Infrared Monitor and verify that all settings are correct.
If you select the wrong physical COM port during installation of the infrared communications driver, the infrared device will be unable to discover another infrared device within range. If this happens, put an actively searching infrared device close to the computer’s infrared device and reinstall infrared on a different COM port until the infrared device on the computer discovers the nearby infrared device.
You might need to change the batteries in an infrared adapter or plug the AC power into an infrared adapter.
This section discusses general problems that might occur when using infrared. For information about specific infrared hardware, see the next section.
Communication over a virtual COM port link between two computers might not be reliable if a printer’s infrared adapter is also within range. You should move the adapter out of range.
You might experience problems transferring files over an infrared link. If the Zmodem protocol fails with a link speed of 115.2 kbps, use the Infrared Monitor Limit Connection Speed To tab to limit the link speed to 19.2 kbps and then retry the Zmodem file transfer.
This section discusses common problems you might experience with specific infrared hardware. For information about general problems you might encounter, see the previous section.
The Texas Instruments TravelMate 5000 might communicate over an infrared link only at very low speeds (9600 bps). The Sharp PC 3050 might communicate over an infrared link only at speeds between 9600 bps and 19.2 kbps.
For the Hewlett Packard Omnibook 4000C or the Hewlett Packard Omnibook 600CT, which have built-in infrared ports, you must install a special echo-canceling serial driver in addition to the components that make up the infrared communications driver. The echo-canceling driver, and instructions on how to install it, are available from Hewlett-Packard.
The Adaptec AIRport 2000 infrared adapter can be powered in three ways: by the serial port, by installed AA batteries, or by an external power supply. In some cases the serial port might not provide sufficient power for the operation of the adapter. This can cause reduced operating range and/or a failure to find another infrared device that is nearby and aligned correctly. If you suspect this problem, connect an AC adapter or add four AA batteries to the battery compartment in the infrared adapter. This will assure sufficient power. In some instances, you might also need to separate the adapter by at least six inches from the other infrared device.
If an ActiSys 220L infrared adapter is attached to a computer and used to print to a printer that is using an Extended Systems ESI-9580 printer infrared adapter, or a Hewlett Packard DeskJet 340, you must use the Options tab in the Infrared Monitor properties to limit the connection speed to 19.2 kbps in order to print successfully. If the infrared devices are allowed to negotiate the connection speed automatically without setting this limit, they will negotiate a higher connection speed, and a program will be unable to print.
| For more information about | See this resource | ||||
|---|---|---|---|---|---|
| Internet drafts and RFCs | http://www.ietf.org/. | ||||
| Virtual private networking | http://www.microsoft.com/communications/. | ||||
| Windows NT remote access servers | Windows NT Server Networking Guide for Windows NT Server version 4.0 and the Networking Supplement for the Windows NT Server 4.0. |