Problem:

Have you forgot the administrator’s password? Can’t figure out your password and you can’t access Windows XP? That’s really so annoyed, right?

Solution:

Don’t worry, one of Spotmau PowerSuite 2010 highly recommended functions – Password Genius – can relieve you from such troubles. “Password Genius” tool is capable of changing and cleaning up the login password of Windows system. It can be used when users forgot login password and can’t access Windows system. It supports Windows XP, VISTA and Windows 7. You can recover any passwords, including Administrator and any User account password.
If you have lost Windows login password, all you need to do is to boot from Spotmau CD. With only a few clicks, you can easily blank Windows XP administrator’s password.

Procedure of finding back Windows XP administrator’s password:

1. Boot from the CD.

2. Enter POWER SUITE 2010’s interface, follow these steps: PowerSuite Bootcare2010 –>Password Kit –> Admin/User Password, then you will have the interface looking just like the following picture.

3. Select the “Windows XP” and “Administrator”, and then click “Start” , you’ll see:

4. Click “OK” and wait for a few seconds ,you’ll see “Password cleanup successfully” . Then you can access Windows XP without password. And you can reset your login password, too.

Check out the following link for a full spotmau review to see what other repair tools are included in this awesome CD.

The other day I told my elderly mother that I needed to perform a Windows XP virus repair on my computer. My mother was clearly confused. “Did you say your computer has a virus?”, she asked, “How does a machine get sick?”

While her words made me chuckle, the truth is that machines (specifically computers) can get sick. If the illness is not taken care of, then it can be deadly.

A computer virus acts very much like a human virus. It has the capability of reproducing itself. It travels through networks and the internet (just as a human virus travels through the air). A virus can also be caught by sharing DVDs and USB flash drives (the computer equivalent of eating off someone else’s plate.) Once inside your computer it goes about attaching itself to files and programs (the human equivalent of a viral infection).

Some viruses aren’t viruses at all. They are adware and spyware. Adware is more of a minor ache; it allows pop ups and unwanted advertisements. Spyware is a cancer, it can go undetected until your life is in ruins. Spyware is the most common means of identity theft.

Then there is your actual virus. Some are like head colds, they make it hard to get started, and then cause you to move slowly. Others are more like the flu, you just can’t function at all.

No matter what type of virus your computer has caught, it needs some medication to get well (Windows XP virus repair). Some tests need to be run in order for your computer to get the proper medications. These tests are called scans.

Scans are like human x-rays. They look around inside your system to see what is going on. Once the problem is found, then the proper medication is administered (a Windows XP virus repair).

I spent a load of money taking my computer to the doctors. These doctor visits were usually time consuming because there are many sick computers (just like humans, if a virus is floating around, it tends to make everyone sick at the same time.). Then I discovered my own private physician to perform Windows XP virus repairs as often as I needed. My private physician is antivirus and repair software. And the best part is, I only had to pay once and I get to call on him as often as necessary.

To sum up, Windows XP viruses are similar to human viruses in how they function. The best way to care for an infected computer is to perform routine Windows XP virus repair operations using antivirus software. Viruses leave behind corrupted files as well. Its not enough to just clean up a virus. It is also necessary to repair the corrupted files. An online Windows XP repair service which fixes corrupted files after virus infection is Reimage. For this online repair service I have written a Reimage Review here.

The Microsoft Point to Point Tunneling Protocol (PPTP) is used to create a Virtual Private Network (VPN) between a PPTP client and server. It is used for remote access from mobile users to connect back to their corporate network over the Internet. A PPTP client connects and authenticates to the PPTP server which assigns an IP address to the client and attaches the remote user to the network. After that, the remote user has full network connectivity just like being connected locally.

In the older PIX version 6.x, you could configure the PIX firewall itself to work as a PPTP server, thus you didn’t even need to have a Windows PPTP server in place. With the new ASA firewall however, you cannot terminate PPTP on the ASA itself. Therefore you must have a Microsoft PPTP server in the network in order to terminate PPTP connections from clients.

PPTP uses two protocols: GRE to encapsulate PPP packets and a control channel at TCP port 1723. Any stateful firewall would have a problem with allowing PPTP protocol without any special “fixup” because of the two protocols needed for communication (GRE and TCP 1723). Cisco ASA allows you to pass PPTP traffic through with a special “inspection” mechanism which checks the control traffic (TCP 1723) in order to dynamically open also access for GRE traffic to pass through with no problems.

In this post we will see two scenarios of allowing PPTP traffic through a Cisco ASA. In the first scenario we have a PPTP client on the inside of ASA which communicates with a PPTP server on the outside zone. In the second scenario we have a PPTP client on the outside of ASA which communicates with a PPTP server on the inside.

Scenario 1: PPTP client on inside and server on outside

The first scenario above depicts a PPTP server located on the outside of the ASA (Internet) and PPTP clients on the inside. Using the “nspect” command in the global policy-map we can enable access from inside to outside for PPTP.

! enable Port Address Translation on the outside interface
ciscoasa(config)#nat (inside) 1 0.0.0.0 0.0.0.0 0 0
ciscoasa(config)#global (outside) 1 interface

! Add PPTP inspection to the default policy-map using the default class-map
ciscoasa(config)# policy-map global_policy
ciscoasa(config-pmap)# class inspection_default
ciscoasa(config-pmap-c)# inspect pptp

Scenario 2: PPTP client on outside and server on inside

This scenario depicts a PPTP server located on the inside network. Here we must configure static NAT for the PPTP server and allow the appropriate protocols from outside (GRE, TCP 1723)

! translate the PPTP server private address 192.168.1.1 to public 50.50.50.1
ciscoasa(config)# static (inside,outside) 50.50.50.1 192.168.1.1 netmask 255.255.255.255

! allow the appropriate protocols from outside to inside
ciscoasa(config)# access-list acl-out permit gre any host 50.50.50.1
ciscoasa(config)# access-list acl-out permit tcp any host 50.50.50.1 eq 1723
ciscoasa(config)# access-group acl-out in interface outside