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):

Tuesday, June 15, 2010
Monday, June 14, 2010
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:
To recap go to:
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"
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.- Restart your computer if you haven't already done so. The STOP 0x0000007B blue screen error might be a fluke.
- 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.
- 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. - Verify that the hard drive is properly installed. An improperly installed hard drive could cause STOP 0x0000007B errors and other issues.
- 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.
- 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. - 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. - 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. - 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. - 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. - 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. - Clear the CMOS. Sometimes the STOP 0x0000007B error is caused by a BIOS memory issue. Clearing the CMOS could solve that problem.
- Update your BIOS. In some situations, an outdated BIOS could cause a STOP 0x0000007B error due to incompatibilities with a hard drive controller.
- 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.
- 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. - 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.
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.Friday, June 11, 2010
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
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
Thursday, June 10, 2010
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
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
Monday, June 7, 2010
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:
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).
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).
|
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.
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.
Tuesday, June 1, 2010
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.
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.
Subscribe to:
Posts (Atom)