Premium Account Site

http://getpremiumdownloadlinks.blogspot.com/2011/04/file-sonic-premium-account.html

Read More

ICS With Ubuntu 10.04 Without Squid Proxy

Introduction

Internet Connection Sharing (ICS) provides the ability for one computer to share its Internet connection with another computer. To do this, a computer with an Internet connection must be configured to function as an Internet gateway. A second computer (or network of computers) connects to the Internet indirectly via the gateway computer.

Situations in which ICS may be necessary include:
dial up connection
authenticated (PPPoA/E) connection
wireless connection
When it is impractical (such as with distance) to run multiple network cables to each computer.

GUI Method via Network Manager (Ubuntu 9.10 and up)

In order to share an Internet connection, the computer that will do the sharing must have two network cards or ports. This assumes that you are using at least one Ethernet port and that it is identified as "eth0". eth0 will be the port that other computers will connect to you on.

When you are logged in:
Go to "System" on your top bar
Navigate to "Preferences" and select "Network Connections"
When that window opens, select "Auto eth0" and press "Edit" (This assumes that you are connected to the internet on some other port, for ex. wlan0 using wireless)

A new window will open. Navigate to the tab titled "IPv4 Settings" and change the Method to "Shared to other computers". After restarting the computer you should now be able to plug in any computer into your other Ethernet port or share through your wireless card.

Note: To clarify the above example here is an example configuration that will work -
You are already connected to the internet using your wireless on port wlan0
The ethernet port eth0 is connected to the PC that needs to share your internet connection (or you could wire eth0 to a router for multiple machines)

Note: in the case of connecting a router, especially one with wireless, where you want the users to share your connection:

Check before you start (in Synaptic or with dpkg-query -l dnsmasq*) that dnsmasq-base is installed and that dnsmasq is not installed. Install or uninstall as appropriate (see next section).
After connecting the router, to enable masquerading, type: sudo iptables -t nat -A POSTROUTING -j MASQUERADE

Wireless Ad-Hoc connection sharing scenario

Step by step guide:
dnsmasq-base has to be installed: sudo apt-get install dnsmasq-base

remove dnsmasq as it's conflicting with NetworkManager: sudo apt-get remove dnsmasq

restart NetworkManager: sudo /etc/init.d/network-manager restart

Add a new wireless network with NetworkManager (left-click on NetworkManager icon, then select "Create New Wireless Network")

Call the new network "UbuntuAdhoc" (note: if you choose another name you will have to turn on connection sharing later by editing the network you just created!)

Set encryption to "WEP40..." (note: you may have to experiment here according to what type of encryption with ad-hoc the phone/other laptop/pc supports, wpa is not supported)

NetworkManager now should connect to itself (which means it creates the ad-hoc wireless network and routes any internet traffic to your wired network interface). Now connect with the client(s) and you should have a working internet connection.

Ubuntu Internet Gateway Method (iptables)

You will need two network cards in the gateway computer, or a PPP interface and a network card. One network card (or PPP interface) connects to the internet, we will call this card eth0. The other card connects to your internal network, we will call this eth1. It is also possible to do ICS with a single network card. In this case, use eth0 for the internet and eth0:0 for the internal network.

Internet <<==>> eth0 <> Ubuntu gateway <> eth1 <<==>> Client PC

Internet <<==>> ppp0 <> Ubuntu gateway <> eth1 <<==>> Client PC

Internet <<==>> eth0 <> Ubuntu gateway <> eth0:0 <<==>> Client PC

Gateway set up

The following example will focus on the most common gateway setup; an Ubuntu computer with two wired network adapters (eth0 and eth1) hosting ICS to a static internal network configured for the 192.168.0.x subnet.

For this example, eth0 is used to represent the network card connected to the internet and eth1 represents the network card connected to a client PC. You can replace eth0 and eth1 as needed for your situation. Also, any private IP subnet can be used for the internal network IP addresses.

In summary:

eth0 = the network adapter with internet (external or WAN).
eth1 = the network adapter to which a second computer is attached (internal or LAN).
192.168.0.x = IP subnet for eth1

Your setup may be different. If so, make sure to change them accordingly in the following commands.

Configure internal network card

Configure your internal network card (eth1) for static IP like so:
sudo ip addr add 192.168.0.1/24 dev eth0

(The external and internal network cards cannot be on the same subnet)
Configure NAT

Configure iptables for NAT translation so packets can be correctly routed through the Ubuntu gateway.
sudo iptables -A FORWARD -o eth0 -i eth1 -s 192.168.0.0/24 -m conntrack --ctstate NEW -j ACCEPT
sudo iptables -A FORWARD -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
sudo iptables -A POSTROUTING -t nat -j MASQUERADE

(rule1 allows forwarded packets (initial ones), rule2 allows forwarding of established connection packets (and those related to ones that started), rule3 does the NAT.)

IPtables settings need to be set-up at each boot (they are not saved automatically), with the following commands:
Save the iptables:

sudo iptables-save | sudo tee /etc/iptables.sav
Edit /etc/rc.local and add the following lines before the "exit 0" line:

iptables-restore < /etc/iptables.sav

Enable routing
Configure the gateway for routing between two interfaces by enabling IP forwarding:

sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward"


Edit /etc/sysctl.conf and (up to 10.04) add these lines:

net.ipv4.conf.default.forwarding=1
net.ipv4.conf.all.forwarding=1

The /etc/sysctl.conf edit is required because of following Bug (Hardy and later releases) Launchpad Bug Report

From 10.10 on it suffices to edit /etc/sysctl.conf and uncomment

#net.ipv4.ip_forward=1

so that it reads
net.ipv4.ip_forward=1

Client set up

Any OS can connect to the internet as an ICS client as long as networking has been configured correctly. The following example will focus on how to set up an Ubuntu ICS client. For this example, it is assumed that the client is connected to an Ubuntu gateway which has been configured to share ICS on the 192.168.0.x subnet according to the gateway set up outlined above.

For this example, eth0 is the network card on the client which is connected (by crossover cable) to eth1 on the Ubuntu gateway. You can replace eth0 as needed for your situation. Also, any private IP subnet can be used for the internal network IP address, as long as it matches the subnet on the gateway.
Disable networking

sudo /etc/init.d/networking stop

Give the client a static IP address

sudo ip addr add 192.168.0.100/24 dev eth0

This IP address can be anything within the gateway's private IP range.
Configure routing

sudo ip route add default via 192.168.0.1

This address should match the IP address on the gateway's internal network card (eth1 in the above example).
Configure DNS servers

Unless your ICS gateway can also perform DNS, you must manually configure the client with your ISP DNS servers. If you do not know your ISP's DNS servers, you can use OpenDNS servers instead.
Backup your current /etc/resolve.conf file:

sudo cp /etc/resolv.conf /etc/resolv.conf.backup
Open /etc/dhcp3/dhclient.conf with your favorite text editor:

sudo nano /etc/dhcp3/dhclient.conf
Search for the line that starts "prepend domain-name-servers", and change it to look like this:

prepend domain-name-servers 208.67.222.222,208.67.220.220;

208.67.222.222 and 208.67.220.220 are OpenDNS DNS servers. If you wish to use your ISP's DNS servers, use them here instead of the OpenDNS servers.

Restart networking

sudo /etc/init.d/networking restart

Once this is finished, your client will now have access to the internet via ICS. Please direct any questions/comments to the Internet Connection Sharing Documentation thread.

A beginner's working example of a Ubuntu Desktop with 2 nic cards, sharing internet connection http://ubuntuforums.org/showthread.php?p=3713684

Advanced Gateway Configuration

The above example outlines how to do basic ICS on a static IP network. Once you have configured your Ubuntu computers for ICS and confirmed that everything works across your static network, there are a few advanced routing configurations which can make it much easier to set up the ICS client.

Advanced configurations include DHCP server, and DNS server. A DHCP server allows the client to get an ip address automatically without having to manually configure a static IP. A DNS server allows the client to resolve internet host names without manually configuring DNS addresses.

DHCP/DNS server

This is deceptively easy, and will be acceptable for most situations. However, it will not allow the ICS client to see computers on different subnets.
Install software

sudo aptitude install dnsmasq
Stop the server

After dnsmasq has been installed, it is automatically started, so it will need to be stopped before changes can be made.
sudo /etc/init.d/dnsmasq stop
Make a backup of the well commented configuration file (we won't use any of this, but it's handy to have a copy of for reference later)

sudo cp /etc/dnsmasq.conf /etc/dnsmasq.conf-backup
Edit /etc/dnsmasq.conf with your favorite text editor and add the following two lines:

interface=eth1
dhcp-range=192.168.0.100,192.168.0.250,72h

Note: The "interface" should match the interface that your clients are connected to, and the "dhcp-range" should be within the gateway's private IP subnet you configured according to the "Gateway set up" directions above.
Start the DHCP/DNS server

sudo /etc/init.d/dnsmasq start

Now your clients should be able to pull an automatic ip address and resolve host names.

Other approaches

The following section includes a rough outline of some alternative methods for configuring an ICS gateway. They are incomplete and untested. They are included simply for the sake of information.

Alternate server software (CLI)

There are other ways to host ICS, but they are outside the scope of this article.

Alternate NAT

The ipmasq daemon does NAT routing so you don't have to configure iptables. The following directions are incomplete and should not be considered a full description of what needs to be done to configure ipmasq.

sudo aptitude install ipmasq

Configure ipmasq to allow dhcp requests, otherwise you need to stop ipmasq to make a connection. You need to copy a .rul from the documentation directory into the /etc config and edit the interface name. Then reconfigure ipmasq to start after networking has been started

sudo dpkg-reconfigure ipmasq.

Dedicated DHCP server

dhcp3 is an easy to configure and scalable true DHCP server that can be configured for many different aplications. dhcp3 configuration is more complex, but it can be useful in many situations:

https://help.ubuntu.com/community/dhcp3-server

Dedicated DNS server

BIND9 is a popular and well supported local DNS server. It is very versatile, and very powerful, but difficult to configure correctly:

https://help.ubuntu.com/community/BIND9ServerHowto

Alternate gateway software (GUI)

Another approach --- set up Firestarter, to run connection sharing, set up dhcp3-server, and set its configuration to listen to the correct eth*. To change this later, run sudo dpkg-reconfigure dhcp3-server.

Basically, you need to have Firestarter active/turned on/protecting, to have the connection shared.

When you install dhcp3-server, it will place a sample config file in your /etc/dhcp3 folder, called dhcpd.conf. I suggest you install dhcp3-server first, and then firestarter, cause if you are lucky, firestarter will set up a new config file for dhcp3 for you.

At any time that changes are made to your dhcpd.conf file, restart the server - sudo /etc/init.d/dhcp3-server restart will do it. Alternatively, every time you run the sudo dpkg-reconfigure dhcp3-server, at the end, your server will restart.

There are several issues that I had...first of all, the Firestarter firewall won't even start if you don't have it configured to listen to the right interface...You can change which one it listens to in Preferences --> Network Settings. The Local network connected device must be the same as you have dhcp3-server listening to, of course, both checkboxes under that need to be checked. The Internet connected network device will be the one that is configured for Internet. Now, I have two NICs, but I have pppoe configured on eth0, and I have Internet connection sharing configured on the same one, cause eth0 is also configured for a static 192.168 internal IP for my internal network.

simple iptables example

simple example wlan0 has the internet connection eth0 is being used to share the connection it could be directly with a single pc via a crossover cable or switch or you could have a router with a cable from eth0 to the wan port and a whole lan setup behind this. Interestingly the internet connection could be ppp0 a 3g or mobile Internet modem.

#!/bin/sh
#
# internet connection sharing wlan0 is the gate way
# eth0 is the lan port this might use a straight ethernet cable to a router wan port or a switch or a single PC
# 192.168.2.2 is the port that is being used by the lan for access I changed it to 192.168.2.254 and set fixed addresses for the wan and router
#
# change wlan0 to ppp0 and you can use this for mobile broadband connection sharing
#
ip link set dev eth0 up
ip addr add 192.168.2.1/24 dev eth0
sysctl net.ipv4.ip_forward=1
iptables -t nat -A POSTROUTING -o wlan0 -s 192.168.2.0/24 -j MASQUERADE
iptables -t nat -A PREROUTING -i wlan0 -p tcp --dport 3074 -j DNAT --to-destination 192.168.2.2
iptables -t nat -A PREROUTING -i wlan0 -p udp -m multiport --dports 88,3074 -j DNAT --to-destination 192.168.2.2
iptables -A FORWARD -i wlan0 -d 192.168.2.2 -p tcp --dport 3074 -j ACCEPT
iptables -A FORWARD -i wlan0 -d 192.168.2.2 -p udp -m multiport --dports 88,3074 -j ACCEPT

You could use the above as a bash script changing things to suit
If things go wrong The Following script should save you if things get badly messed up.



#!/bin/sh
#
# rc.flush-iptables - Resets iptables to default values.
#
# Copyright (C) 2001 Oskar Andreasson <bluefluxATkoffeinDOTnet>
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; version 2 of the License.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program or from the site that you downloaded it
# from; if not, write to the Free Software Foundation, Inc., 59 Temple
# Place, Suite 330, Boston, MA 02111-1307 USA
#
# Configurations
#
IPTABLES="/usr/sbin/iptables"
#
# reset the default policies in the filter table.
#
$IPTABLES -P INPUT ACCEPT
$IPTABLES -P FORWARD ACCEPT
$IPTABLES -P OUTPUT ACCEPT
#
# reset the default policies in the nat table.
#
$IPTABLES -t nat -P PREROUTING ACCEPT
$IPTABLES -t nat -P POSTROUTING ACCEPT
$IPTABLES -t nat -P OUTPUT ACCEPT
#
# reset the default policies in the mangle table.
#
$IPTABLES -t mangle -P PREROUTING ACCEPT
$IPTABLES -t mangle -P POSTROUTING ACCEPT
$IPTABLES -t mangle -P INPUT ACCEPT
$IPTABLES -t mangle -P OUTPUT ACCEPT
$IPTABLES -t mangle -P FORWARD ACCEPT
#
# flush all the rules in the filter and nat tables.
#
$IPTABLES -F
$IPTABLES -t nat -F
$IPTABLES -t mangle -F
#
# erase all chains that's not default in filter and nat table.
#
$IPTABLES -X
$IPTABLES -t nat -X
$IPTABLES -t mangle -X

Further reading https://help.ubuntu.com/community/IptablesHowTo

Internet Connection Sharing Documentation thread http://ubuntuforums.org/showthread.php?t=503287

Attachment: squidku.txt.rar
Attachment: iptables.sav.backup
Attachment: iptables.sav

Read More

Software ISlami, Alqurn di microsoft office 2007 & 2003

Attachment: QuranInWord2007.zip
Attachment: KamusBahasaArabv2.0.rar
Attachment: Mufid v1.0.zip

Read More

Terminal Server (1 Komputer Untuk Unlimiter User Login On Network )

Sopwer Ini Aku Dapet Untuk Keperluan Multi User On Network

Attachment: Terminal Server Patch XP Pro.rar

Read More

Network Configuration

Ubuntu ships with a number of graphical utilities to configure your network devices. This document is geared toward server administrators and will focus on managing your network on the command line.

Ethernet Interfaces

Ethernet interfaces are identified by the system using the naming convention of ethX, where X represents a numeric value. The first Ethernet interface is typically identified as eth0, the second as eth1, and all others should move up in numerical order.

Identify Ethernet Interfaces

To quickly identify all available Ethernet interfaces, you can use the ifconfig command as shown below.

ifconfig -a | grep eth
eth0      Link encap:Ethernet  HWaddr 00:15:c5:4a:16:5a

Another application that can help identify all network interfaces available to your system is the lshw command. In the example below, lshw shows a single Ethernet interface with the logical name of eth0 along with bus information, driver details and all supported capabilities.

sudo lshw -class network
  *-network
       description: Ethernet interface
       product: BCM4401-B0 100Base-TX
       vendor: Broadcom Corporation
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: eth0
       version: 02
       serial: 00:15:c5:4a:16:5a
       size: 10MB/s
       capacity: 100MB/s
       width: 32 bits
       clock: 33MHz
       capabilities: (snipped for brevity)
       configuration: (snipped for brevity)
       resources: irq:17 memory:ef9fe000-ef9fffff

Ethernet Interface Logical Names

Interface logical names are configured in the file /etc/udev/rules.d/70-persistent-net.rules. If you would like control which interface receives a particular logical name, find the line matching the interfaces physical MAC address and modify the value of NAME=ethX to the desired logical name. Reboot the system to commit your changes.

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:15:c5:4a:16:5a", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:15:c5:4a:16:5b", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

Ethernet Interface Settings

ethtool is a program that displays and changes Ethernet card settings such as auto-negotiation, port speed, duplex mode, and Wake-on-LAN. It is not installed by default, but is available for installation in the repositories.

sudo apt-get install ethtool

The following is an example of how to view supported features and configured settings of an Ethernet interface.

sudo ethtool eth0
Settings for eth0:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Half 1000baseT/Full 
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Half 1000baseT/Full 
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: g
        Wake-on: d
        Current message level: 0x000000ff (255)
        Link detected: yes

Changes made with the ethtool command are temporary and will be lost after a reboot. If you would like to retain settings, simply add the desired ethtool command to a pre-up statement in the interface configuration file /etc/network/interfaces.

The following is an example of how the interface identified as eth0 could be permanently configured with a port speed of 1000Mb/s running in full duplex mode.

auto eth0
iface eth0 inet static
pre-up /usr/sbin/ethtool -s eth0 speed 1000 duplex full

	Although the example above shows the interface configured to use the static method, it actually works with other methods as well, such as DHCP. The example is meant to demonstrate only proper placement of the pre-up statement in relation to the rest of the interface configuration.

IP Addressing

The following section describes the process of configuring your systems IP address and default gateway needed for communicating on a local area network and the Internet.

Temporary IP Address Assignment

For temporary network configurations, you can use standard commands such as ip, ifconfig and route, which are also found on most other GNU/Linux operating systems. These commands allow you to configure settings which take effect immediately, however they are not persistent and will be lost after a reboot.

To temporarily configure an IP address, you can use the ifconfig command in the following manner. Just modify the IP address and subnet mask to match your network requirements.

sudo ifconfig eth0 10.0.0.100 netmask 255.255.255.0

To verify the IP address configuration of eth0, you can use the ifconfig command in the following manner.

ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:15:c5:4a:16:5a  
          inet addr:10.0.0.100  Bcast:10.0.0.255  Mask:255.255.255.0
          inet6 addr: fe80::215:c5ff:fe4a:165a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:466475604 errors:0 dropped:0 overruns:0 frame:0
          TX packets:403172654 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2574778386 (2.5 GB)  TX bytes:1618367329 (1.6 GB)
          Interrupt:16 

To configure a default gateway, you can use the route command in the following manner. Modify the default gateway address to match your network requirements.

sudo route add default gw 10.0.0.1 eth0

To verify your default gateway configuration, you can use the route command in the following manner.

route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.0.0.0        0.0.0.0         255.255.255.0   U     1      0        0 eth0
0.0.0.0         10.0.0.1        0.0.0.0         UG    0      0        0 eth0

If you require DNS for your temporary network configuration, you can add DNS server IP addresses in the file /etc/resolv.conf. The example below shows how to enter two DNS servers to /etc/resolv.conf, which should be changed to servers appropriate for your network. A more lengthy description of DNS client configuration is in a following section.

nameserver 8.8.8.8
nameserver 8.8.4.4

If you no longer need this configuration and wish to purge all IP configuration from an interface, you can use the ip command with the flush option as shown below.

ip addr flush eth0

	Flushing the IP configuration using the ip command does not clear the contents of /etc/resolv.conf. You must remove or modify those entries manually.

Dynamic IP Address Assignment (DHCP Client)

To configure your server to use DHCP for dynamic address assignment, add the dhcp method to the inet address family statement for the appropriate interface in the file /etc/network/interfaces. The example below assumes you are configuring your first Ethernet interface identified as eth0.

auto eth0
iface eth0 inet dhcp

By adding an interface configuration as shown above, you can manually enable the interface through the ifup command which initiates the DHCP process via dhclient.

sudo ifup eth0

To manually disable the interface, you can use the ifdown command, which in turn will initiate the DHCP release process and shut down the interface.

sudo ifdown eth0

Static IP Address Assignment

To configure your system to use a static IP address assignment, add the static method to the inet address family statement for the appropriate interface in the file /etc/network/interfaces. The example below assumes you are configuring your first Ethernet interface identified as eth0. Change the address, netmask, and gateway values to meet the requirements of your network.

auto eth0
iface eth0 inet static
address 10.0.0.100
netmask 255.255.255.0
gateway 10.0.0.1

By adding an interface configuration as shown above, you can manually enable the interface through the ifup command.

sudo ifup eth0

To manually disable the interface, you can use the ifdown command.

sudo ifdown eth0

Loopback Interface

The loopback interface is identified by the system as lo and has a default IP address of 127.0.0.1. It can be viewed using the ifconfig command.

ifconfig lo
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:2718 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2718 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:183308 (183.3 KB)  TX bytes:183308 (183.3 KB)

By default, there should be two lines in /etc/network/interfaces responsible for automatically configuring your loopback interface. It is recommended that you keep the default settings unless you have a specific purpose for changing them. An example of the two default lines are shown below.

auto lo
iface lo inet loopback

Name Resolution

Name resolution as it relates to IP networking is the process of mapping IP addresses to hostnames, making it easier to identify resources on a network. The following section will explain how to properly configure your system for name resolution using DNS and static hostname records.

DNS Client Configuration

To configure your system to use DNS for name resolution, add the IP addresses of the DNS servers that are appropriate for your network in the file /etc/resolv.conf. You can also add an optional DNS suffix search-lists to match your network domain names.

Below is an example of a typical configuration of /etc/resolv.conf for a server on the domain "example.com" and using two public DNS servers.

search example.com
nameserver 8.8.8.8
nameserver 8.8.4.4

The search option can also be used with multiple domain names so that DNS queries will be appended in the order in which they are entered. For example, your network may have multiple sub-domains to search; a parent domain of example.com, and two sub-domains, sales.example.com and dev.example.com.

If you have multiple domains you wish to search, your configuration might look like the following.

search example.com sales.example.com dev.example.com
nameserver 8.8.8.8
nameserver 8.8.4.4

If you try to ping a host with the name of server1, your system will automatically query DNS for its Fully Qualified Domain Name (FQDN) in the following order:

1. server1.example.com

2. server1.sales.example.com

3. server1.dev.example.com

If no matches are found, the DNS server will provide a result of notfound and the DNS query will fail.

Static Hostnames

Static hostnames are locally defined hostname-to-IP mappings located in the file /etc/hosts. Entries in the hosts file will have precedence over DNS by default. This means that if your system tries to resolve a hostname and it matches an entry in /etc/hosts, it will not attempt to look up the record in DNS. In some configurations, especially when Internet access is not required, servers that communicate with a limited number of resources can be conveniently set to use static hostnames instead of DNS.

The following is an example of a hosts file where a number of local servers have been identified by simple hostnames, aliases and their equivalent Fully Qualified Domain Names (FQDN's).

127.0.0.1	localhost
127.0.1.1	ubuntu-server
10.0.0.11	server1 vpn server1.example.com
10.0.0.12	server2 mail server2.example.com
10.0.0.13	server3 www server3.example.com
10.0.0.14	server4 file server4.example.com

	In the above example, notice that each of the servers have been given aliases in addition to their proper names and FQDN's. Server1 has been mapped to the name vpn, server2 is referred to as mail, server3 as www, and server4 as file.

Name Service Switch Configuration

The order in which your system selects a method of resolving hostnames to IP addresses is controlled by the Name Service Switch (NSS) configuration file /etc/nsswitch.conf. As mentioned in the previous section, typically static hostnames defined in the systems /etc/hosts file have precedence over names resolved from DNS. The following is an example of the line responsible for this order of hostname lookups in the file /etc/nsswitch.conf.

hosts:          files mdns4_minimal [NOTFOUND=return] dns mdns4

• files first tries to resolve static hostnames located in /etc/hosts.

• mdns4_minimal attempts to resolve the name using Multicast DNS.

• [NOTFOUND=return] means that any response of notfound by the preceeding mdns4_minimal process should be treated as authoritative and that the system should not try to continue hunting for an answer.

• dns represents a legacy unicast DNS query.

• mdns4 represents a Multicast DNS query.

To modify the order of the above mentioned name resolution methods, you can simply change the hosts: string to the value of your choosing. For example, if you prefer to use legacy Unicast DNS versus Multicast DNS, you can change the string in /etc/nsswitch.conf as shown below.

hosts:          files dns [NOTFOUND=return] mdns4_minimal mdns4

Bridging

Bridging multiple interfaces is a more advanced configuration, but is very useful in multiple scenarios. One scenario is setting up a bridge with multiple network interfaces, then using a firewall to filter traffic between two network segments. Another scenario is using bridge on a system with one interface to allow virtual machines direct access to the outside network. The following example covers the latter scenario.

Before configuring a bridge you will need to install the bridge-utils package. To install the package, in a terminal enter:

sudo apt-get install bridge-utils

Next, configure the bridge by editing /etc/network/interfaces:

auto lo
iface lo inet loopback

auto br0
iface br0 inet static
        address 192.168.0.10
        network 192.168.0.0
        netmask 255.255.255.0
        broadcast 192.168.0.255
        gateway 192.168.0.1
        bridge_ports eth0
        bridge_fd 9
        bridge_hello 2
        bridge_maxage 12
        bridge_stp off

	Enter the appropriate values for your physical interface and network.

Now restart networking to enable the bridge interface:

sudo /etc/init.d/networking restart

The new bridge interface should now be up and running. The brctl provides useful information about the state of the bridge, controls which interfaces are part of the bridge, etc. See man brctl for more information.

http://ubuntuforums.org/showthread.php?t=571188

Attachment: How To.pdf

Read More

Kumpulan Panduan Mikrotik

Enjoy It

Attachment: kumpulan ebook mikrotik bahasa Indonesia.zip

Read More

Program For Cyber Sport

If there are additional new software in this category, I will add the software. Thank's

Attachment: ViceVersa Pro 2.5 (copy soft).rar
Attachment: Billing6.9d.rar
Attachment: Pixelab XXcopy Pro 3.08.0.rar
Attachment: sandbox.rar
Attachment: Billing6.9cxeditbygwenyth.rar
Attachment: Disk Drive Administrator 3.6.rar
Attachment: PC.Security.Tweaker.v7.3.rar
Attachment: EDSafemode.zip
Attachment: windowsautologin.exe
Attachment: CaesarSoft CyberBilling v50vx.rar

Read More

Chown Command For Linux

chown

From Wikipedia, the free encyclopedia

Jump to: navigation, search

For the surname, see Chown (surname).

The chown command (abbreviation for change owner) is used on Unix-like systems to change the owner of a file. In most implementations, it can only be executed by the superuser. Unprivileged (regular) users who wish to change the group of a file that they own may use chgrp.

[edit] Usage examples

These examples illustrate typical syntax and use. Because chown modifies permissions, it usually requires root privilege to run.

 # chown root /var/run/httpd.pid 

• Change the owner of /var/run/httpd.pid to 'root' (the standard name for the Superuser).

 # chown rob:developers strace.log 

• Change the owner of strace.log to 'rob' and the group identifier to 'developers'.

 # chown nobody:nogroup /tmp /var/tmp 

• Change the owner of /tmp and /var/tmp to ‘nobody’ (not a good idea)
• Change the group of /tmp and /var/tmp to ‘nogroup’

 # chown :512 /home 

• Change the group identifier of /home to 512 (regardless of whether a group name is associated with the identifier 512 or not).

 # chown -R us base 

• Change the ownership of base to the user us and make it recursive (-R)

 # chown -R newuser:newgroup . 

• Change the ownership to newuser and group to newgroup for all of the files and directories in current directory, and all subdirectories (recursively).

Read More

Quick Setting Mikrotik RB750

Disini Disini saya akan menjelaskan bagaimana menggunakan RB750/RB750G pertama kali. Karena di RB ini tidak ada slot Serial Port, anda bisa meremote RB ini dengan winbox. Didalamnya sudah terdapat konfigurasi untuk port 1 untuk koneksi internet  yang anda bisa pakai atau  anda hapus Pertama menggunakan :

• Konek kabel internet/WAN ke port 1, dan kabel LAN port 2-5
• Set IP LAN komputer dengan otomatis (DHCP)
• Ip default router dari jaringan LAN 192.168.88.1 dengan username admin password kosong

Menyalakan power :

• Kabel langsung dari adaptor ke jack power atau,
• Menggunakan PoE (Power over Ethernet) pada port 1

Ethernet atau Port :

• Port 1 – 5 bisa menggunakan kabel cross/straight untuk koneksi dengan device jaringan lainnya. Dan port 1 bisa untuk PoE injector dengan volt 8.. 28 V DC
• Pada RB750G port 1-5 support gigabit ethernet

Reset RB750 :

• Tombol reset terdapat pada depan RB750
• Reset Konfigurasi.. Tahan tombol ini pada proses booting sampai lampu LED berkedip-kedip, lepas
• Install Ulang RB750 dengan netinstall.. Tahan tombol ini pada proses booting agak lama sampai lampu LED mati dan lepas

 

Download tutorial MT pdf  767kb
MikroTik RouterOS™ adalah sistem operasi dan yang dapat digunakan untuk menjadikan komputer menjadi router network yang handal, mencakup berbagai fitur lengkap untuk network dan wireless.

Langkahnya burn file ISO MikroTik RouterOS™ ke CD.

1. Install Mikrotik OS

- Siapkan PC, minimal Pentium I juga gak papa RAM 64,HD 500M atau pake flash memory 64

- Di server / PC kudu ada minimal 2 ethernet, 1 ke arah luar dan 1 lagi ke Network local

- Burn Source CD Mikrotik OS masukan ke CDROM

- Boot dari CDROM

- Ikuti petunjuk yang ada, gunakan syndrom next-next dan default

- Install paket2 utama, lebih baiknya semua packet dengan cara menandainya (mark)

- Setelah semua paket ditandai maka untuk menginstallnya tekan “I”

- Lama Install normalnya ga sampe 15menit, kalo lebih berarti gagal, ulangi ke step awal

- Setelah diinstall beres, PC restart akan muncul tampilan login

2. Setting Dasar Mikrotik

Langkah awal dari semua langkah konfigurasi mikrotik adalah setting ip. Hal ini bertujuan agar mikrotik bisa di remote dan dengan winbox dan memudahkan kita untuk melakukan berbagai macam konfigurasi

- Login sebaga admin degan default password ga usah diisi langsung enter. Gantilah dengan ip address anda dan interface yg akan digunakan untuk meremote sementara

Seting mikrotik ada 2 cara yaitu dengan TEXT dan Winbox.

Di sini akan saya terangkan seting mikrotik dengan Winbox.

Langkah setting Mikrotik dengan TEXT

Mari kita mulai dengan asumsi proses install sudah berhasil

1. Setelah install Mikrotik sudah OK, selanjutnya masukkan IP sembarang untuk remote.

Misal

ip address add address 192.168.1.254 netmask 255.255.255.0 interface ether2

Kemudian buka browser dengan alamat IP tadi, dan download Winbox

2. Buka Winbox yang telah di download tadi

3. Di tampilan Winbox, pada kolom Connect To masukkan no IP tadi (192.168.1.254) dengan

Login : admin password : kosong. Kemudian klik tombol Connect

4. Login ke Mikrotik Via Winbox berhasil

5. Klik IP —> ADDRESS

6. Ini adalah tampilan dari address

7. Kemudian masukkan IP public (dari ISP)

8. Ini daftar IP pada 2 ethernet

9. Setting Gateway, IP —> Routes

10. Masukkan IP GATEWAY (dari ISP)

11. Hasil ROUTING

12. Masukkan Primary DNS dan Secondary DNS (dari ISP)

Kemudian klik Apply dan OK

13. Setting MASQUERADE

14. Klik IP —> Firewall

15. Kemudian pilih NAT

16. Pada tab General

pada Chain pilih srcnat

pada Out. Interface pilih ether1

pada tab Action pilih masquerade

Kemudian klik Apply dan OK

Powered by Microtic

Sumber : http://go24u.blogspot.com/2010/03/quick-setting-mikrotik-rb750.html

Note :

- Disini saya cantumkan juga beberapa file tutorial mikrotik dan terus saya update dari berbagai situs bila ada file bagus untuk dibaca

Attachment: 205071118_MembuatRouterMenggunakanMikrotikRouterOS.pdf
Attachment: ropik-mikrotik.pdf
Attachment: mikrotik simple.rar

Read More

Cara Blokir Website di Mikrotik

berikut dibawah ini commandnya

/ip fi fi
add chain=forward action=reject reject-with=icmp-net-prohibited content=kompas.com

command diatas akan memblokir pengguna membuka website kompas.com

 

Sumber : http://farounet.wordpress.com/2011/05/06/cara-blokir-website-di-mikrotik-rb750/

Note :

ampuh banget nich

Read More

Chkdsk (Check Disk), ChkNTFS, and Autochk (Auto Check)

*** and the infamous but mysterious, "dirty bit"

see also: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/chkdsk.mspx?mfr=true

             Microsoft Description of autochk, chkdsk, and chkntfs   or the Microsoft ChkNTFS Article

YOU MUST BE USING THE ADMINISTRATOR USER ACCOUNT OR HAVE ADMINISTRATOR PRIVILEGES TO RUN CHKDSK !!

Chkdsk checks the integrity of your hard drive.  The same as with Win98, if you run Chkdsk from the command line (START/run . . . chkdsk).  Chkdsk corrects disk errors only if you specify the /f switch.

Chkdsk is not the same as Scandisk, although functionally they do the same thing !!!  Scandisk runs within WinXp - while Chkdsk runs in a DOS box, or it can run from the recovery Console.

Chkdsk vs Scandisk

For those of you who can still remember "scandisk" - Windows XP doesn't have ScanDisk !!  However, it does have CHKDSK, which is similar.  Unfortunately, the interface of Chkdsk is very limited - you only see a progress bar and not what is going on until the end, where you receive a limited report with the Command Prompt Chkdsk - and no report with the Windows-based Chkdsk..
 

Chkdsk vs Autochk

• Chkdsk runs in Windows as a small box or in a DOS box within Windows, or in the Recovery console
• Autochk runs in the blue boot screen and does the same thing that chkdsk does. 

Autochk does essentially the same thing as Chkdsk but will only run during bootup (but during bootup it will only run if the system detects a cold boot or power off).

NOTE:  the boot partition will always be locked.

• you can run Chkdsk to simply "check" the partition
• you cannot run Chkdsk "directly" with "fix errors" enabled.  However, if you try to run it with "fix errors" on the boot partition, the system will give you the option to run Chkdsk upon the next reboot and then it will run and fix any errors.  You can run Chkdsk with "fix errors" enabled for any non-bootable partition and it will run without having to reboot !!

Controlling Autochk using the ChkNTFS command

Forcing Autochk to run and check a Drive upon Reboot

chkntfs /c drive:   

Example - suppose you want to check your E drive.  You run the following command and then reboot:

chkntfs /c e:

• BootExecute registry entry before chkntfs command:     autocheck autochk *
• BootExecute registry entry  after  chkntfs  command:     autocheck autochk /m \??\E: autocheck autochk *
  
  (more details on the "BootExecute" registry entry are listed below)

Stopping Autochk from running upon Reboot on a Drive

chkntfs /x drive:

Example - suppose you do not want chkdsk to run on your e drive when you reboot

chkntfs /x e:

• BootExecute registry entry before chkntfs command:     autocheck autochk *
• BootExecute registry entry  after  chkntfs  command:     autocheck autochk /k:E *

 

The Dirty bit vs the Registy "Autochk" entry

When you freeze up and have to do a hard reset (cold reboot) - WinXP flags the all hard drives with open files as dirty.  The "Dirty Bit" is set by the file system itself only if it detects a problem.

If the administrator schedules the command to run the next time the system restarts, Chkdsk does not set the "Dirty Bit" on an in-use volume in order to check the volume at the next boot. Instead, it sets a registry entry to tell Autochk to run against that volume:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\BootExecute   with value = autocheck autochk *

Additional entries that can be found in BootExecute are:
 

"BootExecute" Registry value	Function
/P \??\Volume:	Schedules an unconditional Chkdsk against the volume.
/p \??\VOLUME{GUID}	Schedules an unconditional Chkdsk against a volume mount point.
/k:Volume *	Excludes Chkdsk from running against the volume.
/m \??\Volume:	Tells Autochk to look only at the dirty bit on the volume, and if set, run Chkdsk.

 

Sample command	Resulting registry entry
Chkdsk C: /F	Autocheck autochk /p \??\C:
Chkdsk C:\mountpoint /F	Autocheck autochk /p \??\VOLUME{GUID}
Chkntfs D: E: /X	Autocheck autochk /k:D /k:E *
Chkntfs G: /C	Autocheck autochk /m \??\G:

 

Chkdsk within Windows:
NOTE:  Scandisk is not the same as Chkdsk, although functionally they do the same thing !!!  Chkdsk on your system drive (the drive with Windows on it) will only run during bootup, and will only run if the system detects a cold boot or power off.  However, you can run chkdsk and even repair the other drives on your system, by dismounting the drive.

Chkdsk /X: A new command parameter that runs Chkdsk /F and forces a volume dismount to close open file handles on non-system volumes so it can be checked immediately. This eliminates the need of a potential reboot in order to perform the Chkdsk and repair the volume.  

Running chkdsk on any non-system Drive and Fix Errors

Method 1:

1. close all running programs
2. start a DOS box (Start/Run . . . cmd)
3. chkdsk /x n:     -where n is the letter of the drive you wish to run chkdsk on (n cannot be your system drive).  This will dismount the drive and then run chkdsk

Method 2: 

1. close all running programs
2. double-click My Computer
3. right-click on the drive you want to run scandisk on
4. click the Tools tab and click "Check Now" next to "Error Checking"
5. to fix errors, check the "Automatically fix file system errors" box - and
   to run a surface scan, check the "Scan for and attempt recovery of bad sectors" box

Running Chkdsk on Your System Drive

1. close all running programs
2. double-click My Computer
3. right-click on the drive you want to run scandisk on
4. click the Tools tab and click "Check Now" next to "Error Checking"
5. to fix errors, check the "Automatically fix file system errors" box - and
   to run a surface scan, check the "Scan for and attempt recovery of bad sectors" box
6. reboot and Chkdsk will run during the boot process before Windows starts
   

The ChkNTFS Command

You would think that this only works on NTFS drives - but it works on ALL drives.  Displays or specifies whether automatic system checking is scheduled to be run on a FAT, FAT32, or NTFS volume when the computer is started.

Syntax

chkntfs volume: [...]

chkntfs [/d]

chkntfs [/t[:time]]

chkntfs [/x volume: [...]]

chkntfs [/c volume: [...]]

Parameters

volume: [...]

Required. Specifies the drive letter (followed by a colon), mount point, or volume name. Displays a message that identifies the file system of the specified volume. If automatic file checking is scheduled to be run, this parameter displays a message indicating whether the volume has been corrupted, which requires you to run chkdsk.

/d

Restores all chkntfs default settings, except the countdown time for automatic file checking. Default behavior is to check all volumes when the computer is started.

/t[:time]

Changes the Autochk.exe initiation countdown time to the specified amount of time entered in seconds. If you do not specify :time, /t displays the current countdown time.

/x volume: [...] 

Excludes the specified volume from being checked when the computer starts, even if the volume is marked as requiring chkdsk.

/c volume: [...]

Schedules the specified volume to be checked when the computer starts.

/?

Displays help at the command prompt.

Remarks

• To run chkntfs, you must be a member of the Administrators group.
• Although you can set the Autochk.exe initiation countdown time to zero, you cannot cancel a potentially time-consuming automatic file check if you set it to zero.

Examples

To display the Autochk.exe initiation countdown time, type:

chkntfs /t

When changing the Autochk.exe initiation countdown time, type the time in seconds. For example, to change the countdown time to 30 seconds, type:

chkntfs /t:30

The /x command-line option is not accumulative. If you type it more than once, the most recent entry overrides the previous entry. To exclude multiple volumes, list them all in one command. For example, to exclude both the E: and F: volumes, type:

chkntfs /x e: f:

To exclude the F: volume only, type:

chkntfs /x e:

chkntfs /x f:

The /c command-line option is accumulative. If you want to check the specified volume only, reset the defaults to clear any previous commands, exclude all volumes from being checked, and then schedule automatic file checking on the desired volume.

For example, to schedule automatic file checking on the D: volume only, type:

chkntfs /d

chkntfs /x c: d: e:

chkntfs /c d:

 

The mysterious "Dirty Bit"

No one knows where the dirty bit is located, and Microsoft won't say !!  Using chkntfs to force autochk to run upon reboot merely sets an entry in the registry - it does NOT set the dirty bit. 

The command, FSUTIL (see https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/fsutil.mspx?mfr=true) will allow you to do two things to any NTFS drive (it will not work on FAT32 drives !!):

• query the dirty bit - see if it is set or not  - Example:        Start/Run . . . cmd
                                                                                       fsutil dirty query c: )
• set the dirty bit   - Example:  Start/Run  .  .  .  cmd
                                             fsutil dirty set c:

NOTE:  fsutil will NOT reset the dirty bit - the only one way to do this is to either run chkdsk within Windows, or let Autochk run upon reboot

Diskeeper will NOT run with the dirty bit set !!  You will get the following message:

What if the Dirty Bit won't go away ??

More than a few people have encountered this:

1. a drive partition has the dirty bit set

2. so when they reboot, Windows insists on running Autochk to check a drive - it checks the drive and all is well.  Just running that check is supposed to clear the dirty bit

3. but the next time they reboot, again Windows checks the drive !!  Again, all is well and the drive reports no errors

4. they get into Windows and run "fsutil dirty query driver_letter:" and they are told that the dirty bit is set

5. they try booting with a WinXP CD and go into "Repair" mode to run chkdsk /r  (supposed to do a thorough check and also check the surface) - but it does not help

6. and so on  .  .  .   and so on  .  .  .

There is no apparent way for them to clear the dirty bit.  Microsoft has never released the location of the dirty bit, so they are stuck.  Here is the only way to fix the problem:

Method 1) if the drive in question is not your boot drive goto Start/Run . . . msconfig, click the "Starup" tab, and uncheck all items.  Then reboot, hit CTRL-Alt-Delete to get into Windows Task Manager, and shut down as many tasks as possible.  The point here is to free up your drive.  Then Start/Run . . . cmd

chkdsk /x /f drive:     

If it completes successfully this will usually remove the dirty bit.  To check it, enter the following command:

fsutil dirty query drive:

reboot to test

Method 2)  run Kelly's reg edits to first Disable autochk from running upon reboot, then reboot, and run this reg file to or re-enable disk checking upon reboot - this will refresh the entries in your registry to make sure thewy are correct

Method 2) run Partition Magic - try resizing the C: partition a little smaller, create another partition
from the unallocated space, then delete this partition and reclaim the space
back into C:

Method 3)  if all else fails - this WILL WORK !!   move all the files off the drive, reformat the drive, and then move the files back
 

Autochk bootup routine and the "dirty bit" (also called the "chkdsk flag")

When the system is shut down improperly or stops responding, Autochk runs against any volumes that are marked as being "dirty". At least, I know this is done with NTFS, and I think it is also done with FAT32 since my drives are FAT32 and the system does run Autochk whenever I run into problems and have to do a cold boot.  Autochk will not initiate a check of any partitions if none of them are flagged !!  Autochk is set to run during bootup because of the registry entry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager  .  .  .  BootExecute
The BootExecute entry tells Windows what to run upon bootup.  By default, its value is  "autocheck autochk *"  -  this tells Windows to run Autochk on any drive whose dirty bit is set

You can cancel Autochk within the first few seconds by hitting an key.  However, each time you stop chkdsk, the system "remembers" that it still needs to run Autochk due to the flagged partition and will try to run it the next time you reboot.  This continues forever, each time you reboot, until you allow Autochk to run and to complete.

Stopping Autochk

It is a pain that even when you suspect your drives are fine - you still must allow Autochk to continue, since even if you hit a key to skip it, it will continue to try to run upon every reboot until you actually allow it to run.  As we mentioned before - there are workarounds:

• Run chkntfs with the /x option - this is the best workaround.  You can exclude the drive from being checked by using the chkntfs /x command (although it does not reset the dirty bit).  You can use this for one or more drives, as follows:

1. Start/run . . . cmd
2. chkntfs /x n: m: etc.      -where n, m, etc are the letters of the drive/s you want to exclude from being checked upon reboot

• run chkdsk /f within Windows to reset the dirty bit - but this is even more hassle than letting Autochk run and only works on non-system drives

Chkdsk Command-Line Options

  -  they differ depending on whether you are at a command prompt (in a DOS box in Windows), or in the Recover Console !!

Chkdsk from the Command Prompt

Syntax
chkdsk [volume:][[Path] FileName] [/f] [/v] [/r] [/x] [/i] [/c] [/l[:size]]

Parameters
volume: Specifies the drive letter (followed by a colon), mount point, or volume name.

[Path] FileName Specifies the location and name of a file or set of files that you want chkdsk to check for fragmentation. You can use wildcard characters (that is, * and ?) to specify multiple files.

/f     Fixes errors on the disk. The disk must be locked. If chkdsk cannot lock the drive, a message appears that asks you if you want to check the drive the next time you restart the computer.

/v     Displays the name of each file in every directory as the disk is checked.

/r     Locates bad sectors and recovers readable information. The disk must be locked.

/x     Use with NTFS only. Forces the volume to dismount first, if necessary. All open handles to the drive are invalidated. /x also includes the functionality of /f.

/i     Use with NTFS only. Performs a less vigorous check of index entries, reducing the amount of time needed to run chkdsk.

/c     Use with NTFS only. Skips the checking of cycles within the folder structure, reducing the amount of time needed to run chkdsk.

/l[:size]     Use with NTFS only. Changes the log file size to the size you type. If you omit the size parameter, /l displays the current size.

/?    Displays help at the command prompt.


Chkdsk from the Recovery Console

chkdsk [drive:] [/p] [/r]

- Used without parameters, chkdsk displays the status of the disk in the current drive.
- to "fix" the drive, you MUST use the /r option !!!  The /p option does not make changes !!

drive:     Specifies the drive that you want chkdsk to check.

/p     Performs an exhaustive check even if the drive is not marked for chkdsk to run. This parameter does not make any changes to the drive.

/r    Locates bad sectors and recovers readable information. Implies /p.

The chkdsk command requires the file Autochk.exe. If it cannot find it in the startup directory (\%systemroot%\System32, by default), it will attempt to locate it on the Windows Installation CD. If you have a multiboot computer, be sure you are issuing this command from the drive containing Windows.

Sumber : http://www.infocellar.com/winxp/chkdsk-and-autochk.htm

Note :

- Ma'af, sebagian postingan ini berbahasa Inggris. Mohon anda yang belum bisa berbahasa inggris untuk belajar bahasa Inggris.

Read More

How to make a computer faster: 6 ways to speed up your PC

By following a few simple guidelines, you can maintain your computer, help increase your PC speed, and help keep it running smoothly. This article discusses how to use the tools available in Windows 7, Windows Vista, and to help make your computer faster, maintain your computer efficiently, and help safeguard your privacy when you're online.

Note: Some of the tools mentioned in this article require you to be logged on as an administrator. If you aren't logged on as an administrator, you can only change settings that apply to your user account.

1. Remove spyware, and help protect your computer from viruses

Spyware collects personal information without letting you know and without asking for permission. From the websites you visit to user names and passwords, spyware can put you and your confidential information at risk. In addition to privacy concerns, spyware can hamper your computer's performance. To combat spyware, you might want to consider using the PC safety scan from Windows Live OneCare. This scan is a free service that helps check for and remove viruses.

Download Microsoft Security Essentials for free to help guard your system in the future from viruses, spyware, adware, and other malicious software (also known as malware). Microsoft Security Essentials acts as a spyware removal tool and includes automatic updates to help keep your system protected from emerging threatsThe Microsoft Windows Malicious Software Removal Tool

is another utility that checks computers running Windows 7, Windows Vista, Windows XP, Windows 2000, and Windows Server 2003 for infections by specific, prevalent malicious software, including Blaster, Sasser, and Mydoom, and helps remove any infection found.

---

2. Free up disk space

The Disk Cleanup tool helps you to free up space on your hard disk to improve the performance of your computer. The tool identifies files that you can safely delete and then enables you to choose whether you want to delete some or all of the identified files.

Use Disk Cleanup to:

• Remove temporary Internet files.

• Delete downloaded program files, such as Microsoft ActiveX controls and Java applets.

• Empty the Recycle Bin.

• Remove Windows temporary files, such as error reports.

• Delete optional Windows components that you don't use.

• Delete installed programs that you no longer use.

• Remove unused restore points and shadow copies from System Restore.

Tip: Typically, temporary Internet files take the most amount of space because the browser caches each page you visit for faster access later.

To use Disk Cleanup:

Windows 7 users

1. Click Start, click All Programs, click Accessories, click System Tools, and then click Disk Cleanup. If several drives are available, you might be prompted to specify which drive you want to clean.

2. When Disk Cleanup has calculated how much space you can free up, in the Disk Cleanup for dialog box, scroll through the content of the Files to delete list.
   
   

   

3. Clear the check boxes for files that you don't want to delete, and then click OK.

   • For more options, such as cleaning up System Restore and Shadow copy files, under Description, click Clean up system files, and then click the More Options tab.

4. When prompted to confirm that you want to delete the specified files, click Yes.

After a few minutes, the process completes and the Disk Cleanup dialog box closes, leaving your computer cleaner, performing better, and potentially increasing your PC speed.

Windows Vista users

1. In the Start menu, click All Programs, click Accessories, click System Tools, and then click Disk Cleanup.

2. In the Disk Cleanup Options dialog box, choose whether you want to clean up your own files only or all of the files on the computer.

3. If the Disk Cleanup: Drive Selection dialog box appears, select the hard disk drive that you want to clean up, and then click OK.

4. Click the Disk Cleanup tab, and then select the check boxes for the files you want to delete.

5. When you finish selecting the files you want to delete, click OK, and then, to confirm the operation, click Delete files. Disk Cleanup then removes all unnecessary files from your computer. This may take a few minutes.

The More Options tab is available when you choose to clean files from all users on the computer.

Windows XP users

1. Click Start, point to All Programs, point to Accessories, point to System Tools, and then click Disk Cleanup. If several drives are available, you might be prompted to specify which drive you want to clean.
   
   

   

2. In the Disk Cleanup for dialog box, scroll through the content of the Files to delete list.
   
   

   

3. Clear the check boxes for files that you don't want to delete, and then click OK.

4. When prompted to confirm that you want to delete the specified files, click Yes.

After a few minutes, the process completes and the Disk Cleanup dialog box closes, leaving your computer cleaner and potentially performing better.

---

3. Speed up access to data

Disk fragmentation slows the overall performance of your system. When files are fragmented, the computer must search the hard disk as a file is opened (to piece it back together). The response time can be significantly longer.

Disk Defragmenter (sometimes shortened to Defrag by users) is a Windows utility that consolidates fragmented files and folders on your computer's hard disk so that each occupies a single space on the disk. With your files stored neatly end to end, without fragmentation, reading and writing to the disk speeds up.

When to run Disk Defragmenter
In addition to running Disk Defragmenter at regular intervals (weekly is optimal), there are other times you should run it, too, such as when:

• You add a large number of files.

• Your free disk space totals 15 percent or less.

• You install new programs or a new version of the Windows operating system.

To use Disk Defragmenter:

Windows 7 users

1. Click Start, click All Programs, click Accessories, click System Tools, and then click Disk Defragmenter.
   
   

   

2. In the Disk Defragmenter dialog box, click the drives that you want to defragment, and then click the Analyze disk button. After the disk is analyzed, a dialog box appears, letting you know whether you should defragment the analyzed drives.
   
   Tip: You should analyze a volume before defragmenting it to get an estimate of how long the defragmentation process will take.

3. To defragment the selected drive or drives, click the Defragment disk button. In the Current status area, under the Progress column, you can monitor the process as it happens. After the defragmentation is complete, Disk Defragmenter displays the results.

4. To display detailed information about the defragmented disk or partition, click View Report.

5. To close the View Report dialog box, click Close.

6. You can also schedule the Disk Defragmenter to run automatically. (Your computer might even be set up this way by default.) Under Schedule, it reads Scheduled defragmentation is turned on and then displays the time of day and frequency of defragmentation. If you want to turn off automatic defragmentation or to change the time or frequency, click Configure schedule (or Turn on Schedule, if it is not currently configured to run automatically). Change the settings, and then click OK.

7. To close the Disk Defragmenter utility, on the title bar of the window, click the Close button.

Windows Vista users

1. Open Disk Defragmenter: Click the Start button, click All Programs, click Accessories, click System Tools, and then click Disk Defragmenter. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.

2. In the Disk Defragmenter dialog box, click the drives that you want to defragment and then click the Analyze disk button. After the disk is analyzed, a dialog box appears letting you know whether you should defragment the analyzed drives.
   
   Tip: You should analyze a volume before defragmenting it to get an estimate of how long the defragmentation process will take.

3. To defragment the selected drive or drives, click the Defragment disk button. In the Current status area, under the Progress column, you can monitor the process as it happens. After the defragmentation is complete, Disk Defragmenter displays the results.

4. To display detailed information about the defragmented disk or partition, click View Report.

5. To close the View Report dialog box, click Close.

6. You can also schedule the Disk Defragmenter to run automatically. (Your computer might be set up this way by default.) Click Modify schedule....

7. In the Disk Defragmenter: Modify Schedule dialog box, choose how often, which day, and at what time of day you want defragmentation to occur, and then click OK.

8. Click OK again.

Windows XP users

1. Click Start, point to All Programs, point to Accessories, point to System Tools, and then click Disk Defragmenter.
   
   

   

2. In the Disk Defragmenter dialog box, click the drives that you want to defragment and then click the Analyze button. After the disk is analyzed, a dialog box appears, letting you know whether you should defragment the analyzed drives.
   
   Tip: You should analyze a volume before defragmenting it to get an estimate of how long the defragmentation process will take.

3. To defragment the selected drive or drives, click the Defragment button. Note: In Windows Vista, there is no graphical user interface to demonstrate the progress—but your hard drive is still being defragmented.
   
   After the defragmentation is complete, Disk Defragmenter displays the results.

4. To display detailed information about the defragmented disk or partition, click View Report.

5. To close the View Report dialog box, click Close.

6. To close the Disk Defragmenter utility, on the title bar of the window, click the Close button.

Running Disk Cleanup and Disk Defragmenter on a regular basis is a proven way to help keep your computer running quickly and efficiently. If you'd like to learn how to schedule these tools and others to run automatically, please read Speed up your PC: Automate your computer maintenance schedule.

---

4. Detect and repair disk errors

In addition to running Disk Cleanup and Disk Defragmenter to optimize the performance of your computer, you can check the integrity of the files stored on your hard disk by running the Error Checking utility.

As you use your hard drive, it can develop bad sectors. Bad sectors slow down hard disk performance and sometimes make data writing (such as file saving) difficult or even impossible. The Error Checking utility scans the hard drive for bad sectors and scans for file system errors to see whether certain files or folders are misplaced.

If you use your computer daily, you should run this utility once a week to help prevent data loss.

Run the Error Checking utility:

1. Close all open files.

2. Click Start, and then click Computer.

3. In the Computer window (My Computer in Windows XP), right-click the hard disk you want to search for bad sectors, and then click Properties.

4. In the Properties dialog box, click the Tools tab.

5. Click the Check Now button.

6. In the Check Disk dialog box (called Error-checking in Windows 7), select the Scan for and attempt recovery of bad sectors check box, and then click Start.
   
   

   

7. If bad sectors are found, choose to fix them.

Tip: Only select the "Automatically fix file system errors" check box if you think that your disk contains bad sectors.

---

5. Learn about ReadyBoost

If you're using Windows 7 or Windows Vista, you can use ReadyBoost to speed up your system. A new concept in adding memory to a system, it allows you to use non-volatile flash memory—like a USB flash drive or a memory card—to improve performance without having to add additional memory.

• Learn more about ReadyBoost in Windows 7.

• Learn more about ReadyBoost in Windows Vista.

---

6.  Upgrade  to  Windows 7

If you try all the previous remedies and your computer still isn't as fast as you would like it to be, you may want to consider updating to Windows 7.

• Find out if your computer can run Windows 7 using the Upgrade Advisor.

• Compare Window 7 editions.

• Read a third-party review of Windows 7 by David Pogue of The New York Times.

If the Windows 7 Upgrade Advisor determines that your computer can't run Windows 7 and you still have the need for speed, it might be time for a new computer. There are some great deals on new computers right now:

• Shop for new desktop computers.

• Shop for new laptop computers.

• Shop for netbooks

Sumber : http://www.microsoft.com/atwork/maintenance/speed.aspx

Note :

Pada saran berikut ada saran yang saya kurang setuju, yaitu

6.  Upgrade  to  Windows 7

Read More