Clear your local DNS cache

Sometimes when you repair your local area connection from the local area connection status window, you find out that your DNS cache could not be cleared and whatever you do, the cache will not clear up. So here’s the cool way of doing it..


Open your command prompt and type the following command:

C:\>net stop dnscache

If it says that the dnscache is not started then type the following command:

C:\>net start dnscache

It will start your local dns cache. Now try flushing your dns cache by issuing the following command:

C:\>ipconfig /flushdns

It will most probably clear your dns cache and display the results for you.

If you want to see what is in your local dns cache at this time, issue this command to find out:

C:\>ipconfig /displaydns



This can also be done as:



Go to run and type services.msc

select DNS Client, select automatic from drop down menu and start the service.

Your account does not have access to the vault containing this item' is generated when trying to open an archived item

Exact Error Message
Your account does not have access to the vault containing this item. Try using the same logon details you would use to log on to Microsoft Exchange Server. Alternatively you may ask your administrator to grant you access to the vault."

Details:

"Enterprise Vault is retrieving your item...Your password may be required..." when trying to open an archived email. (Figure 1)

Figure 1

 

Additionally,another window appears with the following information "Your account does not have access to the vault containing this item." (Figure 2)

Figure 2

 

This error can be generated by multiple issues and the following items should be checked:

• Verify using the same logon details used to log on to the Microsoft Exchange Server.  
• The account used needs to have access to the vault containing the item.
• May be an issue with the Enterprise Vault add-in. See Related Documents regarding the ResetEVClient utility to resolve this issue.
• Add the Enterprise Vault server names to the Exchange Mailbox Policy. On the Advanced tab, select Outlook and modify the Add server to Intranet Zone setting.

there was problem connecting to microsoft office outlook

Office Communicator 2007 and Outlook 2007 Integration Error

June 26th, 2008 | Category: Communicator 2007, Windows

After installing the Office Communicator 2007 client you may have two errors indicating that there is a problem with Communicator’s integration with Outlook.
The first error refers to a required hotfix that you can download directly from the link provided in the “Information” dropdown in the Communicator client. Simply select the link in the dropdown and install the patch.


The second possible error is a bit more cryptic.
“There was a problem connecting to Microsoft Office Outlook. The e-mail address used in your default Outlook profile is different from the sign-in address used in Communicator.  Change your default Outlook profile to match the sign-in address you are using in Communicator, and then sign out and sign back in to Communicator.”
This occurs because your Outlook profile was created with an address that is different from the default sip address used when activating the Communicator settings for your user profile in Active Directory.  For example: If your AD login is jsmith@fuzzy.net, Communicator will use that address as your default sip login.  However, if your default SMTP address is something different, such as john.smith@fuzzy.net, Outlook will default to that address when creating your mail profile.  To correct this issue, you need to delete your Outlook profile and recreated it using the jsmith@fuzzy.net SMTP address.
To accomplish this, open your Outlook client and go to “Tools/Account Settings..” and select “Microsoft Exchange Server” from the “E-mail” tab and press the “Remove” icon to delete the profile.  Once, deleted, you can now re-create the account by selecting the “New…” icon and then the “Microsoft Exchange, POP3, IMAP, or HTTP” service and filling out the “Add New E-mail Account” using the SMTP address that matches your sip address.
WARNING: Removing and adding an Outlook profile should not cause any loss of mail, however, anytime you alter configurations on a production system, make sure to get a complete backup first!
If the preceding fails to fix your integration issue, you may have a problem with your mapi32.dll. The mapi32.dll file controls the sending and receiving of messages between Outlook and other applications. If an application install replaced a newer version of mapi32.dll with an older version, Outlook integration could fail. To replace mapi32.dll with the most recent version available on your PC, run the command fixmapi.exe and reboot your PC. Note that if mapi32.dll is marked read-only, this command will fail.

C:\WINDOWS\Installer\fbf6b0f.msp was rejected by digital signature policy.

When you try to install a large Microsoft Windows Installer (.msi) package or a large Microsoft Windows Installer patch (.msp) package on a computer that is running Windows Server 2003 Service Pack 2, you receive the following error message:

Error 1718. File FileName was rejected by digital signature policy.

Additionally, the following event may be logged in the Application log:

Type: Error
Source: MsiInstaller
Category: None
Event ID: 1008
Date: Date
Time: Time
User: N/A
Computer: ComputerName

Description:
The installation of FileName is not permitted due to an error in software restriction policy processing. The object cannot be trusted.

Back to the top

CAUSE

This problem occurs if the Windows Installer process has insufficient contiguous...

This problem occurs if the Windows Installer process has insufficient contiguous virtual memory to verify that the .msi package or the .msp package is correctly signed.

Back to the top

RESOLUTION

Update download information The following files are available for download from...

Update download information

The following files are available for download from the Microsoft Download Center:

Collapse this imageExpand this image

Download the Update for Windows Server 2003 (973825) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=d79fb7bd-a16c-45f0-9b32-a309b3763951)

Collapse this imageExpand this image

Download the Update for Windows Server 2003, x64 Edition (973825) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=f1ebf2c8-0573-4686-adbc-099feeafcc9b)

Collapse this imageExpand this image

Download the Update for Windows Server 2003 for Itanium-based Systems (973825) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=5367c44d-2260-44a6-b4c1-2ce9e2b00e2d)

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591  (http://support.microsoft.com/kb/119591/ ) How to obtain Microsoft support files from online services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Prerequisites

You must have Windows Server 2003 Service Pack 2 installed to apply this update.

Restart requirement

You must restart your computer after you apply the update.

Update replacement information

This update does not replace any other updates.

File information

The English version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Back to the top

Update for Windows Server 2003 (KB973825)

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Advapi32.dll	5.2.3790.4555	619,008	18-Jul-2009	15:58	x86	SP2	SP2GDR
Advapi32.dll	5.2.3790.4555	619,008	18-Jul-2009	16:19	x86	SP2	SP2QFE

Back to the top

Update for Windows Server 2003, x64 Edition (KB973825)

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Advapi32.dll	5.2.3790.4555	1,052,160	18-Jul-2009	21:45	x64	SP2	SP2GDR
Wadvapi32.dll	5.2.3790.4555	619,008	18-Jul-2009	21:45	x86	SP2	WOW
Advapi32.dll	5.2.3790.4555	1,065,984	18-Jul-2009	16:32	x64	SP2	SP2QFE
Wadvapi32.dll	5.2.3790.4555	619,008	18-Jul-2009	16:32	x86	SP2	WOW

Back to the top

Update for Windows Server 2003 for Itanium-based Systems (KB973825)

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Advapi32.dll	5.2.3790.4555	1,482,752	18-Jul-2009	21:44	IA-64	SP2	SP2GDR
Wadvapi32.dll	5.2.3790.4555	619,008	18-Jul-2009	21:44	x86	SP2	WOW
Advapi32.dll	5.2.3790.4555	1,483,776	18-Jul-2009	16:32	IA-64	SP2	SP2QFE
Wadvapi32.dll	5.2.3790.4555	619,008	18-Jul-2009	16:32	x86	SP2	WOW

Back to the top

WORKAROUND

Important This section, method, or task contains steps that tell you how to modi...

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756  (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows

To work around this problem, change the PolicyScope registry value to 1 before you try to install the package. To do this, follow these steps.

Note If the computer is joined to a domain, a domain policy update may override the registry changes that you make. We strongly recommend that you disconnect the computer from the domain before you follow these steps.

1. Click Start, click Run, type regedit, and then click OK.
2. In Registry Editor, locate and then click the following registry key:
   HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Safer\CodeIdentifiers
   Note Before you modify this key, we recommend that you back up this key. To do this, right-click CodeIdentifiers, and then click Export. Save the file to a location where you can find it on the computer.
3. Change the PolicyScope registry value. To do this, double-click PolicyScope, and then change the setting from 0 to 1.
4. Close Registry Editor.
5. Click Start, click Run, type cmd, and then click OK to open a Command Prompt window.
6. At the command prompt, type the following command, and then press ENTER:
   net stop msiserver
   This command stops the Windows Installer service if the service is currently running in the background. When the service has stopped, close the Command Prompt window, and then go to step 7.
   
   Note If you receive the following message at the command prompt, close the Command Prompt window, and then go to step 7:
   The Windows Installer service is not started
7. Install the package that you were trying to install when you received the error message that is mentioned in the "Symptoms" section.
8. After you install the package, repeat steps 1 and 2. Then, change the PolicyScope registry value back to 0.
9. If you disconnected the computer from a domain, rejoin the domain, and then restart the computer.
   
   Note If you did not disconnect the computer from a domain, you do not have to restart the computer.

If the previous steps did not resolve the issue, follow these steps:

1. Click Start, click Run, type control admintools, and then click OK.
2. Double-click Local Security Policy.
3. Click Software Restriction Policies.
   
   Note If no software restrictions are listed, right-click Software Restriction Policies, and then click Create New Policy.
4. Under Object Type, double-click Enforcement.
5. Click All users except local administrators, and then click OK.
6. Restart the computer.

Important After you follow the previous steps, local administrators can install the .msi package or the .msp package. After the package is installed, reset the enforcement level by following the previous steps. In step 5, click All users instead of All users except local administrators.

Notes

• The workaround may not work in an Active Directory domain environment. In an Active Directory domain environment, a domain policy refresh operation will overwrite the local Software Restriction Policies.
• Adding more RAM to the computer will not resolve the problem.

Back to the top

MORE INFORMATION

Starting with Windows XP, a security policy that is named Software Restriction P...

Starting with Windows XP, a security policy that is named Software Restriction Policies (also known as SAFER) was introduced to help users avoid running unsafe files. Windows Installer uses software restriction policies to verify the signatures of signed .msi package files and signed .msp package files. Windows Installer does this to make sure that the files were not tampered with before they are installed on the computer. Windows XP and Windows Server 2003 require that the whole .msi package file or the whole .msp package file to be loaded into one contiguous piece of memory in the address space of the Windows Installer process.

If an .msi package file or an .msp package file is too large to fit into a contiguous piece of virtual memory, Windows Installer cannot verify that the package is correct. In this scenario, you experience the symptoms that are described in the “Symptoms” section. The fix that is described in this article enables software restriction policies to use less virtual memory to perform the signature verification. Therefore, Windows Installer can verify any size files.

How to change listening port on webbserver IIS 7?

Right click on your site in the left pane, and go to  Bindings. click Edit There you can add and remove ports which are bound to your site (ports it will respond on):

unable to install printer. the print processor does not exist

Ok obviously you are recieving this error upon the installation of a new or exisiting printer on your local area network, or heck it maybe connected directly to the PC. Well to fix this problem simply uninstall the driver, and then reinstall. You may be prompted during the hardware installation wizard to Use the Existing Driver (recommended) or reinstall the driver. Well, just reinstall it. This will remove, and reinstall the print processor associated with the service / printer.

To recap go to:

Start Control Panel Printer & Faxes Add a New Printer Start Hardware Wizard Reinstall the Printer Driver (do not use existing) Finish the Hardware Wizard Test Print (if you like) Should you have any issues feel free to collaborate and post them here. Hope this helps!

STOP 0x0000007B Error Messages

STOP 0x0000007B Error Messages

The STOP 0x0000007B error will always appear on a STOP message, more commonly called a Blue Screen of Death (BSOD). One of the errors below or a combination of both errors may display on the STOP message:

• "STOP: 0x0000007B"
  
• "INACCESSIBLE_BOOT_DEVICE"

The STOP 0x0000007B error may also be abbreviated as STOP 0x7B but the full STOP code will always be what's displayed on the blue screen STOP message.

Cause of STOP 0x0000007B Errors

STOP 0x0000007B errors are caused by device driver issues (especially those related to hard drive and other storage controllers), viruses, data corruption, and sometimes even hardware failures.
If STOP 0x0000007B isn't the exact STOP code you're seeing or INACCESSIBLE_BOOT_DEVICE isn't the exact message, please check my Complete List of STOP Error Codes and reference the troubleshooting information for the STOP message that you are seeing.

Resolution

Note: Some of these steps may require you to access Windows via Safe Mode. If that's not possible then skip those steps.

1. Restart your computer if you haven't already done so. The STOP 0x0000007B blue screen error might be a fluke.
   
2. Did you just install or make a change to a hard drive controller? If so, there's a good chance that the change you made caused the STOP 0x0000007B error.
   
   Undo the change and test for the 0x7B blue screen error.
   
   Depending on what changes you made, some solutions might include:
   
   
   • Remove or reconfigure the newly installed hard drive controller.
   • Startup with Last Known Good Configuration to undo related registry and driver changes.
   • Use System Restore to undo recent changes.
   • Rollback hard drive controller device driver to version prior to your driver update.
3. Verify that the SCSI chain is correctly terminated, assuming you're using SCSI hard drives in your computer. Incorrect SCSI termination has been known to cause STOP 0x0000007B errors.
   
   Note: Most home computers don't utilize SCSI hard drives.
   
4. Verify that the hard drive is properly installed. An improperly installed hard drive could cause STOP 0x0000007B errors and other issues.
   
5. Verify that the hard drive is configured properly in BIOS. The STOP 0x0000007B error could occur if the hard drive settings in BIOS are incorrect.
   
6. Scan your computer for viruses. Certain viruses that infect the master boot record (MBR) or boot sector can cause STOP 0x0000007B errors.
   
   Important: Make sure your virus scanning software is updated and configured to scan the MBR and boot sector.
   
7. Update the drivers for your hard drive controller. If the drivers to your hard drive controller are outdated, incorrect, or corrupted then the STOP 0x0000007B error will likely occur.
   
   Note: If the STOP 0x0000007B error occurs during the Windows setup process and you suspect that the reason is driver related, be sure to install the latest hard drive controller driver from the manufacturer for use during the installation of the operating system.
   
   Note: This is a likely solution if the second hexadecimal number after the STOP code is 0xC0000034.
   
8. Change the SATA mode in BIOS to IDE mode. Disabling some of the advanced features of SATA drives in BIOS could stop the STOP 0x0000007B error from showing up, especially if you're seeing it during a Windows installation.
   
   Note: Depending on your BIOS make and version, SATA mode may be referred to as AHCI mode and IDE mode may be referred to as either Legacy, ATA, or Compatibility mode.
   
9. Run chkdsk on your hard drive. If the boot volume is corrupted, the chkdsk command might repair the corruption.
   
   Important: You'll likely have to run chkdsk from the Recovery Console.
   
   Note: This will likely be the solution if the second hexadecimal number after the STOP code is 0xC0000032.
   
10. Perform an extensive test of your hard drive. If your hard drive has a physical problem, one very likely situation is the STOP 0x0000007B error you're seeing.
    
    Replace the hard drive if the diagnostics you complete suggest that there is a hardware problem with the drive.
    
11. Run the fixmbr command to create a new master boot record. A corrupted master boot record might be causing your STOP 0x0000007B error.
    
    Note: This will likely be the solution if the second hexadecimal number after the STOP code is 0xC000000E.
    
12. Clear the CMOS. Sometimes the STOP 0x0000007B error is caused by a BIOS memory issue. Clearing the CMOS could solve that problem.
    
13. Update your BIOS. In some situations, an outdated BIOS could cause a STOP 0x0000007B error due to incompatibilities with a hard drive controller.
    
14. Update the hard drive controller's firmware if possible. Just as with the BIOS in the previous step, an incompatibility could be causing the 0x7B error and a firmware update from the manufacturer may correct the problem.
    
15. Repair your Windows installation. If you've just replaced the motherboard in a computer without reinstalling Windows then this will likely fix your problem.
    
    Note: Sometimes a Windows repair will not fix a STOP 0x0000007B error. In those cases, a clean installation of Windows should do the trick.
    
    If you haven't just replaced your motherboard, a Windows reinstall probably will not fix your STOP 0x7B issue.
    
16. Perform basic STOP error troubleshooting. If none of the specific steps above help fix the STOP 0x0000007B error you're seeing, take a look at this general STOP error troubleshooting guide. Since most STOP errors are similarly caused, some of the suggestions might help.

Please let me know if you've fixed a blue screen of death with the STOP 0x0000007B STOP code using a method that I don't have above. I'd like to keep this page updated with the most accurate STOP 0x0000007B error troubleshooting information as possible.

Applies To

Any of Microsoft's Windows NT based operating systems could experience the STOP 0x0000007B error. This includes Windows 7, Windows Vista, Windows XP, Windows 2000, and Windows NT.

Still Having STOP 0x0000007B Issues?

Post the details of your STOP error in the PC Support Forums. Be sure to let us know the that you're seeing the 0x0000007B STOP code and also what steps, if any, you've already taken to resolve it.

How to change default gateway on windows by command line.

To display the entire contents of the IP routing table, type:

route print

To display the routes in the IP routing table that begin with 10., type:

route print 10.*

To add a default route with the default gateway address of 192.168.12.1, type:

route add 0.0.0.0 mask 0.0.0.0 192.168.12.1

To add a route to the destination 10.41.0.0 with the subnet mask of 255.255.0.0 and the next hop address of 10.27.0.1, type:

route add 10.41.0.0 mask 255.255.0.0 10.27.0.1

To add a persistent route to the destination 10.41.0.0 with the subnet mask of 255.255.0.0 and the next hop address of 10.27.0.1, type:

route -p add 10.41.0.0 mask 255.255.0.0 10.27.0.1

To add a route to the destination 10.41.0.0 with the subnet mask of 255.255.0.0, the next hop address of 10.27.0.1, and the cost metric of 7, type:

route add 10.41.0.0 mask 255.255.0.0 10.27.0.1 metric 7

To add a route to the destination 10.41.0.0 with the subnet mask of 255.255.0.0, the next hop address of 10.27.0.1, and using the interface index 0×3, type:

route add 10.41.0.0 mask 255.255.0.0 10.27.0.1 if 0×3

To delete the route to the destination 10.41.0.0 with the subnet mask of 255.255.0.0, type:

route delete 10.41.0.0 mask 255.255.0.0

To delete all routes in the IP routing table that begin with 10., type:

route delete 10.*

To change the next hop address of the route with the destination of 10.41.0.0 and the subnet mask of 255.255.0.0 from 10.27.0.1 to 10.27.0.25, type:

route change 10.41.0.0 mask 255.255.0.0 10.27.0.25

How can I clear the contents of the DNS resolution cache in Windows 2000 and later?

To clear the DNS cache, perform the following steps:

1. Start the Microsoft Management Console (MMC) DNS snap-in (Go to Start, Programs, Administrative Tools, and click DNS).
2. From the View menu, select Advanced.
3. Select and right-click the Cached Lookups tree node from the left-hand pane.
4. Select Clear Cache from the context menu.

You can also use the Dnscmd command in Windows Server 2003 to clear the cache. From the command prompt
, type

dnscmd /clearcache

how to monitor 802.1Q packets through wireshark

NIC: intel(R)82566DM

=========================================

Microsoft Windows* ---

To allow tagged frames to be passed to your packet capture software you must go into the registry and either add a registry dword and value or change the value of the registry key. Depending on the bus type of your network adapter you will either create the keyword "MonitorModeEnabled" for PCI/PCI-X Network Adapters, or "MonitorMode" for PCI-e based Network Adapters.

The new key (dword) should be placed at:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\00xx

where xx is the instance of the network adapter that you need to see tags on. (Check by opening and viewing the name of the adapter).

Note ControlSet001 may need to be CurrentControlSet or another 00x number.

If you are using a PCI or PCI-X Network Adapter the registry dword is: MonitorModeEnabled
Set the dword value to either:
0 - disabled (Do not store bad packets, Do not store CRCs, Strip 802.1Q vlan tags)
1 - enabled (Store bad packets. Store CRCs. Do not strip 802.1Q vlan tags)

If you are using a PCI-Express Network Adapter the registry dword is: MonitorMode
Set the dword value to either:
0 - disabled (Do not store bad packets, Do not store CRCs, Strip 802.1Q vlan tags)
1 - enabled (Store bad packets. Store CRCs. Do not strip 802.1Q vlan btag)
2 - enabled strip vlan (Store bad packets. Store CRCs. Strip 802.1Q vlan tag as normal)

In most cases you should set MonitorMode=1 or MonitorModeEnabled=1.

Warning: This modification should be made very carefully and only by skilled technicians since changes to the registry may disable your machine. This change should only be made for promiscuous mode/sniffing use.

the operation has been cancelled due to restrictions in effect on this computer outlook 2007

 INTERNET Options.




3. Click the Advanced tab.



4. Click Reset.



5. Click the Programs tab.



6. Click Set programs.



7. Click Set Default Programs.



8. Select Microsoft Outlook.



9. Select Set this program as default.



10. Click OK.



11. Close the Default Programs box.



12. Under Internet Options, click the Programs tab.



13. Click Make default under Default web browser.