Delete the temporary Internet files
To delete the temporary Internet files, follow these steps: (1). Start Internet Explorer. >> (2). On the Tools menu, click Internet Options, and then click the General tab. >> (3). Under Temporary Internet files, click Delete Cookies. >> (4). Click OK when you are prompted to confirm the deletion. >> (5). Click Delete Files. >> (6). Click OK when you are prompted to confirm the deletion. >> (7). Under History, click Clear History. >> (8). Click Yes when you are prompted to delete your history of visited Web sites. (9). Click OK.
Configure security, content, and advanced settings in Internet Explorer
Step: 1.To configure security, content, and advanced settings in Internet Explorer, follow these (a). In Internet Explorer, on the Tools menu, click Internet Options, and then click the Security tab. >> (b). Click Trusted sites, and then click Default Level. >> (c). Add the SSL Secured (128-Bit) Web site to the Trusted sites zone. To do this, click Sites, type the URL of the site in the Add this Web site to the zone box, click Add, click OK, and then click Apply.
2. Clear the Secure Sockets Layer (SSL) state and AutoComplete history. To do this, follow these steps:- (a). Click the Content tab. >> (b). Under Certificates, click Clear SSL State. >> (c). Click OK when you receive the message that the SSL cache was successfully cleared. >> (d). Under Personal information, click AutoComplete. >> (e). Under Clear AutoComplete history, click Clear Forms, and then click OK when you are prompted to confirm the operation. >> (f). Click Clear Passwords, click OK when you are prompted to clear all previously saved passwords, and then click OK two times.
3. Verify that Internet Explorer is configured to use SSL 2.0 and SSL 3.0. To do this, follow these steps:-(a). Click the Advanced tab. >> (b). Under Security in the Settings box, select the Use SSL 2.0 and Use SSL 3.0 check boxes (if they are not already selected), and then click OK.
Verify that the date and time settings on your computer are correct
To verify that your computer is configured with the correct date and time settings, follow these steps: -(1). Click Start, and then click Control Panel. >> (2). Click Date, Time, Language, and Regional Options, and then click Date and Time. >> (3). Click the Date & Time tab. >> (4). Make sure that the date and time settings are configured to use the current date and time, and then click OK.
Verify that your computer is using 128-bit encryption
To verify that your computer is using 128-bit encryption, follow these steps: -(1). Start Internet Explorer. >> (2). On the Help menu, click About Internet Explorer. >> (3). The level of encryption on your computer appears next to the words Cipher Strength. Verify that the Cipher Strength value appears as 128-bit. >> (4). Click OK.
Use System Restore to return your computer to a previous state
How to restore the operating system to a previous state in Windows XP:- http://support.microsoft.com/kb/306084/
Use the System File Checker (Sfc.exe) tool to scan all Windows File Protection (WFP)-protected files
To run System File Checker with the /scannow parameter, follow these steps: - (1). Click Start, and then click Run. >> (2). In the Open box, type cmd, and then click OK. >> (3). At the command prompt, type sfc /scannow, and then press ENTER.
Verify that the Microsoft Cryptographic Services service is started
To verify that the Cryptographic Services service is started, or to start it if it is not already started, follow these steps: -(1). Click Start, and then click Run. >> (2). In the Open box, type cmd, and then click OK. >> (3). At the command prompt, type net start cryptsvc, and then press ENTER. >> (4). Type exit to quit Command Prompt.
Re-register .dll files
To re-register these files, follow these steps: (1). Click Start, and then click Run. >> (2). In the Open box, type cmd, and then click OK. 3. At the command prompt, type the following lines and press ENTER after each line:
regsvr32 softpub.dll
regsvr32 wintrust.dll
regsvr32 initpki.dll
regsvr32 dssenh.dll
regsvr32 rsaenh.dll
regsvr32 gpkcsp.dll
regsvr32 sccbase.dll
regsvr32 slbcsp.dll
regsvr32 cryptdlg.dll
4. Click OK when you receive the message that DllRegisterServer in FileName succeeded.
5. Type exit.
Create a new user profile
1. Log on to the computer as Administrator or as a member of the Administrators group. 2. Click Start, and then click Control Panel.
PLEASE REFER TO MSKB:- http://support.microsoft.com/?kbid=813444
Sunday, May 25, 2008
Thursday, May 22, 2008
How to cancel printing or to delete a print job that is stuck in the print queue in Windows XP
Step 1: Start Notepad
To stop the print spooler and its files, we will have you create and run a script file that will automatically stop the service. This sounds difficult, but it really isn't. Just follow these steps carefully.
a. Click Start, and then click Run.
b. In the Open box, type notepad, and then click OK. Notice that a blank Notepad document opens.
Step 2: Copy a command script to Notepad
Now we will have you copy and paste some commands to the Notepad document.
a. Carefully select (highlight) all the following text:
net stop spooler
del %systemroot%\system32\spool\printers\*.shd
del %systemroot%\system32\spool\printers\*.spl
net start spooler
b. Right-click the text that you selected, and then click Copy.
c. In Notepad, right-click in the blank document, and then click Paste.
d. Carefully select (highlight) all the following text:
C:\DeletePrintJobs.cmd
e. Right-click the text that you selected, and then click Copy.
f. In Notepad, click Save As on the File menu.
g. In the File Name box, right-click, and then click Paste.
Note Notice that this file name differs from most other file names that you might have seen. That is because this file is a command script file.
h. Click Save.
Step 3: Run the command script file
Now that you have created the command script file, you will run it. To run it, you will copy and paste the name of the command script file in the Run box.
a. Carefully select (highlight) all the following text:
C:\DeletePrintJobs.cmd
b. Right-click the text that you selected, and then click Copy.
c. Click Start, and then click Run.
d. In the Open box, right-click, and then click Paste.
e. Click OK.
f. Notice that the Command Prompt window opens to run the command script file that you created. Notice also that this window closes automatically when the command script file has finished running. If you do not see the Command Prompt window open, check that you saved the command script file by using the correct name and that you entered the correct command script file name in the Run box. Note If this method does not work the first time, or if you cannot print anything after you use this method, restart your computer, and then try again.
If this method worked, you are finished with this article. However, you may want to read the "Prevention tips" section to prevent this problem from happening again.
PLEASE REFER TO MSKB:- http://support.microsoft.com/kb/946737
To stop the print spooler and its files, we will have you create and run a script file that will automatically stop the service. This sounds difficult, but it really isn't. Just follow these steps carefully.
a. Click Start, and then click Run.
b. In the Open box, type notepad, and then click OK. Notice that a blank Notepad document opens.
Step 2: Copy a command script to Notepad
Now we will have you copy and paste some commands to the Notepad document.
a. Carefully select (highlight) all the following text:
net stop spooler
del %systemroot%\system32\spool\printers\*.shd
del %systemroot%\system32\spool\printers\*.spl
net start spooler
b. Right-click the text that you selected, and then click Copy.
c. In Notepad, right-click in the blank document, and then click Paste.
d. Carefully select (highlight) all the following text:
C:\DeletePrintJobs.cmd
e. Right-click the text that you selected, and then click Copy.
f. In Notepad, click Save As on the File menu.
g. In the File Name box, right-click, and then click Paste.
Note Notice that this file name differs from most other file names that you might have seen. That is because this file is a command script file.
h. Click Save.
Step 3: Run the command script file
Now that you have created the command script file, you will run it. To run it, you will copy and paste the name of the command script file in the Run box.
a. Carefully select (highlight) all the following text:
C:\DeletePrintJobs.cmd
b. Right-click the text that you selected, and then click Copy.
c. Click Start, and then click Run.
d. In the Open box, right-click, and then click Paste.
e. Click OK.
f. Notice that the Command Prompt window opens to run the command script file that you created. Notice also that this window closes automatically when the command script file has finished running. If you do not see the Command Prompt window open, check that you saved the command script file by using the correct name and that you entered the correct command script file name in the Run box. Note If this method does not work the first time, or if you cannot print anything after you use this method, restart your computer, and then try again.
If this method worked, you are finished with this article. However, you may want to read the "Prevention tips" section to prevent this problem from happening again.
PLEASE REFER TO MSKB:- http://support.microsoft.com/kb/946737
Wednesday, May 14, 2008
Improve Core System Performance
On systems with large amount of RAM this tweak can be enabled to force the core Windows system to be kept in memory and not paged to disk.
NOTE:- Plzzzzzzzzz try the steps mentioned below only if you system has min 512mb of ram or above
HKEY_LOCAL_MACHINE >> SYSTEM >> CurrentControlSet >> Control >> Session Manager >> Memory Management. No the Right side look for DisablePagingExecutive
Value Name: DisablePagingExecutive
Value Data: (0 = default, 1 = disable system paging)
Change the value to '1' enable the tweak and stop the core process from being paged, or set it to '0' for the default.
Restart Windows for the change to take effect.
NOTE:- Plzzzzzzzzz try the steps mentioned below only if you system has min 512mb of ram or above
HKEY_LOCAL_MACHINE >> SYSTEM >> CurrentControlSet >> Control >> Session Manager >> Memory Management. No the Right side look for DisablePagingExecutive
Value Name: DisablePagingExecutive
Value Data: (0 = default, 1 = disable system paging)
Change the value to '1' enable the tweak and stop the core process from being paged, or set it to '0' for the default.
Restart Windows for the change to take effect.
Friday, May 9, 2008
Missing wininet.dll
Missing wininet.dll is becoming an issue due to spyaxe infection. Here is how to restore it without the XP cd.
Warning: The system may lock up a few times or give error several times during this procedure. Just keep trying, it will work.
1. At the blank desktop, press CTRL+ALT+DEL.
Task manager should open
2. On the Applications tab, click the New Task button.
The Create New Task window should open.
3. Click the Browse button.
4. Browse to the i386 directory. IMPORTANT: In the File type window at
the bottom of the page, change this to All Files. Customer will have to scroll far right to find it.
5. Find the wininet.dll. Right click and choose copy.
6. Browse to the window\system32 directory. . IMPORTANT: In the File type window at the bottom of the page, change this to All Files.
7. Press CRTL+V to paste. (right-click paste is NOT an option)
8.Make sure wininet.dll appears, then click Cancel in the bottom right.
9. Close the Create New Task window.
10.Click the New Task button again. In the Create New Task window, type explorer.exe and click OK.
This should bring the desktop back.
Warning: The system may lock up a few times or give error several times during this procedure. Just keep trying, it will work.
1. At the blank desktop, press CTRL+ALT+DEL.
Task manager should open
2. On the Applications tab, click the New Task button.
The Create New Task window should open.
3. Click the Browse button.
4. Browse to the i386 directory. IMPORTANT: In the File type window at
the bottom of the page, change this to All Files. Customer will have to scroll far right to find it.
5. Find the wininet.dll. Right click and choose copy.
6. Browse to the window\system32 directory. . IMPORTANT: In the File type window at the bottom of the page, change this to All Files.
7. Press CRTL+V to paste. (right-click paste is NOT an option)
8.Make sure wininet.dll appears, then click Cancel in the bottom right.
9. Close the Create New Task window.
10.Click the New Task button again. In the Create New Task window, type explorer.exe and click OK.
This should bring the desktop back.
Installing HyperTerminal
Installing HyperTerminal: - if you see the error message ‘Cannot find HYPERTERMINAL’ you will need to install HyperTerminal [win98 / me].
1. Click start > settings > control panel > Add / Remove programs.
2. In Add / Remove programs select properities and then click the windows setup tab.
3. Double click communications.
4. Check the box for HyperTerminal.
5. Click ok and then ok again to install [you may be asked for the windows installation cd for this procedure].
1. Click start > settings > control panel > Add / Remove programs.
2. In Add / Remove programs select properities and then click the windows setup tab.
3. Double click communications.
4. Check the box for HyperTerminal.
5. Click ok and then ok again to install [you may be asked for the windows installation cd for this procedure].
Hyperterminal test for verifying hardware function
Hyperterminal test for verifying hardware functionality of dial up modem
1. Close all application that may be trying to use the modem, such as connection software, fax software or bookkeeping sortware.
2. Click START > RUN > hypertrm & click ok
3. The new connection –hyperterminal windows appears. Press ESC or cancel key to close the new connection windows
4. Type ATE1 & press enter. The application responds OK [you may not see these letter as you type them. This normal. The ATE1 command turns on the visible text so you can see whatever you type.]
5. Type AT&F pres enter. The application responds OK.[this loads the modem default settings]
6. Type ATZ & press enter. The application responds OK. [This resets modems to the default settings.]
7. Type ATDT. Immediately follow ATDT with the access number your ISP gave you. Press enter the application dials your ISP access number.[the modem should dial out & connect to your ISP {you hear the screeching tones as it connects}. Typically hyperterminal will then respond with a message stating connected.
8. To disconnect the modem, close hyperterminal. If you are prompted to save the session, click no. [If the modem successfully connects, then the modem itself is working properly & you need to contact your ISP for configuration assistance.
1. Close all application that may be trying to use the modem, such as connection software, fax software or bookkeeping sortware.
2. Click START > RUN > hypertrm & click ok
3. The new connection –hyperterminal windows appears. Press ESC or cancel key to close the new connection windows
4. Type ATE1 & press enter. The application responds OK [you may not see these letter as you type them. This normal. The ATE1 command turns on the visible text so you can see whatever you type.]
5. Type AT&F pres enter. The application responds OK.[this loads the modem default settings]
6. Type ATZ & press enter. The application responds OK. [This resets modems to the default settings.]
7. Type ATDT. Immediately follow ATDT with the access number your ISP gave you. Press enter the application dials your ISP access number.[the modem should dial out & connect to your ISP {you hear the screeching tones as it connects}. Typically hyperterminal will then respond with a message stating connected.
8. To disconnect the modem, close hyperterminal. If you are prompted to save the session, click no. [If the modem successfully connects, then the modem itself is working properly & you need to contact your ISP for configuration assistance.
Backup & Restore Windows Mail Messages
Backup Windows Mail Messages
1. Click on Start , type Windows Mail, and then press the key.
Windows Mail launches.
2. Click on File, select Export, and click on Messages…
The Windows Mail Export window appears.
3. Select Microsoft Windows Mail and click on the Next button.
4. Click on the Browse button.
The Select the location to which you want to export the e-mail messages window appears.
5. Select the location of the folder that you wish to export messages to and click the Select Folder button.
6. Click the Next button
The Select Folders screen appears.
7. Select the message folder that you would like to export and click the Next button.
Windows Mail now exports the messages, this may take several minutes depending on how many messages are present.
8. Click the Finish button.
The mail messages have now been exported.
Restore Window Mail Messages
1. Click on Start , type Windows Mail, and then press the key.
Windows Mail launches.
2. Click on File, select Import, and click on Messages…
The Windows Mail Import window appears.
3. Select Microsoft Windows Mail 7 and click on the Next button.
4. Click on the Browse button.
The Select the location of the e-mail messages that you want to import window appears.
5. Select the folder containing the exported message and click the Select Folder button
6. Click the Next button
The Select Folders screen appears.
7. Select the message folders you would like to import and click the Next button.
Windows Mail now imports the messages, this may take several minutes depending on how many messages are being imported.
8. Click the Finish button.
The mail messages have now been imported.
1. Click on Start , type Windows Mail, and then press the
Windows Mail launches.
2. Click on File, select Export, and click on Messages…
The Windows Mail Export window appears.
3. Select Microsoft Windows Mail and click on the Next button.
4. Click on the Browse button.
The Select the location to which you want to export the e-mail messages window appears.
5. Select the location of the folder that you wish to export messages to and click the Select Folder button.
6. Click the Next button
The Select Folders screen appears.
7. Select the message folder that you would like to export and click the Next button.
Windows Mail now exports the messages, this may take several minutes depending on how many messages are present.
8. Click the Finish button.
The mail messages have now been exported.
Restore Window Mail Messages
1. Click on Start , type Windows Mail, and then press the
Windows Mail launches.
2. Click on File, select Import, and click on Messages…
The Windows Mail Import window appears.
3. Select Microsoft Windows Mail 7 and click on the Next button.
4. Click on the Browse button.
The Select the location of the e-mail messages that you want to import window appears.
5. Select the folder containing the exported message and click the Select Folder button
6. Click the Next button
The Select Folders screen appears.
7. Select the message folders you would like to import and click the Next button.
Windows Mail now imports the messages, this may take several minutes depending on how many messages are being imported.
8. Click the Finish button.
The mail messages have now been imported.
Backup & Restore Windows Mail Account
Backup a Windows Mail Account
1. Click on Start , type Windows Mail, and then press the key.
Windows Mail launches.
2. Click on Tools and select Accounts…
The Internet Accounts window appears.
3. Select the account you wish to export and click on the Export… button.
The Export Internet Account window appears
4. Select the location of the file that you wish to export and click Save
5. Click on the Close button to close the Internet Accounts window.
The account settings have now been exported.
Restore a Windows Mail Account
1. Click on Start , type Windows Mail, and then press the key.
Windows Mail launches.
2. Click on Tools and select Accounts…
The Internet Accounts window appears.
3. Click on the Import… button
The Import Internet Account window appears
4. Select the location of the file that you wish to import and click Open
5. Click on the Close button to close the Internet Accounts window
The account settings have now been imported.
1. Click on Start , type Windows Mail, and then press the
Windows Mail launches.
2. Click on Tools and select Accounts…
The Internet Accounts window appears.
3. Select the account you wish to export and click on the Export… button.
The Export Internet Account window appears
4. Select the location of the file that you wish to export and click Save
5. Click on the Close button to close the Internet Accounts window.
The account settings have now been exported.
Restore a Windows Mail Account
1. Click on Start , type Windows Mail, and then press the
Windows Mail launches.
2. Click on Tools and select Accounts…
The Internet Accounts window appears.
3. Click on the Import… button
The Import Internet Account window appears
4. Select the location of the file that you wish to import and click Open
5. Click on the Close button to close the Internet Accounts window
The account settings have now been imported.
Message Could Not Be Displayed Error in Windows Mail IN VISTA
Problem: Cannot open, move, or delete certain messages in Windows Mail [ When trying to open a message in Windows Mail, the error message Message could not be displayed is shown. If you try to delete or move the message, a dialog box appears stating An unknown error has occurred. ]
Solution: Delete the Windows Mail store folder
1. Restart the computer in safe mode.
2. Click on Start , type appdata, and then press then Enter.
The C:\Users\\appdata folder appears where is the account name assigned to the user currently logged into the system.
3. Double-click to open the Local, and then the Microsoft folder.
4. Delete the Windows Mail folder.
5. Clear the Recycle Bin.
Restart the computer in normal mode and reconfigure the windows Mail and that should do the Trick
Solution: Delete the Windows Mail store folder
1. Restart the computer in safe mode.
2. Click on Start , type appdata, and then press then Enter.
The C:\Users\
3. Double-click to open the Local, and then the Microsoft folder.
4. Delete the Windows Mail folder.
5. Clear the Recycle Bin.
Restart the computer in normal mode and reconfigure the windows Mail and that should do the Trick
"MAPI32.DLL is corrupt" in Outlook 2003 in Vista
I am not sure how many of you have come across the issue when u click on Outlook 2003 in Windows Vista you get the following error Message
"Cannot start Microsoft Office Outlook. MAPI32.DLL is corrupt or the wrong version."
no matter what u do like uninstall and reinstall it back again u still get the same error message.To resolve this issue follow the simple step mentioned below it has worked for me i hope it works for everyone
You will have to locate the Following File [ MSMAPI32.DLL ] and how do you do that very simple
Click on Computer >> Then local disk C: >> Program Files >> Common Files >> System >> MSMAPI >> 1033 { Hear you will find the [ MSMAPI32.DLL ] }
Rename the file to something like MSMAPI32.XXX or MSMAPI32.OLD
Now restart Outlook. Hopefully you get the same result I got
"Cannot start Microsoft Office Outlook. MAPI32.DLL is corrupt or the wrong version."
no matter what u do like uninstall and reinstall it back again u still get the same error message.To resolve this issue follow the simple step mentioned below it has worked for me i hope it works for everyone
You will have to locate the Following File [ MSMAPI32.DLL ] and how do you do that very simple
Click on Computer >> Then local disk C: >> Program Files >> Common Files >> System >> MSMAPI >> 1033 { Hear you will find the [ MSMAPI32.DLL ] }
Rename the file to something like MSMAPI32.XXX or MSMAPI32.OLD
Now restart Outlook. Hopefully you get the same result I got
Some of the Windows Xp shortcut keys
Add/Remove Programs --------------------------- appwiz.cpl
Automatic Updates Configuration ------------- wuaucpl.cpl
Display Properties ------------------------------- desk.cpl
Firewall Settings --------------------------------- firewall.cpl
Internet Options --------------------------------- inetcpl.cpl
Network Connections ---------------------------- ncpa.cpl
Power Options ------------------------------------ powercfg.cpl
Security Center ----------------------------------- wscui.cpl
Sound and Audio ----------------------------------- mmsys.cpl
System Properties ---------------------------------- sysdm.cpl
User Accounts -------------------------------------- nusrmgr.cpl
Component Services --------------------- comexp.msc
Computer Management ----------------- compmgmt.msc
Device Manager --------------------------- devmgmt.msc
Disk Defragmentation ------------------- dfrg.msc
Disk Managment ------------------------ diskmgmt.msc
Event Viewer ---------------------------- eventvwr.msc
Group Policies -------------------------- gpedit.msc
Local Security Settings ---------------- secpol.msc
Local Users and Groups ---------------- lusrmgr.msc
Performance Monitor ---------------- perfmon.msc
Services ------------------------------- services.msc
Shared Folders ----------------------- fsmgmt.msc
Command Prompt ---------------- cmd / command (98-ME)
Hyperterminal ---------------- hypertrm
MS Excel ----------------- excel
MS PowerPoint ------------------- powerpnt
MS Word ---------------------- winword
Notepad ----------------------- notepad
Sound Recorder ------------------- sndrec32
Volume Controls -------------------- sndvol32
Windows Tour -------------------- tourstart
Device Manager --------------------- Windows Key + Break
Minimise All Windows ------------- Windows Key + D
Right Click -------------------------- Key beside Left Ctrl Key
Run Box ------------------------- Windows Key + R
Search Window -------------------- Windows Key + F
START Menu ---------------------- Ctrl + Esc / Windows Key
Windows Explorer ------------------ Windows Key + E
Automatic Updates Configuration ------------- wuaucpl.cpl
Display Properties ------------------------------- desk.cpl
Firewall Settings --------------------------------- firewall.cpl
Internet Options --------------------------------- inetcpl.cpl
Network Connections ---------------------------- ncpa.cpl
Power Options ------------------------------------ powercfg.cpl
Security Center ----------------------------------- wscui.cpl
Sound and Audio ----------------------------------- mmsys.cpl
System Properties ---------------------------------- sysdm.cpl
User Accounts -------------------------------------- nusrmgr.cpl
Other Windows programs
Component Services --------------------- comexp.msc
Computer Management ----------------- compmgmt.msc
Device Manager --------------------------- devmgmt.msc
Disk Defragmentation ------------------- dfrg.msc
Disk Managment ------------------------ diskmgmt.msc
Event Viewer ---------------------------- eventvwr.msc
Group Policies -------------------------- gpedit.msc
Local Security Settings ---------------- secpol.msc
Local Users and Groups ---------------- lusrmgr.msc
Performance Monitor ---------------- perfmon.msc
Services ------------------------------- services.msc
Shared Folders ----------------------- fsmgmt.msc
Applications
Command Prompt ---------------- cmd / command (98-ME)
Hyperterminal ---------------- hypertrm
MS Excel ----------------- excel
MS PowerPoint ------------------- powerpnt
MS Word ---------------------- winword
Notepad ----------------------- notepad
Sound Recorder ------------------- sndrec32
Volume Controls -------------------- sndvol32
Windows Tour -------------------- tourstart
KeyBoard Shortcuts
Device Manager --------------------- Windows Key + Break
Minimise All Windows ------------- Windows Key + D
Right Click -------------------------- Key beside Left Ctrl Key
Run Box ------------------------- Windows Key + R
Search Window -------------------- Windows Key + F
START Menu ---------------------- Ctrl + Esc / Windows Key
Windows Explorer ------------------ Windows Key + E
Commonly used Symantec tools
Hi All;
Check out the link mentioned below for Commonly used Symantec tools
OR
www.symantec.com/autotools
Check out the link mentioned below for Commonly used Symantec tools
http://service1.symantec.com/SUPPORT/tsgeninfo.nsf/docid/2005103109480139
OR
www.symantec.com/autotools
DUNS ERROR 781, 792, 797, 798, 799, 800
DUNS ERROR 781
781 - The encryption attempt failed because no valid certificate was found.
This error may occur with Windows 2000 or XP client attempting to connect to a virtual private network (VPN) using Layer 2 Tunneling Protocol (L2TP) and IP Security Protocol (IPSec).
If you are not attempting to connect with VPN, L2TP or IPSec, check your Connectoid's Security tab - and set it according to your ISP's instructions (most ISPs use 'Typical - allow unsecured password).
If you are attempting to connect with VPN, L2TP or IPSec:
· There may be a problem with the remote computer:
The certificate on the VPN server is not valid or missing - the administrator of the remote computer must correct the problem.
The IPSec Policy Agent service on the remote computer may be stopped, or stopped and re-started without stopping and re-starting the Routing and Remote Access service on the server. The administrator of the remote computer must correct the problem.
For more information - see MS KB 247231
782 - Network Address Translation (NAT) is currently installed as a routing protocol, and must be removed before enabling Internet Connection Sharing.
783 Internet Connection Sharing cannot be enabled. The LAN connection selected as the private network is either not present, or is disconnected from the network. Please ensure that the LAN adapter is connected before enabling Internet Connection Sharing.
784 You cannot dial using this connection at logon time, because it is configured to use a user name different than the one on the smart card. If you want to use it at logon time, you must configure it to use the user name on the smart card.
785 You cannot dial using this connection at logon time, because it is not configured to use a smart card. If you want to use it at logon time, you must edit the properties of this connection so that it uses a smart card.
786 The L2TP connection attempt failed because there is no valid machine certificate on your computer for security authentication.
787 The L2TP connection attempt failed because the security layer could not authenticate the remote computer.
788 The L2TP connection attempt failed because the security layer could not negotiate compatible parameters with the remote computer.
789 The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer.
790 The L2TP connection attempt failed because certificate validation on the remote computer failed.
791 The L2TP connection attempt failed because security policy for the connection was not found.
DUNS ERROR 792
792 - The L2TP Connection Attempt failed because security negotiation timed out.
Windows 2000 & XP: This error can occur if you have a preshared key configured on the client, but the key is not configured on the RRAS (Routing and Remote Access Service) server. This error can occur even if valid certificates are configured on both the client and server. This can be resolved by removing the preshared key from the client so that a security negotiation process using certificates can occur.
See MS KB Q299307
794 - The Framed Protocol RADIUS attribute for this user is not PPP.
795 The Tunnel Type RADIUS attribute for this user is not correct.
796 - The Service Type RADIUS attribute for this user is neither Framed nor Callback
Framed.
DUNS ERROR 797
797 - The modem could not be found.
This error occurs only in Windows 2000 and XP. The error can occur if the modem is no longer visible to the system, and may be a problem related to the modem driver, or system conflicts that cause the modem to work only some of the time.
In some cases, rebooting the machine may "solve" the problem.
If the modem is an external and is not powered on when the system is booted this error may occur: shut-down, power on the modem & re-boot the system.
If the error persists, check to see if there is an updated driver for your modem.
DUNS ERROR 798
798 - A certificate could not be found that can be used with this Extensible Authentication Protocol.
This error may occur if your dial-up networking security settings require a certificate that cannot be located.
Most ISPs do not require EAP (extensible authentication protocol) for access: check your Connectoid's Security Tab settings - normally, 'Typical' is selected, and EAP is not used.
For this error to occur, the security tab settings are set to 'Advanced (Custom Settings), which enables the 'Settings...' button, which produces a windows with 'Logon Security' settings which include EAP. Change the security settings if the server you are connecting to does not require EAP.
If the server does require EAP, contact the system administrator or see the 'Certificates' help section of Windows' Help for Network Connections.
DUNS ERROR 799
799 - Internet Connection Sharing (ICS) cannot be enabled due to an IP address conflict on the network. ICS requires the host be configured to use 192.168.0.1. Please ensure that no other client on the network is configured to use 192.168.0.1.
If you are not using ICS (Internet Connection Sharing), edit the Advanced tab of your connectoid and un-check the 'Allow other computers to connect through this computer's Internet connection' checkbox.
If you are using ICS, the IP address of your machine's LAN connection, and/or other machines on the network are incorrect. As the error message indicates, your machine must be assigned IP 192.168.0.1, and no other machine or device on the LAN can use that address. Your machine's IP address is controlled by Properties associated with your Local Area Connection in the 'LAN or high-speed Internet' section of Windows' Network Connections. (Start->Connect To -> Show All Connections)
This error applies to Windows 2000 & XP.
DUNS ERROR 800
800 - Unable to establish the VPN connection. The VPN server may be un-reachable, or security parameters may not be configured properly for this connection.
This error may occur if a Virtual Private Network connection is specified, but fails to authenticate. See this Microsoft how-to article on using Virtual Private Networks for Secure Internet Data Transfer.
Some of the reasons this error occurs include:
· The PPTP or L2TP server is not reachable. A firewall could be blocking traffic; the server name specified in your connection could be incorrect.
· Your connection configuration might prevent IPSec from establishing a secure channel with the server. A network component such as Network Address Translation (NAT) or a firewall might be blocking IPSec traffic.
· Verify whether you have a current machine certificate or that the pre-shared key is correct. Check the security settings in the properties for your network connection.
· There are no free VPN ports on the server (over-subscribed - maximum number of users already connected).
This error applies to Windows 2000 & XP.
801 This connection is configured to validate the identity of the access server, but Windows cannot verify the digital certificate sent by the server.
900 The router is not running.
901 The interface is already connected.
902 The specified protocol identifier is not known to the router.
903 The Demand-dial Interface Manager is not running.
904 An interface with this name is already registered with the router.
905 An interface with this name is not registered with the router.
906 The interface is not connected.
907 The specified protocol is stopping.
908 The interface is connected and hence cannot be deleted.
909 The interface credentials have not been set.
910 This interface is already in the process of connecting.
911 An update of routing information on this interface is already in progress.
912 The interface configuration in invalid. There is already another interface that is connected to the same interface on the remote router.
913 A Remote Access Client attempted to connect over a port that was reserved for Routers only.
914 A Demand Dial Router attempted to connect over a port that was reserved for Remote Access Clients only.
915 The client interface with this name already exists and is currently connected.
916 The interface is in a disabled state.
917 The authentication protocol was rejected by the remote peer.
918 There are no authentication protocols available for use.
919 The remote computer refused to be authenticated using the configured authentication protocol. The line has been disconnected.
920 The remote account does not have Remote Access permission.
921 The remote account has expired.
922 The remote account is disabled.
923 The remote account is not permitted to logon at this time of day.
924 Access was denied to the remote peer because username and/or password is invalid on the domain.
925 There are no routing enabled ports available for use by this demand dial interface.
926 The port has been disconnected due to inactivity.
927 The interface is not reachable at this time.
928 The Demand Dial service is in a paused state.
929 The interface has been disconnected by the administrator.
930 The authentication server did not respond to authentication requests in a timely fashion.
931 The maximum number of ports allowed for use in the multilinked connection has been reached.
932 The connection time limit for the user has been reached.
933 The maximum limit on the number of LAN interfaces supported has been reached.
934 The maximum limit on the number of Demand Dial interfaces supported has been reached.
935 The maximum limit on the number of Remote Access clients supported has been reached.
936 The port has been disconnected due to the BAP policy.
937 Because another connection of your type is in use, the incoming connection cannot accept your connection request.
938 No RADIUS servers were located on the network.
939 An invalid response was received from the RADIUS authentication server. Make sure that the case sensitive secret password for the RADIUS server is set correctly.
940 You do not have permission to connect at this time.
941 You do not have permission to connect using the current device type.
942 You do not have permission to connect using the selected authentication protocol.
943 BAP is required for this user.
944 The interface is not allowed to connect at this time.
945 The saved router configuration is incompatible with the current router.
946 RemoteAccess has detected older format user accounts that will not be migrated automatically. To migrate these manually, run XXXX.
948 The transport is already installed with the router.
949 Received invalid signature length in packet from RADIUS server.
950 Received invalid signature in packet from RADIUS server.
951 Did not receive signature along with EAPMessage from RADIUS server.
952 Received packet with invalid length or Id from RADIUS server.
953 Received packet with attribute with invalid length from RADIUS server.
954 Received invalid packet from RADIUS server.
955 Authenticator does not match in packet from RADIUS server.
DUNS ERROR 756, 764, 769, 775, 777, 780
DUNS ERROR 756
756 - This connection is already being dialed.
This error indicates more than one simultaneous request to make a dial-up networking connection has been made.
This can occur if you have one or more programs set up to automatically make a connection to the Internet. Check the settings for your e-mail, browser and other applications that access the Internet, disabling automatic connection as appropriate.
757 - Remote access services could not be started automatically. Additional information is provided in the event log.
758 - Internet connection sharing is already enabled on the connection.
760 - An error occurred while routing capabilities were being enabled.
761 - An error occurred while Internet connection sharing was being enabled for the connection.
763 - Internet connection sharing cannot be enabled. There are two or more LAN connections in addition to the connection to be shared.
DUNS ERROR 764
764 - No smart card reader is installed.
This error can occur if the Security settings of your Connectoid are incorrect: in the security tab, make sure that the option to use a Smart Card is NOT enabled. With most connections, the security setting should be "typical" and allow an unsecured password.
765 - Internet connection sharing cannot be enabled. A LAN connection is already configured with the IP address required for automatic IP addressing.
766 - The system could not find any certificate.
767 - Internet connection sharing cannot be enabled. The LAN connection selected on the private network has more than one IP address configured. Reconfigure the LAN connection with a single IP address before enabling Internet connection sharing.
768 - The connection attempt failed because of failure to encrypt data.
DUNS ERROR 769
769 - The specified destination is not reachable.
This error should only occur if you are trying to connect to the Internet or remote server via a PPPoE (Point-to-point protocol over Ethernet) link. A PPPoE connection is often used with DSL service, but is almost never used for a dial-up connection to the Internet.
Check your network connections (connectoids) - if you show all connections (Start-> Connect to -> Show all connections) make sure that your dial-up connectoids are listed in the 'dial-up' section. If you are trying to establish a VPN (virtual private network) dial-up connection, it's necessary to specify a normal dial-up connectoid in the 'First dial' section of the VPN connectoid.
This error may also occur if you are attempting to establish a PPPoE connection via a network card that is not enabled (or properly installed). See MS KB Q316395.
770 - The remote machine rejected the connection attempt.
771 - The connection attempt failed because the network is busy.
772 - The remote computer's network hardware is incompatible with the type of call requested.
773 - The connection attempt failed because the destination number has changed.
774 - The connection attempt failed because of a temporary failure. Try connecting again.
DUNS ERROR 775
775 - The call was blocked by the remote computer.
This error cannot occur with Windows 95/98 or NT - only with Windows Me, 2K or XP.
Make sure you are dialing the correct phone number.
Make sure that your login information (user name / password) is correct. See: Connectoids.
Make sure you have an account that has not been restricted with the ISP you are calling.
Try dialing and do a test login using Hyperterminal.
776 - The call could not be connected because the destination has invoked the Do Not Disturb feature.
DUNS ERROR 777
777 - The connection attempt failed because the modem (or other connecting device) on the remote computer is out of order.
This error cannot occur with Windows 95/98 or NT - only with Windows Me or 2K.
This error can occur if you have installed your modem with an incorrect driver. Identify your modem chipset, PCI ID, manufacturer, and make sure you are using the correct driver.
If you get this error, the modem or DUNS may not be installed or set-up properly. See if you can talk to your modem with Hyperterminal setup as described here - if you can, inspect/re-install DUNs; if you cannot, the modem needs to be re-installed. In some cases, a simple cold-boot (shut down - power off - re-start) may solve the problem.
This error may also occur if the number you are dialing is blacklisted.
Many PCI modems include an entry in Windows' ADD/REMOVE PROGRAMS (from Control Panel or System): it is important to remove any installed modems using this remove function to properly update the registry. In some cases where the modem has been installed more than once with different driver versions without proper removal, the registry may be corrupted: if this is the case, only manual editing, restore from backup, or re-installation of Windows may cure the trouble.
Also note: In many cases, PCI modems will not operate in all of your PCI slots - see this page.
Also see: Forum56 Post regarding HP-supplied modem and error 777.
778 - It was not possible to verify the identity of the server.
779 - To dial out using this connection, you must use a smart card.
DUNS ERROR 780
780 - An attempted function is not valid for this connection.
Check your Connectoid - make sure it is set properly. It should be set to dial out using a modem on your machine and not via a network.
If you are attempting to access the Internet through a local area network, the network setup may be incorrect.
DUNS ERROR 737, 738, 740, 741, 742, 745
DUNS ERROR 737
737 - Loopback detected.
Error 737 is triggered by a loopback of data involved in setting up a PPP connection after the modem successfully CONNECTs to the remote modem.
This error may occur when making calls to ISPs that use an authentication protocol within PPP (point-to-point protocol).
ISPs using authentication after PPP - may include/require a dial-up script or other proprietary dialer. In some cases, a plain-text string is transmitted to the RAS, and then a PPP session is established. If the PPP session isn't established because the local system is receiving back the packets it is sending, error 737 may be reported.
The problem may be timing: a script that has DELAY # (where # is a number representing seconds) may need a value 1 or more seconds greater; or, if there is no delay, one may be needed.
Examine the PPP Log to see details of the PPP setup failure.
DUNS ERROR 738
738 - The server did not assign an address.
This error may occur in Windows 2000 or XP if the Negotiate multi-link for single link connection option is enabled for the dial-up connection. This is an option in the Connectoid for each dial-up connection, and is located in PPP settings:
Connectoid Properties -> Networking Tab -> Settings button (located below the 'type of dial-up server' drop-down selection - the type of dial-up server should be PPP: Windows 95/98/NT4/2000, Internet)
To correct this error, un-check the Negotiate multi-link for single link connection option.
Note: In Windows 2000, this option is checked by default until Service Pack 3. With service pack 2 or lower, it's possible to prevent this option from being on by default with a registry modification. For more information, see MS KB 256213.
DUNS ERROR 740
740 - The TAPI devices configured for Remote Access failed to initialize or were not installed correctly.
All versions of Windows -
Check your Connectoids and make sure they specify correct settings and modem to use.
Re-install RAS (remote access service) and Dial-up Networking.
Third-party products including WinPoET may bring up an error 740 - The Protocol is not Configured / Remove and re-install TCP/IP and the Communications package. You may need to remove and re-install the third-party communications package and/or Windows TCP/IP Networking component.
DUNS ERROR 741
741 - The local computer does not support encryption.
All versions of Windows -
Installing Microsoft RRAS may disable 128-bit encryption. See this MS KB Article.
Windows 95 - If PPTP is being used with older version of DUNS. Solution: Upgrade to DUNS 1.3. See MS KB Article 191192.
Also see:
MSKB Article Identifying 128-bit Windows 95 DUN Client
This Microsoft page will detect and recommend 128-bit encryption upgrade.
DUNS ERROR 742
742 - The remote server does not support encryption.
All versions of Windows -
Installing Microsoft RRAS may disable 128-bit encryption. See this MS KB Article.
Also see:
MSKB Article Identifying 128-bit Windows 95 DUN Client
This Microsoft page will detect and recommend 128-bit encryption upgrade.
743 - The remote server requires encryption.
744 - Cannot use the IPX net number assigned by the remote server. Check the event log.
DUNS ERROR 745
745 - An essential file is missing. Re-install Dial-Up Networking
Windows 95/98/Me
This error may occur if a dial-up networking .dll file is missing or damaged.
Microsoft has published an article describing how to resolve this problem. Removing and re-installing dial-up networking may not resolve this problem, and it may be necessary to also edit the registry as describe in MS KB #174579.
This error can also occur if the password list (.pwl) file is damaged. In addition to DUNS Error 745, other errors may occur including invalid page faults, a TCP/IP warning, and/or the computer locking up. See MS KB#154092.
751 - The callback number contains an invalid character. Only the following characters are allowed: 0 to 9, T, P, W, (,), -, @, and space.
752 - A syntax error was encountered while processing a script.
753 - The connection could not be disconnected because it was created by the multi-protocol router.
754 - The system could not find the multi-link bundle.
755 - The system cannot perform automated dial because this entry has a custom dialer. specified.
DUNS ERROR 711, 718, 720, 721, 733, 735, 736
DUNS ERROR 711
711 - RasMan initialization failure. Check the event log.
This error can occur with Windows NT 4.0 if the Plug and Play Service is disabled. This will also cause the inability to open Modems from Control Panel, and will prevent the detection of modem for Remote Access Service (RAS).
The error may also occur if a modem has been removed physically from a Windows NT 4.0 system, but not removed from RAS; or, if the modem has been replaced without adding the new modem to RAS. If this error occurs without removal or change to previously working modem, it may be possible that the modem has been damaged and can no longer operate.
To resolve this problem, make sure the Plug and Play service is running. Control Panel->Services. See this Microsoft KB Article.
If the modem has been removed from the machine and replaced with another, you need to add the new modem to RAS: My Computer->Dial Up Networking: Remove from the list of installed RAS modems any modem that is no longer present, and install (add) the new modem.
If the error persists, check that the modem driver has been properly installed. You can determine whether the modem works by using Hyperterminal connected directly to the modem's COM port (which does not require RAS). If the modem doesn't respond to AT commands in Hyperterminal, the modem driver may need to be removed and re-installed.
712 - Biplex port is initializing. Wait a few seconds and redial.
713 - No active ISDN lines are available.
714 - Not enough ISDN channels are available to make the call.
715 - Too many errors occurred because of poor phone line quality.
716 - The Remote Access IP configuration is unusable.
717 - No IP addresses are available in the static pool of Remote Access IP addresses.
DUNS ERROR 718
718 - PPP timeout.
This error indicates a PPP conversation was started, but was terminated because the remote server did not respond within an appropriate time. This can be caused by poor line quality or a problem with the server (ISP). This error can occur when your modem has connected to the ISP and has sent username and password, but there is no response from the server.
Sometimes, re-dialing will be successful.
This error can also occur if your ISP account has expired, or if the username or password you are using is invalid.
This error can occur if you have LCP extensions enabled in the TCP/IP Properties of the connectoid and your ISP does not support LCP extensions.
This error may also occur if you have one or more network cards in your machine, and the cards do not have TCP/IP protocol enabled, or if the TCP/IP settings are incorrect. (Go to Networking in Control Panel to examine the properties of your network adapters; or, if you are not using the network card(s), disable them in Control Panel->System->Hardware.)
With Windows NT and Motorola ISDN BitSurfr Pro EZ - see this MS KB article.
When calling a WindowsNT4.0/SP2 Server - see this MS KB article.
If using PPTP and Windows NT - see this MS KB article.
If running MS Routing & Remote Access Server Update for Windows NT 4.0 - see this MS KB article.
With Microsoft Exchange Server 5.5 - see this MS KB article.
When attempting to connect to MSN - see MS KB 319916.
DUNS ERROR 720
720 - No PPP control protocols configured.
All Operating Systems - This error can occur if you have not configured your Dial-up Networking settings to use a protocol supported by the ISP or system you are calling. Check the Server Types tab of your Dial-up connectoid. Most ISP's use TCP/IP protocol, and no others should be checked. There is a screenshot of a Windows 95 connectoid's Server Tab here. Also check the Dial-up Server selection. For most ISP's this will be PPP, although some may support SLIP or CSLIP.
If you have selected TCP/IP as the protocol, and it is not supported by the system you are calling, you may get this error. (For example, a Remote Access Server set up for NetBEUI.) Solution: Configure the Server Types of the DUNS connectoid to match the protocol installed on the remote server.
If you are connecting to a server that requires 128-bit encryption and your system doesn't have 128-bit encryption installed, you may get this error. This Microsoft page will detect and recommend 128-bit encryption upgrade. Also see: MS KB Article: Installing RRAS disables 128-bit encryption.
The installation of TCP/IP and/or dial-up networking may be damaged. Check ControlPanel->Network for TCP/IP assigned to (or bound to) the Dial-up Adapter. You can Remove, then Re-install the TCP/IP protocol (except with newer versions of Windows - see next paragraph). If you have a LAN card in your machine and access the Internet via a modem, unless you use TCP/IP on your LAN, TCP/IP should be assigned (bound) to only the Dial-up Adapter.
With Windows XP, you cannot re-install TCP/IP, but you can reset it with the following DOS command:
Click Start, then Run..., and put the following in the Open text box (or enter the following from a DOS command prompt which you can get by Start->Run-> cmd)
netsh int ip reset resetlog.txt
Windows NT: If you have configured RAS to only receive calls, you may receive this error. Go to the Remote Access Service tab on Services from ControlPanel->Network, and configure RAS for dial-out only, or dial-out and receive calls. See this MS KB Article.
Windows NT & 2000: This MS KB Article indicates the error (as well as error 611) may have several different causes, including the NETBIOS interface not being installed, or NETBIOS binding disabled.
DUNS ERROR 721
721 - Remote PPP peer is not responding.
This error may occur if there is a problem at the ISP. Disconnect, then dial back in. If error 721 persists:
· Try dialing into a different provider or access number if available
· Check the properties of, and/or create a new Connectoid
· Re-install dial-up networking (DUNS) - check Windows' networking properties.
· If you still have difficulty, enable and examine the PPP Log.
722 - The PPP packet is invalid.
723 - The phone number, including prefix and suffix, is too long.
724 - The IPX protocol cannot dial-out on the port because the computer is an IPX router.
725 The IPX protocol cannot dial-in on the port because the IPX router is not installed.
726 - The IPX protocol cannot be used for dial-out on more than one port at a time.
727 - Cannot access TCPCFG.DLL.
728 - Cannot find an IP adapter bound to Remote Access.
729 - SLIP cannot be used unless the IP protocol is installed.
730 - Computer registration is not complete.
731 - The protocol is not configured.
732 - The PPP negotiation is not converging.
DUNS ERROR 733
733 - The PPP control protocol for this network protocol is not available on the server.
All versions of Windows -
Installing Microsoft RRAS may disable 128-bit encryption. See this MS KB Article.
Windows NT & 2000 - TCP/IP protocol may not be correcting installed or bindings may be incorrect. See MS KB Article 168720.
Windows 2000 - This error may occur if the Negotiate multi-link option is enabled and you are dialing a normal one-call (single-link) connection. Solution: Start->Settings->Network & Dial-up Connections - right-click the connection, then Properties, Networking, Settings and clear the Negotiate multi-link for single link connections check box. See MSKB Article 244603.
Windows NT Server - See MSKB Article Q177648 and MSKB Article Q172956.
Also see:
MSKB Article Identifying 128-bit Windows 95 DUN Client
This Microsoft page will detect and recommend 128-bit encryption upgrade.
DUNS ERROR 735
735 - The requested address was rejected by the server.
All versions of Windows: Make sure your connectoid settings are correct - in particular make sure that network (TCP/IP) settings are to obtain an IP address automatically (do not specify an IP address); and, that WINS is disabled.
Windows 2000 & XP: This error may occur when a connection is (re-)established without successfully (re-)negotiating a network protocol. This is a known problem with Windows 2000 & XP - Microsoft has a fix. With Windows 2000, the problem was first corrected with Service Pack 4. A Windows XP fix should be included starting with Service Pack 2, or a separate interim patch is available from Microsoft. See: MS KB 812401
DUNS ERROR 736
736 - The remote computer terminated the control protocol.
This error may occur if the remote access server is unable to obtain an IP address (via DHCP) for the connection.
User report indicates this has occurred with Shiva Lanrover E Plus (now an Intel product), and the problem was solved by configuring the Shiva to act as DHCP server.
Subscribe to:
Posts (Atom)