1. User might have capitalise the user ID. Turn off the CAPS lock and erase the User name and password and try again.Remind the user that the user ID and password is case-sensitive.
2. Wrong telephone number specified
3. Wrong modem specified in dialer
4. User's Account is suspended

1. Configure dialer and proxy settings in the dialer
2. Ask user to make payment at the outlet and keep the receipt and ask the supervisor there to activate the account.

1. Errors in system file structure
2. Dialup Adaptor is missing

1. Do a scandisk twice if errors are found and restart the computer
2. Next reinstall dialup adaptor and TCP/IP

1. Can't see the website even proxy is set
2. Dialer  settings in TCP/IP is assigned wrongly
3. The setting in the TCP/IP properties settings have been modified so reinstallation in TCP/IP and dialup adaptor will not work

1. Check dialer properties in TCP/IP
2. Reinstall TCP/IP and dialup adaptor 
3. Look into the properties of the TCP/IP, set to the follow: 

IP -> Obtain an IP address Automatically 
WINS Configuration -> Use DHCP for WINS Resolution 
Gateway -> Everything is blank 
DNS Configuration -> Disable DNS 
ADVANCED -> Property is set to None
BINDINGS -> Client for Microsoft Network 

3. Use the "Release All" option in the Winipcfg.exe utility to release all IP addresses bound to the network adapter.

4. Make sure the winsock.dll  and the wsock32.dll file is of the correct size.
a) winsock.dll  (for win95 => 42kb)
b) winsock.dll  (for win98 => 21kb)
c) wsock32.dll (for win95 => 65kb)
d) wsock32.dll (for win98 => 40kb)

5. Check that user does not have other Dialup Networking 1.2 / 1.3 installed in the Add / Remove settings list. Uninstall the DUN 1.2 / 1.3. Restart the computer and remove all TCP/IP and dialup adaptor. Then reinstall  the component for DUN for the original Windows. If it prompts for older version is found, do you want to override, answer no. User the older version instead to replace the current version.

1. Do a scandisk to check for errors
2. Reinstall TCP/IP and dial up adaptor.

2) Unable to locate the network socket connection in Netscape

or

Fatal Error! Cannot read IP configuration

Fatal IP

Occurs when:
(1) there is currently no network client installed.

(2) When you ping a website name or TCP/IP address you receive either of the following error messages:
 

Bad IP address < Web address >

PING: transmit failed, error code 10091

or

you get error code 10043 after doing PING test

1. Remove Dial up networking and restart the computer
2. Do a scandisk and then reinstall Dial up networking again.
3. If you get Error code 10043. This indicates that the TCP/IP stack is not being initialized. This error can occur if you have TCP/IP files with a .386 extension in your Windows folder from the Microsoft Windows for Workgroups 32-bit TCP/IP stack.
   
   NOTE : This can also occur if tcp/ip is not installed.
   
   RESOLUTION
   To resolve this issue, rename the following files in the Windows folder. Rename these files to have a different extension, such as an .old extension:
   
   Vdhcp.386
   Vip.386
   Vnbt.386
   Vtcp.386
   Vtdi.386
   
   NOTE : Do not delete these files if you are using America Online (AOL). Deleting these files could result in an inability to connect to AOL.
4. Check that your windows files are installed correctly for the version of your windows. If you have upgraded to Winsock2, Dialup Networking 1.3 or upgrade, or has installed USB update before, then this might be the reason it has failed. Backup your current winsock.dll and wsock32.dll files first then reboot to DOS and rename them. They are located in the windows system directory.
5. At the command prompt, type the following commands, pressing ENTER after each command.
6. Type in:
   cd\ windows \ws2bakup
   ws2bakup.bat
   exit
7. This will now restore your previous windows winsock.dll and wsock32.dll files back to your windows.
8. Restart the computer to try again.

1. Check dialer settings
2. Reinstall TCP/IP

Wrong password

Check dialer settings

1. Perform diagnostic test on modem
2. Change modem in the dialer properties

1. Create a new dialer, make sure that the dialer properties are set properly (press dial properties button and check that there is no area code and the country is set to Singapore)
2. Check if the TCP/IP is present in the Network, in Control Panel

Check if you have the following files in the c:\windows\system  folder:
a. Wsock32.dll
b. Wsock32n.dll
c. Rnaui.dll
d. Msvcrt20.dll
e. Rasapi32.dll
f. Rnaapp.exe

1. Restart your computer and go to F8
2. Rename all the files in (A to F) on the left of the screen
3. Restart Windows normally
4. Extract a copy of the new files for the Windows CAB files from the CD-ROM.

Or alternatively you can use Winzip to search for the files in the CAB files in the CD ROM and do a manual extract, by using Winzip to unzip it.

Extract Original Compressed Windows Files

1. Reinstall TCP/IP and dialup adaptor
2. Reinstall modem driver

or 

The modem is being use by another dialup networking connnection or another program. Disconnect the connection or close the program and try again.

or

The port is already open

1. Press Ctrl+Alt+Del to terminate the program "Rnapp" or Restart the computer to clear away the used memory
2. After re-opening Windows, remember to close all the fax before establishing a connection to the internet
3. Check if any program on the task bar is affecting the COM port of the modem. Right-click and disable all programs on taskbar.

Rasphone.pbk is in the system32\RAS subdirectory of the windowsNT folder

The remote access script files (Pad.inf, modem.inf and switch.inf) are in the \System32\RAS subdirectory in Windows NT folder

or

The port was disconnected by the remote machine.

or

The link has been disconnected for one of the following reasons:

1) An unrecoverable phone line error.
2) A noisy line.
Disconnection by the system administrator.
A conflict in configuration parameters between the client and the remote computer.

1. Shut down the computer, turn off the power.
2. Or perform a scandisk to check for errors
3. Reinstall TCP/IP and dialup adaptor

1. To re-establish the link, check that the authentication, encryption and DNS parameters defined in the DUN phonebook match those on the remote computer.
2. Try also lowering the speed (which I don't recommend)

or

The port was disconnected due to hardware failure.

or

The link has been disconnected for one of the following reasons:

An unrecoverable error occurred in your modem (or other communicaiton device).

An unrecoverable error occurred on your communications port. Your modem cable has come unplugged.

1. Conflict with IRQ setup in the Device Manager
2. Hardware failure
3. If the modem is using a new serial port assignment due to new devices installed by Windows hardware detection.
4. Programs in the StartUp folder can also cause this error message.
5. Wrong modem driver or windows does not recognise the driver after installation due corrupted modem driver overtime.

1. Check physical connection of cable and modem to computer.
2. Remove "?" or "!" 
3. Get driver for modem to install
4. Change the properties of the Dial-Up Networking connection to use the new modem settings
5. To disable the programs in the Startup folder, activate the System Configuration Utility (Win98) and in the startup folder, click on the program's check box to clear it
6. Try testing it using the Hyperterminal program or Windows NT terminal.

/

The port is already in use or is not configured for Remote Access dialout.

1. External modem turned off
2. If the Telephon.ini files is missing or damaged.

1. Switch on the modem
2. Perform diagnostic test
3. Install modem driver if test fail. Try setting up standard modem
4. To resolve missing or damage telephoni.ini file go to: Q120221

/

Unknown error

1. Check dialer settings

or

Internal authentication error

1. Temporary Remote Access dialer error in computer's cache
2. Dialup Adaptor is not working or missing
3. Double TCP/IP in Network
4. If it is ADSL it might be Radius Login Error. That means that the server can't recognise the user.
5. Encrypted Password is turned on

1. Shutdown and restart the computer
2. Reinstall Dialup Adaptor
3. If using Win NT check the NT event log for detailed warnings or errors. Take note of the NetBIOS error code if you are using WinNT.
4. If it is ADSL connectivity, then check with your ISP to test out the account on their side. Try the account with the 56k modem. If it can go through, that means that your ADSL account is having problem and not a line issue.
5. Turn off encrypted password in the dialer.

/

The Remote Access server is not responding

(Server not available)

1. Wrong Tel number
2. Corrupted dialer
3. Internal settings in dialer is wrong
4. Wrong modem driver (standard modem was used or corrupted exisiting driver)
5. Check with backend configuration of your service provider and line provider.

1. Correct the tel number
2. Create a new dialer
3. Check all properties in the dialer
4. Make sure there is no conflict in Device Manager
5. Load in modem driver again. (Shut down and turn off computer and wait for 5 sec before powering up to windows to detect new hardware. Then insert manufacturer's disk into windows)
6. Backend Radius or PPP temination device might not be online. Always do verification of password, fingering of the account to check if the account has been batched or not. Test the user's account at your station to verify or get the user to login with another userid.

The modem has been turned off.

The modem is not securely connected to the computer. Make sure the cable is fasten to both modem and the computer.

The modem is experiencing a hardware glitch.

1. User does not have a dialer.
2. COM port is in used by another device or software* eg. After installing Palm Pilot III, V.
3. Corrupted modem driver

1. Create a dialer for user. It is missing.
2. Remove software and configure again
3. Remove extra number in the dialer properties
4. Wrong tel number
5. Need to reinstall modem driver

1. Connection is set in the phone hole in the modem which is the wrong hole
2. Dialer in Dialup Networking is missing or not created (If user claims that he is able to get connected using another dialer but can't use the specified dialer that is newly created or originally setup even though the settings are set properly, DO A PING TEST and WINIPCFG USING on that specified dialer, if is fails or that the IP address is 0.0.0.0 then it proves that the connection was not established. The computer shows the wrong result)
3. Dialer might be corrupted or modem driver is damaged.

1. Do a scandisk to check for file errors first
2. Check line in home to see if the connection is set in the line hole in the modem.
3. Check dialer properties to remove area code.
4. Reinstall TCP/IP and dialup adaptor
5. Extra numbers in the dialer property box e.g (001)
6. Reinstall modem driver
7. Make a new dialer

1. Connect to wrong hole
2. Dialer modem is selected wrongly
3. Modem is spoilt

1. Connect to LINE hole
2. Check dialer settings or make a new connection
3. Connect to another computer to verify

1.  CAPS lock might be turned on
2. Wrong userid or user type their own name inside the field
3. Extra numbers like area code in dialer properties
4. Account might be suspended

1. Turn off CAPS lock
2. Wrong Userid
3. Wrong Password
4. Dialer settings in the logon box should be erased

1.  Try lowering the baud rate and disable any modem features that may be set.

or

A PPP conversation was started, but was terminated because the remote computer did not respond within an appropriate time.

1. Check dialer settings
2. Reinstall TCP/IP and dialup 

1. Could be cause by poor line quality or by a problem at the server.

or

Dial up networking could not negotiate a compatible set of network protocols

Missing TCP/IP or missing TCP/IP and dial up adaptor

NBEUI protocol not installed. (NT)

Protocol mismatch

1. Put a tick in TCP/IP in the dialup in Dialup networking dialer.
2. Reinstall TCP/IP
3. Check winsock.dll or winsock32.dll if their size is correct. For Win95, Winsock32.dll should be 42kb, for Win98, Wsock32.dll should be 40kb. If there are additional winsock files you should rename them
4. PPP termination device is running a different protocol. Change SS
   encapsulation scheme to match

Remote computer not responding

No protocols configured

* User PC might experience a hang or not responding for 30secs.
* Problem might also occur when user is using VPN. User might not experience any problem over normal dialup

Basic Setting for Most ADSL Modem:

Framing - VC Mux
Modemop mode - t1.413
protocol - PPPoA
VCI - 100
VPI - 0

* Click start-programs-GlobeSpan DSL modem-Configure-Settings.
VCI - 100
VPI - 0
Encapsulation - RFC 2364 PPPoATM Null Encapsulation
Modulation - Multimode
Auto-Modulation - Ticked

or

A PPP link control protocol conversion was started, but was terminated at the request of the remote computer.

2. Re-dial again. Check the dialer properties of the dialer

3. User has set call back number in the phone book entry. Ask user to remove the extra number.

4. You may also check under the Phone book, network settings, called request LCP extension that must be checked for callback to work properly.

5. * When checking through the phone book entries, remember to remove LCP extension. All settings are off except for TCP/IP (remember?)* If you don't know where is it, open the phone book entry and look under the server tab. Remove the tick mark from there * See picture

The following information on LCP Extensions is from the RAS Help file:

Extract from Microsoft: The Request LCP extensions (RFC 1570) check box enables newer PPP features. These extensions may cause problems when calling servers with older PPP software. Clear the Request LCP extensions (RFC 1570) check box only if consistent problems occur. Clearing the checkbox prevents LCP from sending Time-Remaining and Identification packets and requesting callback during the LCP negotiation of PPP.

6. Most likely an error occurred on the server (NT)

1. Uninstall and then reinstall Dialup Networking in the Control Panel.
2. See solution at Q174579