Scan all system files and repair in windows

In windows to repair all system files and check if they are intact you may need a windows CD
go to Start/Run, and type:
SFC /SCANNOW

loopback adapter in Xp and spoof MAC Address

To manually install the Microsoft Loopback adapter in Windows XP, follow these steps:

1. Click Start, and then click Control Panel. Because this is XP, you may have it set up this way, or you may have your interface set up in Classic view. Either way, navigate your way to 'Add Hardware', or 'Printers and Other Hardware'

2. Launch the Wizard to Add Hardware to your system. Do not be confused because you are not actually installing any new hardware, just simply adding a 'network adapter' which is acting as a virtual adapter.
3. Click next, once you have launched the Wizard.  You will see a series of dialog boxes open to ask you about scanning for hardware changes, etc – you will want to do everything manually in this exercise. There will be no automatic scanning for any reason because you have not installed anything, the installation will immediately fail.

4. You will next be asked if the hardware is connected. You can select Yes from the options and click Next.

5. Now, select *from the bottom of the list* the 'Add a new hardware device' option, and then click Next.

6. Click Install the hardware that I manually select from a list, and then click Next.

7. Select 'Network adapters' from the Common hardware types section within the dialog box. Click Next.

8. Select Microsoft and then the Microsoft Loopback Adapater, and then click Next.

Lastly, you will be prompted to Finish up the installation.

Viewing and Configuring the Loopback Adapter

Once you have finished the installation, you will have a brand new loopback interface configured on your PC. There are a few things that you should know about the use of the loopback adapter.

• First, it will appear as a new interface connection in the properties of My Network Places. It will also show up with you view IPCONFIG from the command line.
• Second, you will be confused about it when you see it because if you have multiple adapters set up as most do, you will see Local Area Connection, Local Area Connection 2, Local Area Connection 3 and so on. A trick to seeing what is what is to hover your mouse over the connections until you find the right one as seen in the illustration here:

• It is recommended that you rename the connection to something like 'LOOPBACK' so you can differentiate what it is quicker, and if you use IPCONFIG, check out the output below, you will know it's the LOOPBACK.

C:\>ipconfig

<<Output Omitted>>

Ethernet adapter LOOPBACK:

   Connection-specific DNS Suffix  . :
   Autoconfiguration IP Address. . . : 169.254.25.129
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :

C:\>

• Lastly, notice that the address given to the adapter is on the APIPA subnet. APIPA, which is Automatic Private IP Addressing, is a way for the PC to put itself on the network if DHCP is configured but not available. You can keep this on the APIPA range or hard code a static IP address in to use and test with.
• Unless you disable the interface, it will always appear as up because it cannot go down from a hardware failure as there is no hardware to fail.

Now you can test with this IP address, it will always remain stable and so on.

You can create a MAC Spoof from loopback by using following trick

Just go

1.run and type ncpa.cpl

2.Select  loopback LAN and your own LAN by using ctrl and click

3.Right click and select bridge

4.You have done .Now the traffic flow through the Network bridge and your original mac is hidden

Install any fonts in ubuntu

Close all OpenOffice windows.

2. Navigate to the following Ubuntu menus.
   Application > Add/Remove...
3. Install Fonty Python. This is a font manager for Ubuntu. It's similar to Adobe Type Manager. Find below attached screenshot.
4. Open Fonty Python.
5. Navigate to the following Fonty Python's menu Help > Help F1.
6. The help window will open. Follow instructions on this page.
7. Open OpenOffice. Find the font under the font menu.

Option 2 : For advanced Users

1. Close all OpenOffice windows.
2. Download the font you want from the following site. For example Arial Narrow. Find below attached screenshot to clarify download link location.
   http://www.free-fonts-ttf.org/true-t...ns.htm?page=32
3. Copy the fonts to your fonts directory. This directory is located under. This is optional but you can create sub-folders inside this directory.
   /usr/share/fonts/truetype
4. If you do not have access to copy the fonts the the above folder then type in the following command in TERMINAL.
   Code:

    gksudo nautilus 

5. Nautilus file browser will open.
6. Use Nautilus to copy the fonts to your .fonts directory.
7. To rebuild your fonts list. Type in the following command in TERMINAL
   Code:

    sudo fc-cache -vf 

8. Open OpenOffice. Find the font under the font menu.
9. That's it. Now you can read .doc or .docx that comes from other people who uses this font.

Concurrent multiple Remote Desktop Sessions XP

Concurrent  Multiple Remote Desktop Sessions in Windows XP SP2
Windows XP does not allow concurrent sessions for its Remote Desktop feature. What this means is that if a user is logged on at the local console, a remote user has to kick him off (and ironically, this can be done even without his permission) before starting work on the box. This is irritating and removes much of the productivity that Remote Desktop brings to Windows. Read on to learn how to remove that limitation in Windows XP SP2

A much touted feature in SP2 (Service Pack 2) since then removed was the ability to do just this, have a user logged on locally while another connects to the terminal remotely. Microsoft however removed the feature in the final build. The reason probably is that the EULA (End User License Agreement) allows only a single user to use a computer at a time. This is (IMHO) a silly reason to curtail Remote Desktop's functionality, so we'll have a workaround.

Microsoft did try out the feature in earlier builds of Service Pack 2 and it is this that we're going to exploit here. We're going to replace termserv.dll (The Terminal Server) with one from an earlier build (2055).

To get Concurrent Sessions in Remote Desktop working, follow the steps below exactly:

1. Download the termserv.zip file  and extract it somewhere. (You have to be registered to see the file)
2. Reboot into Safe Mode. This is necessary to remove Windows File Protection.
3. Copy the termserv.dll in the zip to %windir%\System32 and %windir%\ServicePackFiles\i386. If the second folder doesn't exist, don't copy it there. Delete termserv.dll from the dllcache folder: %windir%\system32\dllcache
4. Merge the contents of Concurrent Sessions SP2.reg file into the registry.
5. Make sure Fast User Switching is turned on. Go Control Panel -> User Accounts -> Change the way users log on or off and turn on Fast User Switching.
6. Open up the Group Policy Editor: Start Menu > Run > 'gpedit.msc'. Navigate to Computer Configuration > Administrative Templates > Windows Components > Terminal Services. Enable 'Limit Number of Connections' and set the number of connections to 3 (or more). This enables you to have more than one person remotely logged on.
7. Now reboot back into normal Windows and try out whether Concurrent Sessions in Remote Desktop works. It should!

If anything goes wrong, the termserv_sp2.dll is the original file you replaced. Just rename it to termserv.dll, reboot into safe mode and copy it back.

The termserv.dl_ file is provided in the zip is for you slipstreamers out there. Just replace that file with the corresponding file in the Windows installation disks.

Alternate location for DLL for XP Service Pack 3.

source

Wake on LAN WOL in Linux

Configure WOL in Ubuntu

1. If you havent already, go to your BIOS, and turn on WakeOnLAN (it varies, look for it.) If your network card is onboard, your set for step 2, otherwise there is probably a cable that should go from your network card to your motherboard, though this is not always the case.

2. Back in ubuntu, kubuntu, xubuntu, w/e, we now need to make a script that will run every time the computer is started, because this command only lasts until the computer is turned on again once.

2a. Find out what network device you want to have the computer wake-able from, usually all, which is just one. If you have more network devices in your system, 9 chances out of 10, you already know what they are called.
You can NOT wake up a laptop or computer that is only connected via wireless with wake-on-lan, unless the bios has a method for this, this is very rare.
In your terminal, type: Code:

 ifconfig 

You'll get something like: (I have removed my mac address for security) Code:

 eth0     
Link encap:Ethernet
 HWaddr 01:23:45:67:89:ab         
inet addr:192.168.1.2
Bcast:192.168.1.255  Mask:255.255.255.0         
inet6 addr: fe80::215:f2ff:fe6f:3487/64 Scope:Link         
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1         
RX packets:71495 errors:0 dropped:0 overruns:0 frame:0         
TX packets:76190 errors:0 dropped:0 overruns:0 carrier:0          
collisions:0 txqueuelen:1000         
RX bytes:23164212 (22.0 MiB)
TX bytes:7625016 (7.2 MiB)         
Interrupt:217 Base address:0xd400  lo      
Link encap:Local Loopback         
inet addr:127.0.0.1  Mask:255.0.0.0         
inet6 addr: ::1/128 Scope:Host         
UP LOOPBACK RUNNING  MTU:16436  Metric:1         
RX packets:1290 errors:0 dropped:0 overruns:0 frame:0         
TX packets:1290 errors:0 dropped:0 overruns:0 carrier:0         
collisions:0 txqueuelen:0           RX bytes:161182 (157.4 KiB)  TX bytes:161182 (157.4 KiB) 

So, I want this system to be wake-able from eth0.

2b. Now we create the script.
Note: you must be an administrator on the system you are doing this to. Code:

 sudo -i 

Enter your password at the prompt.
Change to the startup script directory and start editing a new file: Code:

 cd /etc/init.d/
pico wakeonlanconfig 

Paste, or type this into the file, replacing eth0 with your network device, repeat the ethtool line as many times for your devices before the exit line: Code:

 #!/bin/bash
ethtool -s eth0 wol g
 exit 

Set the permissions of the file: Code:

 chmod a+x wakeonlanconfig 

Make the script run on startup: Code:

 update-rc.d -f wakeonlanconfig defaults 

You should see something like: Code:

 Adding system startup for
/etc/init.d/wakeonlanconfig ...  
/etc/rc0.d/K20wakeonlanconfig ->../init.d/wakeonlanconfig   
/etc/rc1.d/K20wakeonlanconfig -> ../init.d/wakeonlanconfig   
/etc/rc6.d/K20wakeonlanconfig -> ../init.d/wakeonlanconfig   
/etc/rc2.d/S20wakeonlanconfig -> ../init.d/wakeonlanconfig   
/etc/rc3.d/S20wakeonlanconfig -> ../init.d/wakeonlanconfig   
/etc/rc4.d/S20wakeonlanconfig -> ../init.d/wakeonlanconfig   
/etc/rc5.d/S20wakeonlanconfig -> ../init.d/wakeonlanconfig 

Now we finish by running it, and making sure there are no errors. Code:

 /etc/init.d/wakeonlanconfig 

This should produce no output and put you right back at the prompt you started at.

3. Use it. you'll need something to send wake-on-lan packets with, "wakeonlan" is in the repos. And you'll need the mac address of the system.

To get your MAC address, on the same system you just enabled WOL on, type: Code:

 ifconfig | grep HW 

its the thing that looks like 01:23:45:67:89:ab , write it down.
turn off that system: Code:

 sudo halt 

if your using wakeonlan from the repos, and you are on the same network as the computer your tying to wake up, replace 01:23:45:67:89:ab with your mac address and do, from another computer: Code:

 wakeonlan 01:23:45:67:89:ab 

In MOST cases, you CAN SEND wake on lan packets from a wireless connected computer.
If that doesnt work, its likely the port on the system your trying to wake up isnt the default (9), try 7, or if your BIOS settings or book told you one, use that one. Code:

 wakeonlan -p 7 01:23:45:67:89:ab 

If that STILL doesnt work, make sure wakeonlan is enabled in your bios and your hardware supports it.

*Note: It has been said that you need to disable -i from halt, however I have never had to do this, nor do I know how.
source

WOL from internet
Here is generic configuration for router (may vary depend on your router and IP addresses used):

Name: WakeOnLan Broadcast
Enable: yes
IP Address: 192.168.0.255 <--- here is the private broadcast IP address, NOT your IP like 192.168.0.1
Protocol: UDP
Private Port: 9
Public Port: 9
Schedule: Always
source