Tampilkan postingan dengan label network. Tampilkan semua postingan
Tampilkan postingan dengan label network. Tampilkan semua postingan

Jumat, 16 Juli 2010

Ethernet 10/100/1000Base-T and 100Base-T4 Crossover









Name NIC1 Color NIC2 Name
TX+ (BI_DA+) 1 White/Orange 3 RX+ (BI_DB+)
TX- (BI_DA-) 2 Orange 6 RX- (BI_DB-)
RX+ (BI_DB+) 3 White/Green 1 TX+ (BI_DA+)
- (BI_DC+) 4 Blue 7 - (BI_DD+)
- (BI_DC-) 5 White/Blue 8 - (BI_DD-)
RX- (BI_DB-) 6 Green 2 TX- (BI_DA-)
- (BI_DD+) 7 White/Brown 4 - (BI_DC+)
- (BI_DD-) 8 Brown 5 - (BI_DC-)

Kamis, 01 April 2010

Setting linksys WAG160N

1.Buka browser ………… 192.168.1.1
2.Username : admin, password = admin
3.Set Up….Basic Set up
4.pilih Encapsulation : RFC 2516 PPPoE
5.Multiplexing : LLC
6.QoS Type : UBR
7.Autodetect: Disable
8.Virtual Circuit : VPI : 0, VCI : 35
9.DSL Modulation : Multimode
10.Usernamae : ………@telkom.net
11.Password : isikan password dari speedy
12.Keep Alive – Redial Period: 30 seconds
13.Host Name : Speedy
14.Domain Name : telkom.net
15.MTU : Manual
16.Size : 1492
17.Local IP Address : 192.168.1.1
18.Subnet MAsk : 255.255.255.0
19.Save Setting

Sabtu, 27 Maret 2010

Share Folder Tanpa Password Dengan Samba ….

Samba, sebuah tool sakti untuk berbagi file dengan komputer lain. Dengan samba kita dapat berbagi bahkan dengan Operating System yang berbeda. Seperti windows dengan linux. Defaultnya linux tidak bisa mengakses folder share milik windows, demikian sebaliknya. Untuk itu digunakanlah samba. Dengan samba dari linux kita bisa mengakses folder share milik windows, sebaliknya dengan samba pula folder share di linux bisa diakses dari windows.

Samba diinstall di linux, dalam hal ini penulis menggunakan distro ubuntu, untuk linux yang lain caranya menyesuaikan. Supaya linux dapat mengakses folder share milik windows cukup dengan menginstall sambanya saja. Otomatis linux akan dapat membaca folder share windows. Sedangkan supaya windows dapat mengakses folder share milik linux maka samba perlu dikonfigurasi terlebih dahulu. Caranya adalah sebagai berikut.

Langkah pertama adalah dengan menginstall samba terlebih dahulu.

sudo apt-get install samba


Setelah itu baru samba-nya dikonfigurasi. Pengkonfigurasian samba dilakukan pada file /etc/samba/smb.conf. Langkah selanjutnya sebagai berikut :

1.Pertama ktia buka file konfigurasi sambanya
sudo gedit /etc/samba/smb.conf
2.Setelah itu akan terbuka sebuah teks editor berisi aturan-aturan pengkonfigurasian samba. Kemudian cari kata security = user. Setelah ketemu ganti dengan kata berikut
security = share
Jangan lupa untuk menghilangkan tanda titik koma (;) di depan kata security tersebut
3.Hilangkan juga tanda titik koma (;) pada bagian guest account = nobody
4.Kemudian pada bagian akhir kita berikan setting untuk folder yang akan kita share
[nama folder share]
writable = no
path = /path/nama/directory
public = yes
guest ok = yes
guest only = yes
guest account =nobody
browsable = yes
5.Setelah itu restart sambanya
/etc/init.d/samba restart
Setelah konfigurasi berjalan sempurna, folder share milik linux sudah bisa terbaca dari windows. Untuk konfigurasi lebih lanjut dapat diutak-atik sendiri …….

Setting UP SAMBA

What is SAMBA
Samba is an implementation of the SMB/CIFS protocol for Unix systems, providing support for cross-platform file and printer sharing with Microsoft Windows, OS X, and other Unix systems.
Samba can be used to:
•Act as a server for SMB clients: share folders and printers, including PDF pseudo-printers so all the computers in your network may write PDF files •Act as a domain controller in a Windows network (authenticating users, etc.) •Do some more complex things, such as using a Windows domain controller to authenticate the users of a Linux/UNIX machine Samba is freely available under the GNU General Public License. More information be found at http://www.samba.org.

Back to top
Client Access - Browsing SMB shares
The samba package is a meta-package intended to be installed on file and printer sharing servers. Clients do not need this meta-package (you are acting as a client if you need to access files on another computer). For example, installing samba is not necessary if you only need your Ubuntu system to do any of the following:
•Access shared folders, drives and printers on a Windows computer (that is, act as a client with Windows servers). To do this, you only need the smbfs plugin. See MountWindowsSharesPermanently for more information.
•Have your Windows computer use (via a network) a printer that is attached to a Linux computer. CUPS can be configured to make the printer accessible to the network. •Share directories between two Linux computers. You can use NFS or setup an SSH server on one computer and access it from other computers using an scp or sftp client, or Places -> Connect to Server... and choose "SSH" as the service type.

Ubuntu Clients
Ubuntu and Gnome make it easy to access files on a Windows network share. Open the Places Menu, then click on Network. You will see a Windows network icon. Double-click to open it. The next window shows all the domains/workgroups found on your network. Inside each domain/workgroup you will see all the computers on the domain/workgroup with sharing enabled. Double-click on a computer icon to access its shares and files.
•If you want to be able to share folders with nautilus (the file browser), install the nautilus-share package (installed by default in Ubuntu 9.10 Desktop edition):

sudo apt-get install nautilus-shareAlternate: From the menu at the top select "Location" -> "Connect to a server". In the "Service type" pull down select "Windows share". Enter the server ip address in the "Server:" box and the share name in the "Share:" box. Click "Connect" and then "Connect" again on the second dialog box
Note: The default installation of Samba does not synchronize passwords. You may have to run "smbpasswd" for each user that needs to have access to his Ubuntu home directory from Microsoft Windows.

Windows Clients (XP,Server,Vista, Win7)
Microsoft Windows clients connect and browse through their corresponding network interface.
Example: XP clients can open Windows Network Neighborhood or My Network Places to browse available SMB shares.
Back to top
Samba Client - Manual Configuration
This section covers how to manually configure and connect to a SMB file server from an Ubuntu client. smbclient is a command line tool similar to a ftp connection while smbfs allows you to mount a SMB file share. Once a SMB share is mounted it acts similar to a local hard drive (you can access the SMB share with your file browser (nautilus, konqueror, thunar, other).

Connecting to a Samba File Server from the command line
Connecting from the command line is similar to a ftp connection.
List public SMB shares with

smbclient -L //server -U userConnect to a SMB share with

smbclient //server/share -U userEnter you user password.
You can connect directly with

smbclient //server/share -U user%passwordbut your password will show on the screen (less secure).
Once connected you will get a prompt that looks like this :

smb: \>Type "help" , without quotes, at the prompt for a list of available commands.
Back to top

Connecting using CIFS
CIFS is included in the smbfs package and is a replacement for smbfs (I know, the terminology here is a little confusing).
Reference : http://linux-cifs.samba.org/
As above, install by any method, smbfs.

Allow non-root users to mount SMB shares
By default only root may mount SMB shares on the command line. To allow non-root users to mount SMB shares you could set the SUID, but I advise you configure sudo. You should configure sudo with visudo
You may either allow the gruop "users" to mount SMB shares, or add a group, samba, and add users you wish to allow to mount SMB shares to the samba group.

sudo groupadd samba
sudo adduser user sambaChange "user" to the username you wish to add to the samba group.

sudo visudoIn the "group" section add your group you wish to allow to mount SMB shares

Add a line in the "group" section :
## Members of the admin group may gain root privileges
%admin ALL=(ALL) ALL
%samba ALL=(ALL) /bin/mount,/bin/umount,/sbin/mount.cifs,/sbin/umount.cifsChange "%samba" to "%users" if you wish to allow members of the users group to mount SMB shares.
The following will mount the myshare folder on myserver to ~/mnt (it will be in your home directory):

mkdir ~/mnt
sudo mount -t cifs //myserver_ip_address/myshare ~/mnt -o username=samb_user,noexecNote: "samba_user" = the user name on the samba server (may be different from your log-in name on the client).
The "noexec" option prevents executable scripts running from the SMB share.
You will be asked for BOTH your sudo and then your samba_user password.
To umount,
sudo umount ~/mnt
Automagically mount SMB shares
In order to have a share mounted automatically every time you reboot, you need to do the following:
With any editor, create a file containing your Windows/Samba user account details:

gksu gedit /etc/samba/userKDE users must use kdesu rather than gksu and instead of Gedit they can use Kwrite as editor.
... it should contain two lines as follows:

username=samba_user
password=samba_user_passwordNote: "samba_user" = the user name on the samba server (may be different from your log-in name on the client). "samba_user_password" is the password you assigned to the samba_user on the samba server.
Save the file and exit gedit.
Change the permissions on the file for security:

sudo chmod 0400 /etc/samba/user # permissions of 0400 = read onlyNow create a directory where you want to mount your share (e.g. /media/samba_share):

sudo mkdir /media/samba_shareNow, using any editor, and add a line to /etc/fstab for your SMB share as follows:

sudo cp /etc/fstab /etc/fstab.bak
gksu gedit /etc/fstabAdd a line for your SMB share:

//myserver_ip_address/myshare /media/samba_share cifs credentials=/etc/samba/user,noexec 0 0The share will mount automatically when you boot. The "noexec" option prevents executable scripts running from the SMB share.
To mount the share now, without rebooting,

sudo mount /media/samba_shareYou can unmount the share with :

sudo umount /media/samba_shareIf you wish to increase security at the expense of convenience, use this line in /etc/fstab

//myserver_ip_address/myshare /media/samba_share cifs noauto,credentials=/etc/samba/user,noexec 0 0The noexec" option prevents executable scripts running from the SMB share.
Edit /etc/samba/user, remove the password (leave just the samba user).
Now the share will NOT automatically mount when you boot and you will be asked for your samba password.
Mount the share with :

sudo mount /media/samba_shareCIFS may cause a shutdown error.
CIFS VFS: Server not responding.There is a fix in the troubleshooting section of this forum post.
Back to top

Connecting using SMBFS (deprecated)
Note: This method still works, but as outlined under the "CIFS" section above is "deprecated" (no longer maintained and pending removal from the kernel).
Mounting a share on the local filesystem allows you to work around programs that do not yet use GnomeVFS to browse remote shares transparently. To mount a SMB share, first install smbfs:

sudo apt-get update
sudo apt-get install smbfsTo allow non root accounts to mount shares, change the permissions on the smbmnt program thus:

sudo chmod u+s /usr/bin/smbmnt /usr/bin/smbumount

--------------------------------------------------------------------------------


Note: This may be a security risk as after setting the SUID bit anyone can mount a SMB share. I advise you configure sudo, as above.
The working line in /etc/sudoers is as follows (see CIFS section above):

%samba ALL=(ALL) /bin/mount,/bin/umount,/sbin/mount.cifs,/sbin/umount.cifs,/usr/bin/smbmount,/usr/bin/smbumountThis allows any user in the samba group to mount SMB shares (you will need to create a samba group and add users).
The following will mount the myshare folder on myserver to ~/mnt (it will be in your home directory):


--------------------------------------------------------------------------------



mkdir ~/mnt
smbmount //myserver/myshare ~/mntTo umount,
smbumount ~/mntIn order to have a share mounted automatically every time you reboot, you need to do the following:
Open a shell as root

sudo -sCreate a file containing your Windows/Samba user account details:

vi /etc/samba/user...it should contain two lines as follows:
username=george
password=secretChange the permissions on the file for security:

chmod 0600 /etc/samba/userNow create a directory where you want to mount your share (e.g. /mnt/data):

mkdir /mnt/dataNow edit the file system table (/etc/fstab) and add a line as follows:

//server/share /mnt/data smbfs credentials=/etc/samba/user,rw,uid=bob 0 0...where 'bob' is the non-root user you log into ubuntu with, 'server' is the name or address of the Windows machine and 'share' is the name of the share.
To mount the share now, just use the following command as root. It will mount automatically on subsequent reboots.

mount /mnt/datato be continued...

Ubuntu Client
On the Ubuntu client using the menu at the top, go to "Places" -> "Network". You will see an icon "Windows network" and should be able to browse to your shared folder. You will be asked for a password, leave it blank. Click the "Connect button.
(no need for a password).
If you would like to mount your SMB share using your (server) hostname rather than the IP Address, edit /etc/hosts and add your samba server (syntax IP Address hostname).

192.168.1.100 hostnameWhere "hostname" = the name of your samba server.

Windows Client
On Windows open "My Computer" and navigate to "My Network Places". Navigate to your Ubuntu server and your share will be available without a password.
Alternate : From the menu at the top select "Tools" -> "Map Network Drive". Select an available letter for your SMB share (Default is z: ). In the "Folder:" box enter \\samba_server_ipaddress\share. Tic (Select with the mouse) the option "Reconnect at login" if you want the share to be automatically mounted when you boot Windows. Click the "Finish" box. A dialog box will appear, enter your samba user name and password. Click "OK".
If you would like to mount your SMB share using your (server) hostname rather than the IP Address, edit C:\WINDOWS\system32\drivers\etc\hosts and add your samba server (syntax IP Address hostname).

192.168.1.100 hostnameWhere "hostname" = the name of your samba server. Back to top
Samba Server Configuration - Graphical
Note: For Ubuntu 8.04 (Hardy) and later, shared folders are created directly from the folder. Browse to the location of the folder you would like to share, right-click the folder, and choose Sharing Options. Click the Share this folder.
This section should allow you to "quick start" SMB shares between Ubuntu and either Ubuntu or Windows servers. The gui method is easier to work with, because:
1.Shares are Public (browsable in Network Places) 2.A password is not set for shares (they can be mounted by anyone). However, remember that this is less secure.
Be warned you are installing a service (server) and you may wish to install a Firewall management utility to help prevent undesired access. See also the manual configuration sections below to learn how to "hide" your shares from browsing and set a password for access.

Ubuntu Server
This section enables Ubuntu as a samba file server.

Sharing a Folder
To share a directory you must have permission to access the directory. Go to your home directory ( Places -> Home folder). Right click on the "Documents" directory and in the pop up menu select "Share Folder".
If samba is not installed you will get a pop up menu "Sharing services are not installed". Select "Install Windows networks support (SMB)" and deselect "Install Unix networks support (NFS)" -> then click "Install services".
If you get an error message that the samba .deb could not be found, open a terminal and update apt-get.

sudo apt-get updateTry again and Ubuntu will download and install samba. Right click on the "Documents" directory and in the pop up menu select "Share Folder". You will get a pop up menu "Share Folder". Select "Windows networks (SMB)" in the pull down menu and give your share a name in the "Name" box. Unselect the "Read only" check box if you want read/write access to the share. Click the "Share" button.

Windows XP Server
This section enables Windows XP as a samba file server.

Sharing a Folder
1. On the Windows server, browse in explorer ("My Computer") to the location of the folder you wish to share (C:\Documents and Settings for example). Next right click on the folder to share and select "Sharing and Security...". In the pop-up dialog box click the "Sharing" tab. Click the "Network Setup Wizard" to configure your network to allow shares. Work your way through the wizard. Note the default workgroup is MSHOME. You may change this value if you like but all your computers should be in the same workgroup. Eventually you will be given the option to "Turn on file and printer sharing". This is the option you want, continue with the network wizard. You will have to restart your computer for the settings to take effect -> Restart Windows.
2. After rebooting, again open explorer ("My Computer") and navigate to the folder you wish to share. Again right click on the folder and select "Sharing and Security...". In the pop-up dialog box click the "Sharing" tab. In the "Network sharing and security" box, tic (select with the mouse) the "Share this folder on the network" box. Give the folder a share name. This will give read only access to Ubuntu computers via samba. To allow read/write access tic (select with the mouse) the "Allow network users to change my files" box. Click the "Apply" button and close the dialog box.
Back to top

Samba Server Configuration - Manual
Configuration is performed by reading and editing /etc/samba/smb.conf, the configuration file for the samba server.
There are a few graphical tools available such as "kdenetwork-filesharing" and "Swat".
A fairly comprehensive graphical Samba configuration tool is available for KDE, by installing the "kdenetwork-filesharing" package. Once install, you can find it by launching the KDE Control Center. (Alt-F2 and then type kcontrol). Browse to Internet & Network > Samba. It is fairly easy to use.
A less friendly but also graphical tool is Swat, a web-based interface.
The following tips show how to do some basic things without installing additional software, using the command line. It is not difficult, just be careful with typos.
First open a terminal: Applications > System Tools > Terminal and open the file smb.conf

sudo nano -w /etc/samba/smb.confHow to Save: To save in nano use "CTRL-O", then "CTRL-X".
Tip: Replacing nano with gedit gives you a nice graphical editor.
The file *smb.conf* is divided in several sections:

Global Settings
Debugging/Accounting
Authentication
Printing
File sharing
Misc
Share DefinitionsComments may start with either a # or a ;

Global Settings
Let's start with Global Settings. Here you will see several lines, which you can also see in the graphical networktool like workgroup and wins server. If you changed everything to your liking already then you can skip this section, if not change to what you need. If you do not know what items mean, leave them be and read the relevant part in the real Samba-howto instead of randomly changing them. It will save you trouble-shooting later.

File Sharing (Basics)
The important part for us is File sharing. Samba shares are named in brackets, [ ], and configured by adding options in the lines that follow. Most options are boolean (yes / no).
We need to change:

[homes]
comment = Home Directories
browseable = no

# By default, the home directories are exported read-only. Change next
# parameter to 'yes' if you want to be able to write to them.
writable = noThis describes your /home folder. Usually you want to share this folder in a home-environment, because these are the files you want to share. To do so, make the following changes:

[homes]
comment = Home Directories
browseable = yes

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
read only = noThis finishes sharing your /home folder. The last thing we need to do is fixing a user.
Add users who can access your shares with the 'smbpasswd' command.

sudo smbpasswd -a username

New SMB password:
Retype new SMB password:
Added user username.NOTE: the username used here should be a real user setup on your PC/Server. Reload Samba for every change to users/passwords or 'smb.conf'

sudo /etc/init.d/samba reloadThat's the basis of Samba file-sharing. Please leave your comments about what else is needed here.
- Can/should the SMB password be different from the user's system password? MartinSpacek - 2007-11-19
Back to top
File Sharing (Advanced)
We started with the base of Samba file-sharing. The above-mentioned items should be enough to get you started. Next we will add details that you might or might not need.

If you have more than one network card
If you have more than one network card (or interface) then you have to define where you want Samba to run. In smb.conf under the [global] section, add:

interfaces = 127.0.0.1, 192.168.0.31/24
bind interfaces only = yesThe first address (127.0.0.1), is a loopback network connection (it's your own machine). The second address (192.168.0.31), is the address of the card you want Samba to run on, the second number (24) is the subnet default for a CLASS-C network. It may vary depending on your network.
With "bind interfaces only" you limit which interfaces on a machine will serve SMB requests.
You can limit which IP address can connect to your Samba server adding these lines:

hosts allow = 127.0.0.1, 192.168.0.31, 192.168.0.32
hosts deny = 0.0.0.0/0The loopback address must be present in the first line. The second line deny access from all IP address not in the first line.
Back to top

Private and public shares in same config
First you'll want to set this up in the [global] section of your smb.conf

[global]
security = user
encrypt passwords = true
map to guest = bad user
guest account = nobodysecurity = user restricts logins to users on your server. encrypt passwords = true is necessary for most modern versions of Windows to login to your shares. map to guest = bad user will map login attempts with bad user names to the guest account you specify with guest account = nobody. That is, if you attempt to login to the share with a user name not set up with smbpasswd the you will be logged in as the user nobody.
Next the private share

[private]
comment = Private Share
path = /path/to/share/point
browseable = no
read only = noIf browsable is set to no the share will not show up on graphical browsers such a "My Network Places" on Windows or Places -> Network on Ubuntu.
path is the path to the directory that you want to share out. browseable = no will have the share not show up when users browse the network. read only = no will let you, as an authenticated user, write to the share.
Finally, the public share

[public]
comment = Public Share
path = /path/to/share/point
read only = no
guest only = yes
guest ok = yesAgain, path is the path to the directory that you want to share out. read only = no will allow users to write to this share. guest only = yes and guest ok = yes will allow guest logins and also force users to login as guests. The user you specified with guest account in the [global] section must have write permissions on /path/to/share/point in order to write files to the share.
Note: When Windows attempts to access a SMB share it will use the current Windows user name and password. The map to guest = bad user trick above allows access to the public share only if you give Samba an incorrect user name. If you give it a valid user name, but a bad password, the login will fail and Windows will give you a password prompt when you try to access the share. If you have the same user name for your Windows machine and your Ubuntu machine, you could be unwittingly giving the Samba server a valid user name, but invalid password. To resolve this you will either have to change the Windows user name, or to remove that user name from the Samba password file with sudo smbpasswd -x [username].
Note: The above uses security = user. To access the private shares you will have to make sure the user exists in smbpasswd. These users must also already exist as normal users on your machine. You add users to smbpasswd simply by running sudo smbpasswd -a [username] and giving a password.

Setting permissions
To set permissions of newly created documents / files edit /etc/samba/smb.conf and in the [global] section add :

create mask = 0644
directory mask = 0755Back to top

Sharing CUPS Printers

Graphical Configuration

Setup Ubuntu Print Server
1.In your menu go to System -> Administration -> Printing
2.Under "Local Printers" on the left, select the printer you wish to share. Select the "Policies" tab on the right and make sure the "Shared" box is selected.
Ubuntu Client
1.Again go to System -> Administration -> Printing
2.Click "New Printer" in the upper right. In the next menu select "Windows Printer via SAMBA". Now enter your Ubuntu Samba Print Server (set up as above) IP address in the box on the left titled "smb://". Click the "Browse" button. 3.Select the printer in the "SMB Browser" window (Click on the little arrows). Once you have selected your printer, check the "Authentication required" and enter your samba user name and password. Then click the "Verify" button. You should see confirmation that the share is available. 4.Click the "Forward" button and install the drivers for your printer as you would for any other printer.
Windows Client
1.Go to Control Panel -> Printers
2.Click "Add a printer" on the upper left. The printer wizard will start -> click forward. Select Network Printer and click "Next". Select "Browse for a printer" (Top button) and click "Next". In the next window, navigate to your Ubuntu Samba Print Server and click "Next". Continue with the printer and driver installation.
For more information, see NetworkPrintingFromWinXP.
Back to top

Manual Server Configuration
If You would like to share Your printers make the following changes to Samba:
If not already done create the Samba-user You want the share to be used by.
In smb.conf uncomment and change the lines ending up with the following configuration:

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
load printers = yes

# [...] // Some BSD printing stuff, do not edit if You do not need to

# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
printing = cups
printcap name = cupsand in the Share Definitions section append and/or modify the [printers] part ending up like this:

# ======================= Share Definitions =======================
# [...] // File and Folder sharing, do not edit if You do not need to

[printers]
comment = All Printers
browseable = no
path = /tmp
printable = yes
public = yes
writable = no
create mode = 0700
printcap name = /etc/printcap
print command = /usr/bin/lpr -P%p -r %s
printing = cupsSome explanation what is done:
the [printers] part defines the default-behavior for all the printers that are mentioned in "printcap name". A sort of template how to create shares for these printers. This template is applied if "load printers" is set to true. For more detailed explanation refer to the Samba documentation.
And do not forget to reload Samba:

sudo /etc/init.d/samba reloadBack to top

Securing Samba
This section was started to give some general advise on security considerations and is not an exhaustive review of samba security.

/etc/samba/smb.conf
•Networking Section - use "hosts allow" and "hosts deny"
# hosts allow = 127.0.0.1 192.168.1.0/24
hostal allow = 127.0.0.1 192.168.1.1 192.168.1.2
hosts deny = 0.0.0.0/0hosts deny 0.0.0.0/0 = all others. •Shares ◦When defining a share, consider the following options : 1.browseable = no ~ Shares will not show up when browsing your network. 2.users = user1 user2 ~ List of users able to access the share When setting up a Samba share, you can limit the users who have access to your share

[private]
comment = Private Share
path = /path/to/share/point
browseable = no
read only = no
valid users = user1 user2 user3Now only samba users user1, user2, and user3 will have access to the share "private".

Firewall
Configure your firewall (iptables) to limit access to your server. Samba uses ports
•UDP ports 137 and 138 •TCP ports 139 and 445


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

Senin, 22 Maret 2010

Mengatasi Local Only HOTSPOT pada vista

Masalah ini terjadi karena adanya perbedaan antara desain Windows Vistadan Microsoft Windows XP Service Pack 2 (SP2). Khususnya, dalam Windows XPSP2, maka broadcast flag dalam paket DHCP discovery diatur ke 0(dinonaktifkan). Dalam Windows Vista, yang broadcast flag dalam paket DHCPdiscovery tidak dinonaktifkan. Oleh karena itu, beberapa router danbeberapa non-Microsoft DHCP server tidak dapat memproses DHCP discoverypaket tersebut.

nah loh apa saya bilang, Windows VISTA kan penyebabnya? Sempat saya sarankan buat downgrade aja ke Windows XP tapi sayang karena Windows VISTA nya kan original. xixixi

Akhirnya saya menemukan solusinya setelah baca beberapa literatur tadi, nah ini dia solusinya silakan dibaca dengan dengan seksama. Untuk mengatasi masalah ini, menonaktifkan DHCP broadcast flag pada Windows Vista. Untuk melakukannya, ikuti langkah berikut:

1.Click tombol Start —> RUN


, Ketikkan regedit pada kotak RUN tersebut.


Jika muncul prompt konfirmasi password administrator, ketik password anda, atau click Continue.

2.Carilah kemudian click registry subkey berikut:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{GUID}
Pada registry path, click (GUID) subkey yang berhubungan dengan jaringan adaptor yang terhubung ke jaringan.

3.Pada Edit menu, Pilih New, dan kemudian click DWORD (32-bit) Value.
4.Pada kotak New Value #1, ketikkan DhcpConnEnableBcastFlagToggle, dan kemudian tekan ENTER.
5.Klik kanan DhcpConnEnableBcastFlagToggle, dan kemudian click Modify.
6.Pada kotak Value data, ketikkan 1, dan kemudian click OK.
7.Tutup Registry Editor.
Dengan menetapkan registri key ini ke 1, Windows Vista akan mencoba untuk mendapatkan alamat IP dengan menggunakan DHCP di broadcast flag Temukan paket. Jika gagal, ia akan mencoba untuk mendapatkan alamat IP tanpa menggunakan flag di broadcast DHCP Temukan paket.

Jika Anda tahu router atau non-Microsoft DHCP server tidak mendukung broadcast flag DHCP, Anda dapat mengatur entri registri berikut sebagai berikut, bukan menggunakan DhcpConnEnableBcastFlagToggle kunci registri.

HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ TCPIP \ Parameter \ interface \ (GUID)

Value name: DhcpConnForceBroadcastFlag
Value type: REG_DWORD
Value data: 0

Semoga aja dengan solusi ini bisa diatasi masalah tadi, biar ga banyak yang menanyakan masalah yang sama, ga bisa konek internet wifi. Teruslah mencoba dan selalu mencoba, karena orang yang gagal adalah orang yang berhenti mencoba.

Minggu, 21 Maret 2010

SHARING FILE MENGGUNAKAN WINDOWS XP

Salah satu fitur menarik yang terdapat pada Windows XP (termasuk Windows 2000) dibandingkan versi windows sebelumnya yaitu Windows 95/98/ME adalah dukungan level kemanan bertingkat untuk tiap pengguna (user). Yang memberikan kemudahan terutama bagi administrator untuk menentukan dan mengatur user mana yang diberi kewenangan untuk mengakses sebuah informasi pada sistem. Pada makalah ini akan dijelaskan bagaimana cara membuat dan mengatur berbagi file (share) dan folder antar user Windows XP dengan user windows lainnya dalam sebuah jaringan LAN (Local Area Network) berdasarkan hak akses yang berbeda bagi setiap user.


Pada Windows 95/98/ME, data dapat di-sharring dengan menambahkan password pada folder yang telah di-share. Siapapun yang mengetahui password dapat mengakses data yang ada dalam folder tersebut. Hal ini tentunya beresiko tinggi apabila terdapat pada sebuah jaringan yang cukup besar seperti di perkantoran atau universitas.

Pada Windows XP, terdapat dua metode untuk melakukan file sharing, yaitu:

Simple File Sharing (SFS), cara kerjanya seperti file sharing pada windows 98 dan menjadi pilihan standar (default) pada sistem Windows XP. Metode ini biasanya digunakan pada jaringan kecil dengan menggunakan anggota Workgroup dan bukan menggunakan Domain yang biasanya digunakan pada jaringan berskala besar seperti jaringan korporat. Disini taidak ada pengaturan password, level akses ataupun aturan lainnya, sehingga semua user bisa mengakses data yang didalamnya. Fitur ini hanya terdapat pada Windows XP Home Edition.
Access Control List (ACL), apabila ACL dipilih maka secara otomatis metode SFS dimatikan. Dengan metode ACL, administrator atau user dapat mengatur hak akses lebih spesifik untuk setiap folder atau disk, sehingga kerahasiaan dan kemanan data lebih terjamin dibandingkan metode SFS.


Langkah-langkah metode Access Control List (ACL) adalah sebagai berikut:

Mematikan fitur Simple File Sharing untuk meningkatkan kemanan dan kontrol
Membuat User Account dan Group Account
Men-share folder atau disk
Megatur hak akses pada folder atau disk yang telah di-share
Mengijinkan user tanpa password untuk tetap dapat mengakses jaringan


Untuk memudahkan konsep diatas, diilustrasikan sebagai berikut:

Terdapat empat user yaitu: Alasdair, Fraser, Iona, and Catriona
Terdapat tiga folder yang akan di-sharring yaitu Girlstuff, Boystuff, dan Kidstuff. Dimana ketiga folder tersebut mempunyai pengaturan yang berbeda untuk setiap user. Folder Girlstuff hanya bisa diakses oleh Iona dan Catriona, folder Boystuff oleh Alasdair dan Fraser serta Kidstuff oleh semua user.
Melihat bagaimana tiap user mencoba mengakses ketiga folder diatas.


Mematikan Fungsi Simple File Sharing

Langkah pertama adalah mematikan fungsi FSF untuk mengaktifkan ACL dengan cara sebagai berikut:

Masuk ke menu Start | My Computer | Tools | Folder Options | View.
Geser slider pada bagian Advance Option sampai menemukan ‘Use Simple File Sharing (Recommended)’, kemudian hilangkan tanda [√] (un-check).
Klik tombol OK.



Gambar 1. Jendela Dialog Folder Option


Membuat User Account

Langkah selanjutnya adalah membuat account untuk keempat user diatas dengan cara sebagai berikut:

Masuk ke menu Start | Control Panel | User Accounts. Selanjutnya tekan tombol ‘Create a new account’, dan masukkan nama user yang akan dibuat. Dalam hal ini sebagai contoh adalah user Alasdair.




Gambar 2. Langkah-langkah membuat User Account


Klik tombol Next kemudian pilih tipe account yang akan dipakai oleh user Alasdair. Karena hak aksesnya akan dibatasi maka pilih ‘Limited’. Ulangi langakah diatas untuk membuat account yang lainnya.


Membuat Password untuk Setiap User

Secara default, setiap user boleh tidak memiliki password. Tetapi Windows XP tidak akan memperkenankan seorang user mengakses mesin berbasis Windows XP dalam sebuah jaringan tanpa memiliki password. Untuk menambahkan password, pada Control Panel | User Account, pilih user yang dikehendaki kemudian klik ‘Create a new password’. Masukkan password dan ulangi sekali lagi untuk konfirmasi. Usahakan password tidak mudah ditebak untuk keamanan. Ulangi pembuatan password untuk user lain yang telah dibuat diatas. Sebagai tambahan (bila dikehendaki), masukkan ‘Password hint’ untuk menjaga user yang lupa akan passwordnya.




Gambar 3. User Fraser telah dilindungi oleh password

Mengatur Hak Akses untuk User Tidak Berpasword

Supaya user lain yang tidak memiliki password dapat pula mengakses mesin XP maka perlu dilakuka perubahan pada sistem sebagai berikut:

Masuk ke menu Control Panel | Performance and Maintenance | Administrative Tools | Local Security Policy.
Pilih Local Policies | Security Options.
Klik dua kali pada ‘Accounts: Limit local account use of blank passwords to console login only’ , dimana menjadi pilihan default. Matikan (Disable) pilihan ini kemudian klik OK. Dan sekarang semua user yang tidak memiliki password dapat mengakses ke mesin XP.





Gambar 4. Tampilan Local Security Policy


Untuk pengaturan lebih lanjut mengenai user account dapat ditemukan dan diatur pada bagian: Start | Control Panel | Performance and Maintenance | Administrative Tools Computer Management kemudian buka folder ‘Local Users and Groups’, pilih ‘Users’.


Membuat Grup User

Untuk memudahkan dalam pemberian hak akses kepada setiap user, sebaiknya dibuat sebuah grup yang mewakili karakteristik dari sekelompok user. Misalkan dalam sebuah universitas terdapat banyak user karyawan dan mahasiswa. Akan lebih mudah diatur apabila terdapat grup mahasiswa dan karyawan. Dimana aturan untuk satu grup karyawan akan belaku bagi semua user yang menjadi karyawan pada universitas tersebut. Untuk membuat sebuah grup langkah-langkahnya sebagai berikut:

Dari menu Control Panel | Adimistrative Tools | Computer Management , buka System Tools | Local Users and Groups | Groups; kemudian pilih Action | New Group.
Klik ‘New Group’ beri nama dan deskripsi grup. Sebagai contoh: Boys.
Klik ‘Add’ untuk menambahkan user kedalam grup.
Pada pilihan ‘Select User’, atur ‘Object Type’ ke ‘Users’ kemudian klik OK. Pada ‘Location’ akan menampilkan nama komputer yang digunakan.
Selanjutnya klik ‘Advance’ dan klik ‘Find Now’ untuk melihat daftar user.
Pilih user yang akan dimasukkan kedalam grup baru ini. Gunakan tombol [Ctrl] untuk melakukan banyak pilihan user. Lalu klik OK dua kali.

Gambar 5. Membuat Grup User

Membuat Folder yang akan Disharing

Langkah berikutnya adalah membuat folder yang akan dijadikan sharing file. Pada Windows Exploler, masuk ke direktori utama drive C. Buat tiga folder yaitu GirlStuff, BoyStuff dan KidStuf dengan cara meng-klik kanan kemudian pilih New | Folder.


Gambar 6. Membuat 3 folder pada direktori utama drive C

Berikutnya adalah memberikan batasan spesifik terhadap ke tiga folder tersebut. Disini akan dicontohkan pada folder Boystuff.

Klik-kanan pada folder Boystuff, pilih ‘Sharing and Security’.
Pada Tab Sharing, pilih ‘Share this folder’ dan beri nama share serta deskripsinya pada bagian ‘Comment’.
Abaikan pada bagian User Limit, pada Windows XP jumlah maksimal user yang diijinkan terhubung pada mesin dalam satu waktu adalah 10.

Gambar 7. Tampilan dialog File Sharing Properties

Mengatur Acces Control List pada Folder Share

Masih pada folder Boystuff Properties, klik tombol ‘Permissions’. Secara default akan terpilih Everyone dimana memiliki hak akses mutlak pada folder, sehingga bisa mengubah bahkan menghapus apapun yang ada didalam folder Boystuff.


Gambar 8. Dialog Permission pada Folder yang Dishare

Untuk mengubah hak akses sebagai berikut:

Klik ‘Add’ kemudian pilih ‘Object Type’
Hilangkan tanda [√] (un-check) pada Built-in security principles and Groups, karena kita hanya akan melihat user saja. Klik OK, maka dari lokasi ini akan muncul nama komputer milik kita.
Pilih ‘Advance’ kemudian klik ‘Find Now’, akan muncul daftar user.
Klik pada user yang akan diberi hak akses untuk folder Boystuff, yaitu Aldair dan Fraser. Gunakan kombinasi tombol [CTRL] + Klik untuk melakuka pemilihan banyak (multiple choise).

Gambar 9. Proses Perubahan Hak Akses pada Folder Boystuff

Kembali ke editor ACL, secara default, user yang baru ditambahkan hanya memiliki hak untuk membaca saja (read-only). Supaya user memiliki hak baca/tulis (read-write), aktifkan pada bagian ‘Change’ di Permission for X (X: Nama User). Lakukan untuk user Alasdair dan Fraser serta pastikan jangan ada yang diberi hak ‘Full Control’.


Gambar 10. Proses perubahan hak akses pada folder Boystuff

Selanjutnya lakukan langkah-langkah diatas untuk folder Girlstuff sehingga hanya bisa diakses oleh Iona dan Catriona. Serta jangan lupa hapus grup Everyone. Dan terakhir pilih folder Kidstuff serta ulangi prosedur diatas supaya keempat user dapat mengakses folder tersebut.

Menghubungkan Klien ke Server

Ketika user lain dalam jaringan mencoba mengakses data yang ada pada mesin XP, sistem akan mengidentifikasi user dan password user tersebut. Apabila account user tersebut ada didalam sistem, selanjutnya ia akan mengecek ke ACL untuk memastikan folder mana yang dapat diakses oleh user.

a. Client Windows 95/98/ME

Berikut ini adalah langkah-langkah untuk menghubungkan sebuah klien yang menggunakan sistem operasi Windows 98SE. Apabila kita login kedalam sistem windows 98 tanpa password, maka harus Logout terlebih dahulu, kemudian masukkan nama dan password yang telah terdaftar pada mesin XP dan windows 98 tersebut. Sedangkan pada pengaturan Network Properties dapat diatur ke Primary Network Logon to Windows Logon, sedangkan jika diatur ke Client for Microsoft Networks apabila klien tersebut terhubung ke Windows NT/2000. Berikut adalah langkah-langkah untuk mengakses mesin XP:

Klik dua kali pada ikon Network Neighborhoo atau My Network Places. Akan muncul nama-nama komputer yang terhubung dalam satu grup.

Gambar 11. Tampilan Network Neighborhood

apabila terdapat peringatan error, kemungkinan anda belum login ke windows 98SE, Pilih Start | Logout, kemudian login ulang dengan memasukkan user name dan password. Klik dua kali pada mesinXP yang telah tersedia untuk mengakses folder yang telah di-share.

Gambar 12. Tampilan pada server MesinXP yang telah di share foldernya

Masuk ke folder-folder yang tersedia. Apabila user deberi hak akses Read/Write, maka bisa memodifikasi file yang ada di server, juga dimungkinkan untuk mengkopi file dari server ke tempat klien dimana dia berada.

Gambar 13. User mengakses file yang berada di server mesin XP

Apabila ada seorang user bukan dari anggota grup yang telah ditentukan pada server mesin XP, mencoba mengakses informasi yang ada disebuah folder dimana dia tidak memiliki hak akses terhadap folder tersebut, maka server secara otomatis akan menolak user tersebut. Misalkan Fraser mencoba untuk mengakses data yang ada di folder Girlstuff, maka sistem akan memberikan warning box bahwa user Fraser ditolak.


Gambar 14. Warning box yang muncul apabila user tanpa akses mencoba masuk

b. Client Windows XP

Pada Windows XP yang dilakukan hampir sama pada windows 98, masuk ke My Network, kemudian pilih server yang akan dituju. Selanjutnya akan muncul form username dan Password. Salah satu perbedaan jika menggunakan windows XP, kita bisa masuk menggunakan user dan password user lain selama user dan passwordnya terdapat pada server mesin XP

Windows XP Professional File Sharing

One of the handy features of Windows XP (and Windows 2000, for that matter) compared to earlier Windows versions like 95/98/Me is its support for user-level security, which gives you fine control over who can access what information on a system. In this article, we'll show you how to set up your Windows XP Professional computer so you can share files and folders with other Windows computers on a network, while making sure that only desired users have access.

In Windows 95/98/Me, you share data by assigning a password to a shared folder, and anyone that knows the password can gain access to the data. That may be adequate in a small home network where, for example, Mom and Dad know the password to the family's financial data, but Junior doesn't. But it isn't practical in a networks with lots of potential users, since it's hard to keep a password secret amongst a large group of people.

Windows XP Professional replaces password-based security with two alternatives:

Simple File Sharing is enabled by default on Windows XP Professional systems that are members of a workgroup (typically used in small networks) rather than a domain (typically used in large corporate networks). For full details, see our article on Simple File Sharing. There are no passwords or access restrictions and, with one exception described in the article, everything that's shared is accessible by everyone on the network. Simple File Sharing is the only type of sharing available in Windows XP Home Edition.
By disabling Simple File Sharing, you can specify an Access Control List (ACL) for each shared disk or folder. Using an ACL gives you much greater control over shared data, since it lets you determine the specific users that will have access as well as the level of access they will receive.

Jumat, 19 Maret 2010

fix windows unable log certificate

I recently bought a new Linksys wireless router and after setting it up with basic WEP security, I tried to logon from my laptop and was successful! Not very exciting, eh?

So then I tried to connect from my desktop computer that has a wireless USB adapter attached to it and I ended up getting this error message:

Windows was unable to find a certificate to log you on to the network


Fabulous! What certificate! I checked my settings on the wireless router to make sure I didn’t accidentally setup certificate security, but found no such thing. Also, since I was able to connect from my laptop with no problem, it led me to believe it was something wrong with my desktop.

After about 30 minutes of fiddling around with various settings, I was able to figure out what the problem was. Here’s how to connect to your wireless router if you are getting this message.

First, click on the wireless icon in your taskbar and under Related Tasks, choose Change advanced settings.



Now click on the Wireless Networks tab and select the network in the list at the bottom. Click on Properties once you select the wireless network that is having problems.



Click on the Authentication tab and now uncheck the Enable IEEE 802.1x authentication for this network box. If the box was checked, then that was why you were getting the “unable to find a certificate to log you on to the network” message because Windows is looking for one, but your wireless router is not setup for certificate security.



And that’s it! Once I unchecked that box and tried to reconnect to the wireless network, everything worked fine! Enjoy

Windows was unable to find a certificate to log you on to the network

We have a wireless network with two computers running Windows XP. One computer frequently will not connect to the network on start-up. We get a message that says "Windows was unable to find a certificate to log you on to the network"

After bringing up the Linksys window and re-establishing the connection, it will work for the rest of the session.

Any advice is appreciated. Kudos! Thanks!


02-12-2008 06:51 PM

Reply



Bookmark this Message
Subscribe to this Message


Subscribe to this message's RSS Feed
Highlight this Message
Print this Message
Report Abuse to a Moderator



Re: WUSB300N Unable to find Certificate Options

ridcully
Junior specialist
Posts: 1976
Registered: 09-07-2006



Message 2 of 4

Viewed 3,850 times


This is caused by setting the encryption to WPA-RADIUS instead of WPA-PSK on the client radio.Both the router and the client are trying to find a RADIUS server with which to authenticate your system.Switch the encryption to WPA-PSK (pre-shared key) on both ends and it will work ....... Kudos! Thanks!


02-13-2008 02:41 PM

Reply



Mark Message as New
Bookmark this Message
Subscribe to this Message


Subscribe to this message's RSS Feed
Highlight this Message
Print this Message
Report Abuse to a Moderator



Re: WUSB300N Unable to find Certificate Options


I couldn't find a place to do that. I did find that if I double-clicked on the little icon in the lower right corner that looks like a monitor with two arcs to the right, a window comes up that says "Wireless Network Connection 2 Status". If I click on properties and configure and advanced, there is a property for Encryption type. It currently has a value of HW Encryption. The only other choice is SW Encryption. Am I looking in the wrong place?




Re: WUSB300N Unable to find Certificate Options


BTW - I have two icons in the lower right corner that seem to have something to do with the wireless network. One looks like a computer monitor with two circular arcs to the right. The other is a rectangle with three quarter circular arcs in it. If the system is working, the rectangle is green. If not working, it is gray.

adsl to router 2

tanya
Mohon pencerahan.
Sy baru pasang speedy pake modem Aztech, link Ok bisa pake.
Lantas 1 mg kemudian beli Linksys utk wifi nya.
Tanya dong om, Kalo setting di Linksys or Aztech yg perlu diubah apa ya biar jalan ?

Tak jalanin wizard linksys ....responnya unable to connect to internet.

di Aztechnya sbb :

DSL UP

Downstream / Upstream (Kbps) 384/64

Internet Connected

Connected Time 0hr 54min 37sec

Connection Type PPPoE

Username 121122200843@telkom.net

IP Address 125.161.204.111

Default Gateway 125.161.204.1

Primary DNS 203.130.196.5

Secondary DNS 203.130.208.18




Router Information


System Uptime 0 hours 55 minutes
Model DSL605EU

Firmware Version 113.106.1i

Build 005

Ethernet MAC address 00:30:0A:8E:F2:1C

DSL MAC address 00:30:0A:8E:F2:1E

USB MAC address 00:30:0A:8E:F2:1D

NAT Enabled

Firewall Enabled


Mhn info di Linksys hrs setting sept apa.

Sy call ke 147 ,ktnya Router urusan anda

tks om dan rekans sekalian.

jawab :
Coba tolong dicolokin RJ45 dari port LAN modem Aztech ke salah satu port LAN di Linksys (bukan yang port internet lho) terus coba buka internet browsernya.

Pengalaman saya (menggunakan modem 3com dan router linksys) waktu awalnya kabel RJ45 dari modem saya colokin ke port internet ternyata ngga bisa connect justru kalau ke port LAN switch malah bisa.

tanya :
bentar-bentar, WRTG ada 1 WAN, dan 4 port LAN, lha port internet yang mana tuh pak ? (kalo port internet tuh puluhan ribu kayaknya hehehhehe)

jawab :
Sorry maksud saya tentang port internet adalah WAN
Ketika saya colokin RJ45 dari modem ke port itu internetnya malah ngga bisa Tapi kalau ke LAN 1,2... dst WIFInya bisa


Waduh, makasih baged om-om ... sy juga punya kasus sama aztech 605EU + WRT54GL skrg udah bisa jalan berkat forum ini. ternyata kable dari Aztech dicolokin ke Eth. WRT54GL malah bisa(seting di 'connectin type' WRT54GL-nya DHCP)... tp stlh 4jam utak-atik (Hihihi..Katro ya)

(Masih Katro jg mode:On),
Sekalian mo tanya jg om-om senior, kalo kasusnya seperti diatas, aztech-WRT54GL link-nya kan pake Ethernet ya...berarti ... Linksys WAG200G+WRT54GL bisa juga gak ya? asumsinya WRT54GL-nya dipake sbg Repeater WIFI-nya WAG200G (spy jangkauannya bs tambah jauh) Om-om senior tolongin sy ya ngerjain PR dari pak RT buat ngebangun RT/RW net. Pls Help........


WAG200G + WRT54GL bisa juga sih, tetapi ada fungsi yang tidak digunakan karena keduanya sama2 routernya, kalo mau memperirit budget beli WAP54G / JAHT / Levelone sebagai repeater, dan diperhatikan untuk produk linksys pastikan dulu voltase listrik stabil.

Sebenernya saya telat baca forum ini om...., pertama saya beli WAG200G karena jangkauannya kurang saya tambah WRT54GL+DD-WRT (dapat baca di forum ini juga). Pas dikonek gak nyambung juga, akhirnya tukar pinjam Aztechnya teman


http://opensource.telkomspeedy.com/forum/viewtopic.php?id=1393

Connecting Linksys AM300 ADSL Modem to a Linksys WRT54GS Wireless Router Options

Help! I am trying to connect a Linksys AM300 ADSL Modem to a Linksys WRT54GS router and then to a PC running windows XP. All three devices are connected via Ethernet cable i.e no wireless. I thought this would be easy however, it has turned in to a nightmare! I have spoken to a Linksys support engineer and even though on the AM300 box it shows such a situation the support engineer said you cannot connect an AM300 to a WRT54GS! This sounds daft. I am a novice at this networking game and would be grateful to anyone who can spend sometime explaining how I should set up the AM300, WRT54GS and XP laptop.

At present I can connect to the internet by using an Ethernet cable to connect my XP laptop directly to the AM300 (I used the Linksys auto configuration tool to setup the AM300) and this works fine. In fact that is how I am presently writing this post. The problem occurs when I connect the WRT54GS between the XP laptop and the AM300. At this point I loose the internet connection and depending upon the settings in the AM300 & WRT54GS it depends on whether I can see these two devices by typing in the IP address (http://192.168.1.1) in to IE7.

I am confused on what settings to put where – I have tried most combinations but nothing seems to work. My end game is to connect both my NAS and Vista desktop to the WRT54GS using Ethernet cables and connect both my XP Laptop and Nokia N800 to the WRT54GS using wireless. At present I have put the Vista PC away as this seems to introduce a whole new problem i.e. it won’t connect to the internet even when connected directly to the AM300 via Ethernet.

Question 1

So to start with what settings should I put in the AM300? Should I set it to bridge mode or PPOE or Router? Can I leave the IP address at 192.168.1.1.? I read on some blogs that the IP address of the AM300 and WRT54GS will clash if one of them is not changed. My starting point for doing config changes to the AM300 is after I have run the auto setup software – this puts the AM300 in to Gateway mode on the advanced tab and gives me good internet access when connected directly to my XP laptop.

Question 2

What settings should I put in the WRT54GS? My internet service provider uses PPOE and the WRT54GS has such an option. What do I do with the IP address? Should it be set to 192.162.2.1 as some blogs suggest? What should I do with the DHCP server settings in both the AM300 and WRT54GS?

Question 3

What settings do I need in my XP Laptop (connecting via an Ethernet cable to keep it simple)? Do I just leave them as is as it works when connected directly to the AM300?

Question 4

In what sequence do I power on the AM300, WRT54GS and XP Laptop? This is completely confusing me!!

Can you keep you please keep your answers simple as I am not an expert. In case your wondering with the exception of the AM300 I have had all this kit working however, I moved house and in doing so moved from a Cable ISP to an ADSL ISP hence the confusion with the AM300 (the cable ISP provided their own modem that worked fine).

In case you need to know the XP laptop is running service pack 3 and the vista desktop is running service pack 1.

Any help would be much appreciated. Thank you.
Kudos! Thanks!


09-30-2008 08:59 PM

Reply



Bookmark this Message
Subscribe to this Message


Subscribe to this message's RSS Feed
Highlight this Message
Print this Message
Report Abuse to a Moderator



Re: Connecting Linksys AM300 ADSL Modem to a Linksys WRT54GS Wireless Router Options

gandalf
Junior specialist
Posts: 2308
Registered: 09-06-2006



Message 2 of 8

Viewed 3,679 times


Well try upgrading the firmware of the router & keep on holding tightly
the reset button in such a way that power light is blinking on the
router & then do a complete network power cycle i.e., unplug the power
cables from the modem & from the router & then plug in the power cable
to the modem first once all the lights are solid green you could plug
in the power cable to the router & check out it will definately work!!
Kudos! Thanks!


10-01-2008 05:00 PM

Reply



Mark Message as New
Bookmark this Message
Subscribe to this Message


Subscribe to this message's RSS Feed
Highlight this Message
Print this Message
Report Abuse to a Moderator



Re: Connecting Linksys AM300 ADSL Modem to a Linksys WRT54GS Wireless Router Options

Ian12345
Regular visitor
Posts: 4
Registered: 09-30-2008



Message 3 of 8

Viewed 3,663 times


gandlalf,

Thanks for the reply however, I really need answers to all my questions. I upgraded the firmwire before I started this exercise. I have powered off an on my equipment as you suggested but still without success. I know that in theory the Linksys router and modem should be able to swap routing tables however, they don't seem to do this in practice - maybe this is a fault with the Linksys product. If I connect the modem to the router and the router to the XP laptop then I can successfully ping the router. However, I cannot ping the modem (even when logged in to the router and doing it from the admin tab it fails).

I really need some anwers to basic questions. For example:-
1) Should the ADSL modem be setup in Gateway or Router mode?
2) Should the WRT Router be set up in Gateway or Router mode?
3) Does the WRT router have to be set up for PPoE as well as the modem?

For info the modem IP address is 192.168.1.1. (default) but I have changed the Router IP address to 192.168.2.2.

Any help is most appreciated. I am being to think the Linksys engineer was correct when he said a Linksys Modem is not compatible with a Linksys Router - daft I know! Kudos! Thanks!


10-02-2008 03:20 AM

Reply



Mark Message as New
Bookmark this Message
Subscribe to this Message


Subscribe to this message's RSS Feed
Highlight this Message
Print this Message
Report Abuse to a Moderator



Re: Connecting Linksys AM300 ADSL Modem to a Linksys WRT54GS Wireless Router Options

gandalf
Junior specialist
Posts: 2308
Registered: 09-06-2006



Message 4 of 8

Viewed 3,652 times


You can switch the modem to bridge. keep the IP as it is on the modem (192.168.1.1) and on the router it should be 192.168.2.2 as you have set up already . on the router use internet connection type as PPPoE. Kudos! Thanks!


10-02-2008 11:14 AM

Reply



Mark Message as New
Bookmark this Message
Subscribe to this Message


Subscribe to this message's RSS Feed
Highlight this Message
Print this Message
Report Abuse to a Moderator



Re: Connecting Linksys AM300 ADSL Modem to a Linksys WRT54GS Wireless Router Options

_crazy_
Newbie
Posts: 2
Registered: 10-02-2008



Message 5 of 8

Viewed 3,644 times


Hi, try to upgrade the AM300 firmware to 1.19.04.

Changelog:

Firmware V1.19.04 - 02/04/08
- TI Datapump v7.2.3.0
- Resolves issue with LAN Subnet when using PPP Half Bridge
- Resolves issue with PPPoE connection failure when client receives PPPoE-Session packets before receiving PADS. Kudos! Thanks!


10-02-2008 12:30 PM

Reply



Mark Message as New
Bookmark this Message
Subscribe to this Message


Subscribe to this message's RSS Feed
Highlight this Message
Print this Message
Report Abuse to a Moderator



Re: Connecting Linksys AM300 ADSL Modem to a Linksys WRT54GS Wireless Router Options

Ian12345
Regular visitor
Posts: 4
Registered: 09-30-2008



Message 6 of 8

Viewed 3,638 times


Crazy, thanks for the info. I am presently running version 1.19.02. Do you know where I can download 1.19.04 as I cannot find it on the Linksys website and it does sound relevant? Thanks. Kudos! Thanks!


10-02-2008 05:12 PM

Reply



Mark Message as New
Bookmark this Message
Subscribe to this Message


Subscribe to this message's RSS Feed
Highlight this Message
Print this Message
Report Abuse to a Moderator



Re: Connecting Linksys AM300 ADSL Modem to a Linksys WRT54GS Wireless Router Options

WEP n WPA

Keamanan Wireless dengan metode Wired Equivalent Privacy (WEP)


WEP merupakan standart keamanan & enkripsi pertama yang digunakan pada wireless, WEP (Wired Equivalent Privacy) adalah suatu metoda pengamanan jaringan nirkabel, disebut juga dengan Shared Key Authentication. Shared Key Authentication adalah metoda otentikasi yang membutuhkan penggunaan WEP. Enkripsi WEP menggunakan kunci yang dimasukkan (oleh administrator) ke client maupun access point. Kunci ini harus cocok dari yang diberikan akses point ke client, dengan yang dimasukkan client untuk authentikasi menuju access point, dan WEP mempunyai standar 802.11b.


Proses Shared Key Authentication:



1.Client meminta asosiasi ke access point, langkah ini sama seperti Open System Authentication.

2.Access point mengirimkan text challenge ke client secara transparan.

3.Client akan memberikan respon dengan mengenkripsi text challenge dengan menggunakan kunci WEP dan mengirimkan kembali ke access point.

4.Access point memberi respon atas tanggapan client, akses point akan melakukan decrypt terhadap respon enkripsi dari client untuk melakukan verifikasi bahwa text challenge dienkripsi dengan menggunakan WEP key yang sesuai. Pada proses ini, access point akan menentukan apakah client sudah memberikan kunci WEP yang sesuai. Apabila kunci WEP yang diberikan oleh client sudah benar, maka access point akan merespon positif dan langsung meng-authentikasi client. Namun bila kunci WEP yang dimasukkan client adalah salah, maka access point akan merespon negatif dan client tidak akan diberi authentikasi. Dengan demikian, client tidak akan terauthentikasi dan tidak terasosiasi.



WEP memiliki berbagai kelemahan antara lain :



1.Masalah kunci yang lemah, algoritma RC4 yang digunakan dapat dipecahkan.

2.WEP menggunakan kunci yang bersifat statis

3.Masalah initialization vector (IV) WEP

4.Masalah integritas pesan Cyclic Redundancy Check (CRC-32)


WEP terdiri dari dua tingkatan, yakni kunci 64 bit, dan 128 bit. Sebenarnya kunci rahasia pada kunci WEP 64 bit hanya 40 bit, sedang 24bit merupakan Inisialisasi Vektor (IV). Demikian juga pada kunci WEP 128 bit, kunci rahasia terdiri dari 104bit.
Serangan-serangan pada kelemahan WEP antara lain :




1.Serangan terhadap kelemahan inisialisasi vektor (IV), sering disebut FMS attack. FMS singkatan dari nama ketiga penemu kelemahan IV yakni Fluhrer, Mantin, dan Shamir. Serangan ini dilakukan dengan cara mengumpulkan IV yang lemah sebanyak-banyaknya. Semakin banyak IV lemah yang diperoleh, semakin cepat ditemukan kunci yang digunakan

2.Mendapatkan IV yang unik melalui packet data yang diperoleh untuk diolah untuk proses cracking kunci WEP dengan lebih cepat. Cara ini disebut chopping attack, pertama kali ditemukan oleh h1kari. Teknik ini hanya membutuhkan IV yang unik sehingga mengurangi kebutuhan IV yang lemah dalam melakukan cracking WEP.

3.Kedua serangan diatas membutuhkan waktu dan packet yang cukup, untuk mempersingkat waktu, para hacker biasanya melakukan traffic injection. Traffic Injection yang sering dilakukan adalah dengan cara mengumpulkan packet ARP kemudian mengirimkan kembali ke access point. Hal ini mengakibatkan pengumpulan initial vektor lebih mudah dan cepat. Berbeda dengan serangan pertama dan kedua, untuk serangan traffic injection,diperlukan spesifikasi alat dan aplikasi tertentu yang mulai jarang ditemui di toko-toko, mulai dari chipset, versi firmware, dan versi driver serta tidak jarang harus melakukan patching terhadap driver dan aplikasinya.


Keamanan wireless dengan metode WI-FI Protected Accsess (WPA)


Merupakan rahasia umum jika WEP (Wired Equivalent Privacy) tidak lagi mampu diandalkan untuk menyediakan koneksi nirkabel (wireless) yang aman dari ulah orang usil atau ingin mengambil keuntungan atas apa yang kita miliki—dikenal dengan jargon hackers. Tidak lama setelah proses pengembangan WEP, kerapuhan dalam aspek kriptografi muncul.
Berbagai macam penelitian mengenai WEP telah dilakukan dan diperoleh kesimpulan bahwa walaupun sebuah jaringan wireless terlindungi oleh WEP, pihak ketiga (hackers) masih dapat membobol masuk. Seorang hacker yang memiliki perlengkapan wireless seadanya dan peralatan software yang digunakan untuk mengumpulkan dan menganalisis cukup data, dapat mengetahui kunci enkripsi yang digunakan.
Menyikapi kelemahan yang dimiliki oleh WEP, telah dikembangkan sebuah teknik pengamanan baru yang disebut sebagai WPA (WiFI Protected Access). Teknik WPA adalah model kompatibel dengan spesifikasi standar draf IEEE 802.11i. Teknik ini mempunyai beberapa tujuan dalam desainnya, yaitu kokoh, interoperasi, mampu digunakan untuk menggantikan WEP, dapat diimplementasikan pada pengguna rumahan atau corporate, dan tersedia untuk publik secepat mungkin. Adanya WPA yang "menggantikan" WPE, apakah benar perasaan "tenang" tersebut didapatkan? Ada banyak tanggapan pro dan kontra mengenai hal tersebut. Ada yang mengatakan, WPA mempunyai mekanisme enkripsi yang lebih kuat. Namun, ada yang pesimistis karena alur komunikasi yang digunakan tidak aman, di mana teknik man- in-the-middle bisa digunakan untuk mengakali proses pengiriman data. Agar tujuan WPA tercapai, setidaknya dua pengembangan sekuriti utama dilakukan. Teknik WPA dibentuk untuk menyediakan pengembangan enkripsi data yang menjadi titik lemah WEP, serta menyediakan user authentication yang tampaknya hilang pada pengembangan konsep WEP.
Teknik WPA didesain menggantikan metode keamanan WEP, yang menggunakan kunci keamanan statik, dengan menggunakan TKIP (Temporal Key Integrity Protocol) yang mampu secara dinamis berubah setelah 10.000 paket data ditransmisikan. Protokol TKIP akan mengambil kunci utama sebagai starting point yang kemudian secara reguler berubah sehingga tidak ada kunci enkripsi yang digunakan dua kali. Background process secara otomatis dilakukan tanpa diketahui oleh pengguna. Dengan melakukan regenerasi kunci enkripsi kurang lebih setiap lima menit, jaringan WiFi yang menggunakan WPA telah memperlambat kerja hackers yang mencoba melakukan cracking kunci terdahulu.
Walaupun menggunakan standar enkripsi 64 dan 128 bit, seperti yang dimiliki teknologi WEP, TKIP membuat WPA menjadi lebih efektif sebagai sebuah mekanisme enkripsi. Namun, masalah penurunan throughput seperti yang dikeluhkan oleh para pengguna jaringan wireless seperti tidak menemui jawaban dari dokumen standar yang dicari. Sebab, masalah yang berhubungan dengan throughput sangatlah bergantung pada hardware yang dimiliki, secara lebih spesifik adalah chipset yang digunakan. Anggapan saat ini, jika penurunan throughput terjadi pada implementasi WEP, maka tingkat penurunan tersebut akan jauh lebih besar jika WPA dan TKIP diimplementasikan walaupun beberapa produk mengklaim bahwa penurunan throughput telah diatasi, tentunya dengan penggunaan chipset yang lebih besar kemampuan dan kapasitasnya.
Proses otentifikasi WPA menggunakan 802.1x dan EAP (Extensible Authentication Protocol). Secara bersamaan, implementasi tersebut akan menyediakan kerangka kerja yang kokoh pada proses otentifikasi pengguna. Kerangka-kerja tersebut akan melakukan utilisasi sebuah server otentifikasi terpusat, seperti RADIUS, untuk melakukan otentifikasi pengguna sebelum bergabung ke jaringan wireless. Juga diberlakukan mutual authentification, sehingga pengguna jaringan wireless tidak secara sengaja bergabung ke jaringan lain yang mungkin akan mencuri identitas jaringannya.
Mekanisme enkripsi AES (Advanced Encryption Standard) tampaknya akan diadopsi WPA dengan mekanisme otentifikasi pengguna. Namun, AES sepertinya belum perlu karena TKIP diprediksikan mampu menyediakan sebuah kerangka enkripsi yang sangat tangguh walaupun belum diketahui untuk berapa lama ketangguhannya dapat bertahan.

Gambaran Setting ADSL to ROUTER

Hi all, mo sharing pengalaman waktu nyeting router WIFI di rumah, ta' coba pake bahasa sehari-hari supaya bisa di mengerti.

sebenarnya sudah lama aku pingin membuat rumah menjadi wireless, baru kesampaian beli routernya weekend kemaren. Selama ini aku berlangganan speedy personal, waktu itu kalau ga salah ada pameran dan aku beli paket yg paling murah... modem adsl yg di dapat juga paling rendah speknya, cuma punya satu ethernet port merk Prolink, type H9000S. (saking tuanya tuh modem udah ga ada lagi di portfolionya prolink :-D)

Aku beli Wireless-G Broadband Router mek Linksys, type WRT54G. alasannyanya cukup lah utk kebutuhan, ga perlu ada modem, karena aku sudah punya si prolink... type G cukup utk deliver 54 KBps over the air... dan harganya mayan lah IDR 550K

kalau baca bungkusnya, aku kira gampang pasangnya, tinggal plug and play... ternyata tidak :-((

setelah ngoprek, tanya sana-sini + baca manual... akhirnya jalan deh

inti permasalahannya ada pada default IP address antara Prolink dan Linksys yg ga nyambung... yg satu pake 10.0.0.2 255.0.0.0 yg satu lagi pake 192.168.1.1 255.255.255.0

permasalah menjadi tambah runyam karena Prolink IPnya ga bisa diubah... jadi solusinya di sisi Linksys yg harus berubah...

Berikut step2nya :
1. kita ga usah mengubah setting pada Modem Prolink, parameter2 yg penting sbb:
IP Address 10.0.0.2
Subnet Mask 255.0.0.0
PPP type PPPoE LLC

2. Linksys settingnya agak panjang nih..

SETUP

- Basic Setup -

Pilih -- Static IP
Internet IP Address: 10.0.0.3
Subnet Mask: 255.0.0.0
Gateway: 10.0.0.2
Static DNS 1: 202.134.0.155
Static DNS 2: 202.134.2.5

Local IP Address: 10.0.1.10
Subnet Mask: 255.255.255.0

DHCP Server: Enable
Starting IP Address: 10.0.1.100
Maximum Number of DHCP Users: 7 (teserah kalian, tapi aku belum check max nya berapa)
Client Lease Time: 0 minutes (0 means one day)
WINS: 0.0.0.0


- Advance Routing -

Operating Mode -- pilih router sbg Gateway


WIRELESS

- Basic Wireless Settings -
Wireless Network Mode: Mixed
Wireless Network Name (SSID): Roy linksys (ganti nama juga boleh)
Wireless Channel: 11 - 2.462GHz
Wireless SSID Broadcast: Enable

- Wireless Security -
sebaiknya di setting... biar orang lain ga bisa nimbrung access internet kita..

Security Mode: WEP
Default Transmit Key: 1
WEP Encryption: 64 bits 10 hex digits
Passphrase: [masukin password kamu] lalu tekan tombol generate
-- nanti muncul password2 yg bisa di pake utk access WIFI secara otomatis
Key 1:
Key 2:
Key 3:
Key 4:


- Advanced Wireless Settings -
Frame Burst: Enabled

Utk parameter lainnya di biarkan standar...


Moga-moga sharing ini bisa membantu kalau2 ada teman2 yg menemukan problem yg sama dengan saya... kalau masih bingung drop me email or message...