Disclaimer:
This website is not affiliated with any organizations or corporations.
The content of this website is completely dictated by the author, on his own
personal time.
The content provided on this website is intended for informational purposes
only.
I make no warranties or guarantees that anything here is applicable to
your situation.
Any use of the information contained herein is at
your own risk.
Error 5
: Invalid Procedure Call
Error 5
: Unknown User (NT 4)
Error 6
: Overflow
Error 610: Another Dial Up Networking session is active
Error 621: Cannot Open Phonebook
Error
623: Cannot Find Phonebook Entry
Error
629: The port was disconnected by the remote computer
Error
630: The port was disconnected due to hardware failure
Error
633: The port is not available or the modem is not configured
Error 635: Unknown User
Error
645: Internal Authentication Error
Error
650: The Remote Access Server is not responding
Error 666: Device Not Ready
Error
667: Cannot read the media.ini file
Error
676: Then number you have dialed is busy
Error
678: The computer you are dialing does not answer.
Error 679: No carrier
Error 680: No
dial tone
Error
691: Could not establish a compatible set of network protocols
Error 718: PPP Time Out
Error 720: No Protocols configured
Error
731: The Protocol is not Configured
Error
745: An essential File is missing or Invalid Session Management Module
Error xxx: When all else fails
--------------------------------------------------------------------------------
Error 5: Invalid Procedure Call
This error usually occurs when DUN is not installed or is corrupt.
Double click Add/Remove Programs.
If Win95, look for any Dial-Up Networking updates in the list of
applications on the Install/Uninstall tab. If one is present, uninstall.
Click to the Windows Setup tab.
Remove all communications components. Click OK.
Do not restart yet.
Remove all network components. Click OK.
Do not restart yet.
Delete telephon.ini and then run tapiini.exe
Remove the "HKey_Current_User\RemoteAccess" registry key after backing the registry up.
Search for ws2bakup.bat If you find it, run the ws2bakup.bat file through a DOS window in Safe Mode to uninstall.
(Important: If you try to run it through normal windows, you will then
have to reboot into DOS MODE and run the batch file again in DOS)
Reinstall DUN only.
Say No to all version conflicts.
Reinstall the necessary network components in the network control panel.
Add/configure the client, adapter, and protocol in the network.
Say No to all version conflicts.
Click OK on the network control panel window.
Restart the computer.
Create/Configure a new connectoid.
Configure the Internet Control Panel to use the new DUN connection.
Try connecting again.
Back to Top
Error 5 (NT4): Unknown User
Retype the username and password before connecting.
Make sure that Domain is empty.
If member doesn't have the option to enter the username/password when going to dial the phonebook entry,
you may need to "unsave" the password.
To do this:
Double click My Computer.
Double click the Dial-Up Networking Icon.
Click the More button and select Edit entry and modem properties.
Click the Security Tab.
Check to make sure that "Accept any authentication
including clear text" is set.
At the bottom of the window click the button that says Unsave Password.
Click on the Server Tab.
Uncheck "Enable PPP LCP extensions"
Ok back out to the Dial-Up Networking window and attempt to dial the connection again.
For the member info you want to enter the username/password for the account. All lower case.
LEAVE DOMAIN BLANK
If you cannot "unsave" the password and dialing in after changing the other settings, you need to delete
the current phonebook entry and create a new one making sure the above settings are correct.
Back to Top
Error 380: Invalid Property Value
This error usually occurs when the connectoid has become corrupt.
Make a new connectoid and try again.
Remove the "HKey_Current_User\RemoteAccess" registry key after backing the registry up.
Restart the machine and make a new connectoid.
Back to Top
Error 6: Overflow
This error means the memory stack on the computer is corrupt and usually occurs when the
computer has been on for long periods of time without a reboot.
Restart the computer.
Try connecting again.
Back to Top
Error 610 Another Dial Up Networking session is active
This happens when Dial Up Networking does not shut down all the way.
Make sure the user is not currently connected.
Press Ctrl + Alt + Del. End task on Rnaapp.exe
Check for other communication software that might be trying to use the port.
Remove any shortcuts from the start menu and "msconfig" then reboot.
Press Ctrl + Alt + Del to insure that nothing is running but systray and explorer.
If a program does not appear in the start up folder or msconfig, check the
system.ini and the win.ini for load and run commands.
If you find any suspicious ones, remark them out by placing a semi-colon to the
left of them and restart the computer.
Rename the Telephon.ini file and run tapiini.exe then reboot.
Do a diagnostics on the modem inside the modem control panel to see if it responds.
Back to Top
Error 621: Cannot Open Phonebook
This error usually occurs because DUN is not installed or corrupt or the DUN connections are corrupt.
Double click Add/Remove Programs.
If Win95, look for any Dial-Up Networking updates in the list of
applications on the Install/Uninstall tab. If one is present, uninstall.
Click to the Windows Setup tab.
Remove all communications components. Click OK.
Do not restart yet.
Remove all network components. Click OK.
Do not restart yet.
Delete telephon.ini and then run tapiini.exe
Remove the "HKey_Current_User\RemoteAccess" registry key after backing the registry up.
Search for ws2bakup.bat If you find it, run the ws2bakup.bat file through a DOS window in Safe Mode to uninstall.
(Important: If you try to run it through normal windows, you will then
have to reboot into DOS MODE and run the batch file again in DOS)
Reinstall DUN only.
Say No to all version conflicts.
Reinstall the necessary network components in the network control panel.
Add/configure the client, adapter, and protocol in the network.
Say No to all version conflicts.
Click OK on the network control panel window.
Restart the computer.
Create/Configure a new connectoid.
Configure the Internet Control Panel to use the new DUN connection.
Try connecting again.
Back to Top
Error 623: Cannot Find Phonebook Entry
This problem is caused by the Total Access software having problems reading the registry entries for locations.
This fix also works if the customer has weird numbers showing up when they dial, but you can't seem to find them
entered into the properties of the connectoid, or in the dialing properties.
Delete telephon.ini and run tapiini.exe
Then after backing up the registry:
H_KEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Telephony
(Delete all location folders under telephony.)
Create/Configure a new connectoid named "EarthLink username@earthlink.net".
Configure the Internet Control Panel to use the new DUN connection.
Try connecting again.
Back to Top
Error 629 The port was disconnected by the remote computer
Switch PoPs
Check connectoid properties, uncheck cancel the call if not connected
within also make sure that error control, compress data, flow control, hardware are all
selected in the connectoid and also in the modems
control panel. Remove any init strings from both as well.
Make sure there is a uninterrupted connection between the modem and the telephone jack.
(i.e. no splitter, surge protectors, fax machine, etc...)
Change the WINS resolution value to disable in TCP/IP properties. If it's already disabled,
change it to use DHCP for wins resolution, click OK, go
back into the properties of TCP/IP and change it back to disabled.
click on ok and ok then reboot. Try connecting again.
Try adding an Initialization String
Back to Top
Error 630 The port was disconnected due to hardware failure
This problem, more often than not, stems from a
bad or incorrectly installed modem
Shutdown the computer , if the modem is external, make sure it is
turned off too then turn the modem back on BEFORE restarting the computer.
Then have the customer try to dial again. If the customer only has
one phone line, you should hear the modem try to access the phone
line, or the system will give the customer a no dial tone error.
Check connectoid properties, uncheck
"cancel the call if not connected within xx"
also make sure that error control, compress data, flow control, hardware are all
selected in the connectoid and also in the modems control panel.
remove any init strings from both as well.
Go to Modems Control Panel. Click on Diagnostics tab. Then hit more info on the correct com port.
If the modem fails to respond, try creating a standard modem.
Remember to change "connect using" in the connectoid.
Have customer try to dial again.
Check the system.ini file.
Under the boot heading make sure comm.drv=comm.drv.
Extract unimdm.tsp in to the c:\windows\system folder then reboot.
Create/configure a new connectoid in DUN.
If you still get the same error the modem is probably bad or incorrectly installed.
Back to Top
Error 633: The
port is not available or the modem is not configured
This can occur when the modem
is not installed properly, or if the wrong modem
is selected in the connectoid,
or
if the telephon.ini file is missing or damaged.
Make sure the connectoid has the proper modem selected.
Check more info on modem. If it fales, rip and reinstall modem.
Make sure correct modem is selected in DUN if you end up reinstalling it.
Try connecting again.
Open the registry editor and go to the following key:
Hkey_local_machine|Software|Microsoft|Windows|CurrentVersion|Telephony\Providers
Modify the value of the ProviderFilename0
value to TSP3216L.TSP
then open
Hkey_Current_User and delete the Remote
Access key
Find
the file named telephon.ini
and rename it to telephon.old
then run tapiini.exe
and reboot.
Create
a new connectoid.
Try connecting again.
extract unimdm.tsp
Back to Top
Error 635: Unknown User
Check the PoP.
Check the account status in RMOD.
Verify username and password entry in DUN connectoid.
Switch pops.
delete the *.pwl files
extract rasapi32.dll into the c:\windows\system folder
Change the WINS resolution value to disable in TCP/IP properties. If it's already disabled,
change it to use DHCP for wins resolution, click OK,
go back into the properties of tcp/ip and change it back to disabled.
Reboot
Create/Configure a new connectoid.
Configure the Internet Control Panel to use the new DUN connection.
Try connecting again.
Back to Top
Error 645 Internal Authentication Error
This error is usually caused by the PoP or corrupt/missing network stack.
Check the PoP
Check the network for:
Client for Microsoft Networks, Dial Up Adapter, and TCP/IP-->DUA
If they are all there: try switching PoPS. If 1 or more aren't:
Install missing component and remove anything unnecessary.
Reboot and try again.
Switch PoPs
The above should fix this 99% of the time, but if not...
Double click Add/Remove Programs.
If Win95, look for any Dial-Up Networking updates in the list of
applications on the Install/Uninstall tab. If one is present, uninstall.
Click to the Windows Setup tab.
Remove all communications components. Click OK.
Do not restart yet.
Remove all network components. Click OK.
Do not restart yet.
Delete telephon.ini and then run tapiini.exe
Remove the "HKey_Current_User\RemoteAccess" registry key after backing the registry up.
Search for ws2bakup.bat If you find it, run the ws2bakup.bat file through a DOS window in Safe Mode to uninstall.
(Important: If you try to run it through normal windows, you will then
have to reboot into DOS MODE and run the batch file again in DOS)
Reinstall DUN only.
Say No to all version conflicts.
Reinstall the necessary network components in the network control panel.
Add/configure the client, adapter, and protocol in the network.
Say No to all version conflicts.
Click OK on the network control panel window.
Restart the computer.
Create/Configure a new connectoid.
Configure the Internet Control Panel to use the new DUN connection.
Try connecting again.
Back to Top
Error 650 The Remote Access Server is not responding.
The server doesn't understand the info being sent by the modem. This error is often the result of the
combination of Microsoft Family Logon being present and a problem with KFlex, X2 or bad V.90.
Switch PoP's.
Clean up the network control panel so only
Client for Microsoft Networks, Dial Up Adapter and TCP/IP are there.
If they are all there then, change the WINS resolution value to disable in TCP/IP properties.
If it's already disabled, change it to
use DHCP for wins resolution, click OK,
go back into the properties of TCP/IP and change it back to disabled.
say no if it asks to reboot
Extract Rasapi32.dll then reboot.
Make a new connectoid
Try connecting again.
Uncheck the flow control in the modem configuration in the
connectoid and make sure that error correction is selected
Try connecting again.
If the modem is a 56k modem:
Disable 56K, connect at V.34 then update the drivers.
If they have a combination KFlex or X2 modem with V.90:
disable just KFlex or X2 and keep the v.90.
If they only have KFlex:
drop to v.34 and get a modem update.
If they only have X2:
drop to v.34 and get a modem update.
Have modem checked by local technician.
Back to Top
Error 666: Device Not Ready
This error is most often caused by one of the following:
The memory stack in the modem is corrupt
Windows has started in safe mode
The modem driver is corrupt or installed on the wrong COM port
Shutdown the computer, if the modem is external, make sure it is turned off too,
then turn the modem back on BEFORE restarting the computer.
Perform a diagnostics test on the modem's COM port.
If the modem fails to respond, try creating a standard modem.
Remember to change "connect using" in the connectoid.
Have customer try to dial again.
Check the system.ini file.
Under the boot heading make sure comm.drv=comm.drv.
Extract unimdm.tsp in to the c:\windows\system folder.
Remove the "HKey_Current_User\RemoteAccess" registry key
after backing up the registry. Then reboot.
Create/Configure a new connectoid.
Configure the Internet Control Panel to use the new DUN connection.
Try connecting again.
Back to Top
Error 667: Cannot read the media.ini file
The reg hack is:
HKLM\System\CurrentControlSet\Services\Remote Access\Authentication\SMM_files\PPP
Select Path in the list.
It should have "rasapi32.dll" for its value,
if it doesn't then modify it to say so.
Back to Top
Error 676:The number you have dialed is busy
This can happen if the PoP or the dialing properties are off.
Change PoPs.
Have the member dial the phone number on their handset
exactly as it is shown in the window. Call the member
back if necessary to find out what they got when dialing.
Check the Dialing Properties.
Make sure the customer has no extraneous or erroneous information.
Remove all prefix codes like *70 or 9,
Try using the area code or remove area code if it is already being dialed.
Back to Top
Error 678 The computer you are dialing is not answering
Switch PoPs.
Verify dialing properties.
Have the member dial the phone number on their handset
exactly as it is shown in the window. Call the member
back if necessary to find out what they got when dialing.
Change the WINS resolution value to disable in TCP/IP properties.
If it's already disabled, change it to use DHCP for wins resolution, click OK,
go back into the properties of TCP/IP and change it back to disabled.
click on ok and ok then reboot. Try connecting again.
Check for Line Noise in a terminal window.
Back to Top
Error 679: No carrier
Make sure there is a uninterrupted connection between the modem and the telephone jack.
(i.e. no splitter, surge protectors, fax machine, etc...)
Check for Line Noise in a terminal window.
Change the WINS resolution value to disable in TCP/IP properties.
If it's already disabled, change it to use DHCP for wins resolution,
click OK, go back into the properties of TCP/IP and change it back to disabled,
click on ok, then ok, and then reboot. Try connecting again.
Try adding an Initialization String
Back to Top
Error 680: No dial tone
This error occurs if the modem cannot initialize the line or if it can not hear a dial tone.
Make sure they don't have a telephone answering service that interrupts the initial second's dial tone
if they have new messages. If they do, have them check their messages before they try to connect or
enter 3
commas before the PoP number in the connectoid and then remove the check from
"wait for dial tone before dialing" on
the configure button, connection tab in the connectoid.
Make sure there is a uninterrupted connection between the modem and the telephone jack.
(i.e. no splitter, surge protectors, fax machine, etc...)
Have them listen for a dial tone with a telephone on the jack the computer would normally be plugged into.
Try switching phone cords or even phone jacks if it is possible.
If all this fails the modem is most likely broken or improperly installed.
Back to Top
Error 691 Could not establish a
compatible set of network protocols
This problem is usally a username/password entry issue or a congested PoP.
Check the account status and password in RMOD.
Check the PoP? Is it experiencing failures?
Switch PoPs.
Extract Rasapi32.dll from the cab files.
Say no when it asks to reboot
Delete all the *.pwl files.
Delete the telephon.ini file and then run tapiini.exe
Check the registry.
HKLM\System|CurrentControlSet\Services\Remote Access\Authentication\SMM_Files\PPP\Path=rasapi32.dll
Is the PPP Path correctly pointing to Rasapi32.dll?
Change the WINS resolution value to disable in TCP/IP properties. If it's already disabled,
change it to use DHCP for wins resolution, click OK,
go back into the properties of tTCP/IP and change it back to disabled.
click on ok and ok then reboot.
Try connecting again.
Check for Line Noise in a terminal window.
Back to Top
Error 718: PPP Time out
This error usually means the network is down.
It can also be a problem with TCP/IP.
Check the PoP.
Check the connectoid. Is server types set to PPP?
Uninstall/Reinstall Dial Up Networking.
Try adding an initialization string.
Back to Top
Error 720 No Protocols Configured
This error can be caused by a bad PoP or
missing/corrupt network components.
Check the network.
If Client for Microsoft Networks, DUA, and TCP/IP are already there then
Switch PoPs
If they aren't then install the missing component and
Flip the switch on wins resolution in the TCP/IP properties interface.
Reboot,
Create/configure a new connectoid and try connecting again.
Back to Top
Error 731:
The Protocol is Not Configured
Check the registry.
HKLM\System|CurrentControlSet\Services\Remote Access\Authentication\SMM_Files\PPP\Path=rasapi32.dll
Is the PPP Path correctly pointing to Rasapi32.dll?
Next, if the path does check out, make sure
Client for Microsoft Networks, DUA, and TCP/IP are in the Network
control panel.
Flip the switch on wins resolution in the TCP/IP properties interface.
Reboot,
Create/configure a new connectoid and try connecting again.
Back to Top
Error 745: An essential file is missing or Invalid Session Management Module
Check the registry.
HKLM\System|CurrentControlSet\Services\Remote Access\Authentication\SMM_Files\PPP\Path=rasapi32.dll
Is the PPP Path correctly pointing to Rasapi32.dll?
Check Add/Remove Programs for Compuserve Navigator PPP and RPADLL
remove them if either is present
Uninstall/reinstall communications.
Back to Top
--------------------------------------------------------------------------------
When all else fails
Some problems defy all fixes when you try them. In these cases, rebuild the entire network.
Now not everything on this list needs to be done for every problem, but you wouldn't be looking
at this if you knew the exact problem. Do everything here.
Search for ws2bakup.bat If you find it, run the ws2bakup.bat file through a DOS window in Safe Mode to uninstall.
(Important: If you try to run it through normal windows, you will then
have to reboot into DOS MODE and run the batch file again in DOS)
Double click Add/Remove Programs.
If Win95, look for any Dial-Up Networking updates in the list of
applications on the Install/Uninstall tab. If one is present, uninstall.
Click to the Windows Setup tab.
Remove all communications components. Click OK.
Do not restart yet.
Remove all network components. Click OK.
Do not restart yet.
Find and rename the following files:
vip.386, vtcp.386, vtdi.386,
vdhcp.386, vnbt.386,
pppmac.vxd
Delete the telephon.ini file and then run tapiini.exe
Delete any *.pwl files
Extract the winsock.dll to the c:\windows folder;
Extract
wsock32.dll,
rasapi32.dll,
rnathunk.dll, rnr20.dll,
afvxd.vxd, wsock.vxd,
wshtcp.vxd,
rnaui.dll, unimdm.tsp to
the c:\windows\system folder;
Extract
rna.inf to the c:\windows\inf folder.
Do not reboot.
Check the registry.
HKLM\System|CurrentControlSet\Services\Remote Access\Authentication\SMM_Files\PPP\Path=rasapi32.dll
Is the PPP Path correctly pointing to Rasapi32.dll?
Remove the Following Folders from the registry:
H_Key_Current_user\Remote Access &
H_Key_Local_Machine\System\Current Control Set\Services\Remote Access and H_KEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock 2 if it exists.
REBOOT
Reinstall Dial Up Networking Only.
Do not reboot yet.
Reinstall/Configure Network stack as necessary.
Delete any unnecessary components that DUN may have installed.
Make sure TCP/IP-->DUA is set as default protocol on the advanced tab of it's properties interface.
Reboot
Create and configure a new DUN connection.
Configure the Internet Control Panel to use the new DUN connection.
Set the new connectoid properties, uncheck cancel the call if not connected within
also make sure that error control, compress data, flow control, hardware are all
selected in the connectoid and also in the modems control panel.
remove any init strings from both as well.
Try connecting again.
Make sure there is a uninterrupted connection between the modem and the telephone jack.
(i.e. no splitter, surge protectors, fax machine, etc...)
Add an initialization string.
If this does not solve the problem, you have ruled out software. the problem lies
either with the Network, the modem, or the phone lines.
Back to Top
