Basic Mikrotik Router Through ADSL Speedy

Skenario dibawah ini adalah di asumsikan Koneksi ke speedy melalui Modem, apabila koneksi ke speedy melalui Mikrotik PC (Setting pppoe di Mikrotik Routernya, dan modem di fungsikan sebagai bridge...) akan di ceritakn dilain waktu, lebih memudahkan penyetingan lewat WINBOX bawaan router.

1. Penggambaran konfigurasi koneksi ADSL
modem —Mikrotik—-Switch —– Client
|
Client

a. Modem IP –>> 192.168.1.1

b. Mikrotik menggunakan 2 LAN card - Ether1 —->> 192.168.1.2

- Ether2 —->> 192.168.0.1

c. Switch — Client ip 192.168.0.1-253

2. Konfigurasi Mikrotik PC

a. tambahkan ip address ke LAN card 1

/ip address add interface=ether1 address = 192.168.1.2 netmask= 255.255.255.0

b. tambahkan ip address ke LAN card 2

/ip address add interface=ether2 address = 192.168.0.1 netmask= 255.255.255.0

>>>>>>>

akan sama pabila anda mengetikan seperti dibawah ini

/ip address add address=192.168.1.2/24 interface=ether1

/ip address add address=192.168.0.1/24 interface=ether2

<<<<<<<<

c. Untuk melihat hasil tambahan tadi IP address tadi

/interface print

d. Memberi nama peralatan ( interface)

/interface set 0 name=”WAN” –>> Untuk ke Modem

/interface set 1 name=”LAN” –>> Untuk Local

e. Setting routing untuk jaringan ( modem )

/ip route add gateway=192.168.1.1

f. Setting dns server ISP (DNS Telkom)

/ip dns set primary-dns=202.134.1.10 allow-remote-requests=yes
/ip dns set secondary-dns=202.134.0.155 allow-remote-requests=yes

g. Setting NAT di router untuk sharing BW di LAN nya

/ip firewall nat add chain=srcnat action=masquerade out-interface=WAN

HOw To Hide My Admin Account

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Winlogon\SpecialAccounts\UserList

Under this key you simply create a new DWORD value - the name matches the users name exactly, and the value is one of the following (Decimal format)

0 - Hides the user just from the welcome screen
1 - The user is shown

Join Samba in the SUBNET network on the Same Class

Here is the situation that I Just installed new Wireless Router in The Office, the Router need to create a subnet to join in the same class network in the existing network.

I'm Going to share my SAMBA across subnets. Both Windows and Linux clients will be able to use this server. Our example network has three segments, as this elegant ASCII network diagram shows:

                    router
                   |
--------------------switch----------------------
|                     |                        |
192.168.1.0/24   192.168.2.0/24    192.168.3.0/24
lan1                 lan2                   lan3

For ease of discussion, we'll call them lan1, lan2, and lan3. Our Samba server sits on lan1, with an address of 192.168.1.10. lan2 and lan3 contain a motley assortment of Windows and Linux clients. In this example there is no domain controller, but only a peer network. We'll get to Windows-type domains in a moment.

Your Windows clients need three things to be able to use the Samba server:

• They must all be in the same workgroup (in part 1 it's group1)
• They must all be configured to support NetBIOS over TCP
• They need the address of your WINS server

You can save a step by delivering the WINS address via DHCP. Windows 2000, XP, and Vista should have NetBIOS-over-TCP enabled by default, but it never hurts to check. It can be disabled, and in Active Directory domains that do not have antique, unsafe Windows 9x/ME clients it is often turned off.

Then the Samba server must be the WINS (Windows Internetworking Name) server and domain master browser. You must have one, and one only WINS server per workgroup to enable cross-subnet Samba browsing. WINS is the magic ingredient that makes it all work. WINS performs NetBIOS name resolution, because ordinary DNS does not include the necessary NetBIOS extensions. NetBIOS-based networking uses UDP broadcasts; since broadcast traffic cannot cross routers, your Samba WINS server encapsulates NetBIOS over TCP/IP. The domain master browser controls the browse lists; it has nothing to do with Active Directory or NT domains.

at the the smb.conf and add these lines to the [global] section:

   domain master = yes
preferred master = yes
local master = yes
wins support = yes
wins proxy = yes
os level = 65

Test and restart Samba just like we did in Part 1. Once your Windows clients are correctly configured, they should all be able to browse the file shares on your Samba server and use your shared printers. Figure 1 shows what an example cross-subnet workgroup looks like on Windows Vista. Xena is the Samba server on lan1, Freya and Uberpc are on lan2, and Newpad is on lan3.

Dont Forget in your router to add a WINS Server IP refer to SAMBA Machine

Set Your Wireless Channels

A. For best performance, you should choose a channel at least 5 channels from your neighbors' networks.

Although 802.11b and 802.11g devices are designed to share the airwaves with neighboring networks, it is best to find a clear channel for several reasons, chief among these:

1. When your neighbors' networks are busy, there is less available bandwidth on those frequencies for your data, reducing your performance

2. Your Access Point (AP) and wireless devices may not hear your neighbor's weaker wireless signals, causing degraded performance due to collisions

3. Your neighbor's networks may not be entirely 802.11b or 802.11g compliant. Some "advanced" technologies are known to interfere with 802.11-compliant systems instead of sharing the airwaves with them.

In order to find a completely clear channel, you need to choose a channel that is 5 or more channel numbers away from your neighbors. This is not always possible, particularly in heavily populated areas. So do your best.

You need to understand that the wireless channels translate to a radio frequency. Channel 6, for example, is 2.437 GHz (or 2437 MHz). Each channel up or down is 5 MHz away. However, and this is key, Wi-Fi signals are 20 MHz wide! So when you set your Wi-Fi device to channel 6, you actually are using the frequencies of channels 5, 6, 7, and half of 4 and 8.

                    -10 MHz   2437 MHz  +10 MHz
---------01---02---03---04---05---06---07---08---09---10---11---------
                        ~~~~~CHANNEL 06~~~~~

So consider the situation below when 3 wireless networks are on 3 different, but adjacent channels, 5, 6, and 7. They may be different channels, but they are using much of the same spectrum and, as a result, they will contend with each other.

---------01---02---03---04---05---06---07---08---09---10---11---------
                   ~~~~~CHANNEL 05~~~~~
                        ~~~~~CHANNEL 06~~~~~
                             ~~~~~CHANNEL 07~~~~~

This is why it is recommended to try to be at least 5 channels (25 MHz) away from your neighboring networks. By doing so, you avoid overlapping the frequency spectrum that their networks use. By moving the network 5 channels away (6 minus 5 equals 1, or 6 plus 5 equals 11), you avoid any overlap. As follows:

---------01---02---03---04---05---06---07---08---09---10---11---------
~~~~~CHANNEL 01~~~~~
                        ~~~~~CHANNEL 06~~~~~
                                                 ~~~~~CHANNEL 11~~~~~