setrom [at] WordPress.com

Long Time No See

setrom — Sun, 19 Jun 2011 03:28:30 +0000

Sudah lama tidak update blog ini, sejalan dengan hadirnya aplikasi wordpress for blackberry ya’ mencoba exis, isu terakhir adalah “Ada harga yang lebih murah dari GRATIS yaitu harga pertemanan”. Dunia memang sudah aneh, selama ini usaha memberi support sudah dilakukan tapi memang tidak pernah dipandang maklum saya orang rendahan… Tidak layak mungkin bergaul dengan orang penting.. Yang dibikin penting, ah yang penting aku tidak pusing, biarlah janji tinggal janji , masih ada jalur lain buat mencari rezeki.

padi song

setrom — Tue, 15 Dec 2009 04:04:00 +0000

Engkau… seperti kekasihku yang dulu
Sungguh… hadirmu menyejukkan risau jiwaku
Begitu lekatnya… perasaanku kini padamu
Hingga… anganku kusandarkan padamu

Memang gerakmu memang langkahmu
Mengingatkan aku pada dirinya yang telah berlalu
Inginku menyangkal inginku membantah
Betapa pesona dirimu memikat erat jiwaku

Mungkin… terbuai mungkin aku terlena
Ada… keinginan yang tak tentu arah
Engkau… tercipta bukan untuk bersama
Biar… kunikmati kerinduan ini

Maafkan aku yang selalu teringat akan dirinya
Menggugah segala yang ada dalam kenanganku
Sedapatnya aku menepis keinginan itu
Kuharap engkau dapat memaafkan aku

Apa yang terpancar dari dalam hati
Tak dapat aku bantah tak mampu kusingkirkan
Sesungguhnya aku sangat ingin melupakan
Inginku melupakan …. inginku melupakan ….

Engkau… seperti kekasihku yang dulu
Sungguh… hadirmu menyejukkan risau jiwaku

2,1 Juta Cakram Bajakan Siap Dimusnahkan

setrom — Tue, 15 Dec 2009 03:50:12 +0000

Jakarta – Sepanjang tahun 2009 ini, Direktorat Reskrim Khusus (Ditreskrimsus) Polda Metro Jaya berhasil mengumpulkan 2.187.056 keping cakra digital bajakan. Jutaan cakram bajakan tersebut akan dimusnahkan.

Rincian cakram bajakan yang akan dimusnahkan tersebut terdiri dari 535.628 MP3, 1.324.997 film Indonesia dan barat, 315.856 film porno, serta 10.578 software dan game bajakan.

Barang bukti ini merupakan hasil sitaan dari 51 kasus yang melibatkan 67 orang tersangka, dimana 57 orang di antaranya telah dijatuhi vonis.

Selain CD bajakan, polisi juga menyita 95 unit mesin pengganda VCD (duplikator). Akibat aksi pembajakan ini, kerugian negara diperkirakan mencapai 7,4 miliar.

( faw / faw )

Sumber : Ardhi Suryadhi – detikinet

Sumber : http://www.detikinet.com/read/2009/12/15/104355/1260247/399/21-juta-cakram-bajakan-siap-dimusnahkan

Install Zend Optimizer & IonCube Centos 5.3

setrom — Tue, 06 Oct 2009 12:10:51 +0000

[Zend Optimizer]

Download http://www.zend.com/free_download/optimizer

# wget http://downloads.zend.com/optimizer/3.3.9/ZendOptimizer-3.3.9-linux-glibc23-i386.tar.g

# tar zxf ZendOptimizer-3.3.9-linux-glibc23-i386.tar.gz

# cp ZendOptimizer-3.3.9-linux-glibc23-i386/data/5_1_x_comp/ZendOptimizer.so /usr/lib/php/modules/

# nano /etc/php.ini

” add line”

[Zend]
zend_extension=/usr/lib/php/modules/ZendOptimizer.so

Restart Apache

# /etc/init.d/httpd restart

[ IonCube Loader]

# wget http://downloads2.ioncube.com/loader_downloads/ioncube_loaders_lin_x86.tar.gz

# tar zxf ioncube_loaders_lin_x86.tar.gz

# mv ioncube /usr/lib/php/modules/

# chown -R root:root /usr/lib/php/modules/ioncube

# nano /etc/php.ini

add line after [PHP]/ line no 2

zend_extension=/usr/lib/php/modules/ioncube/ioncube_loader_lin_5.1.so

# /etc/init.d/httpd restart

cek phpinfo();

CentOS 5: Eaccelerator Installation

setrom — Tue, 06 Oct 2009 11:16:30 +0000

eAccelerator is a free open-source PHP accelerator, optimizer, and dynamic content cache. It typically reduces server load and increases the speed of your PHP code by 1-10 times.

Through SSH.

yum install php-devel

yum groupinstall 'Development Tools'

Change directory.

cd /tmp

Get the file.

wget http://bart.eaccelerator.net/source/0.9.5.2/eaccelerator-0.9.5.2.tar.bz2

tar xvfj eaccelerator-0.9.5.2.tar.bz2

Change directory.

cd eaccelerator-0.9.5.2

Phpize.

phpize

./configure

Install it.

make

make install

Create the file /etc/php.d/eaccelerator.ini

vi /etc/php.d/eaccelerator.ini

Enter.

extension="eaccelerator.so" eaccelerator.shm_size="0" eaccelerator.cache_dir="/var/cache/eaccelerator" eaccelerator.enable="1" eaccelerator.optimizer="1" eaccelerator.check_mtime="1" eaccelerator.debug="0" eaccelerator.filter="" eaccelerator.shm_max="0" eaccelerator.shm_ttl="0" eaccelerator.shm_prune_period="0" eaccelerator.shm_only="0" eaccelerator.compress="1" eaccelerator.compress_level="9"

Create /var/cache/eaccelerator ditrectory

mkdir -p /var/cache/eaccelerator

Change permission.

chmod 0777 /var/cache/eaccelerator

Restart Apache.

/etc/init.d/httpd restart

link : http://www.php.ph/2007/12/21/centos-5-eaccelerator-installation/

How to Migrate to Thunderbird Portable

setrom — Fri, 02 Oct 2009 06:12:18 +0000

I’ve been keeping my life on Flash storage since around 2004. I started off using an old SD card in a cheap USB reader as a lightweight method of carrying my daybook and notes between work and home. Over the years 600 web pages of technical notes, my personal journal, plans and action lists migrated to a series of ever larger replacement thumb drives. Today nearly everything I work on lives on a single 8 GByte Sandisk drive.

As the drives have got larger I’ve slowly migrated to a portable software environment running off the same thumb drive, so that whether at a work PC, with a notebook on the train, or one of the bigger laptops at home I have consistent access to applications and data. Most of the thirty applications I regularly use come from PortableApps.com with a smattering of others configured with the help of PortableFreeware.com.

PortableApps.com recently released a new version of Thunderbird Portable and given my son’s assertion that playing The Sims is rather more mission critical than my e-mail it seemed clear that now was a good time to move that last application off of the family laptop and onto the thumb drive. However with an archive of more that 16,000 e-mails I was somewhat concerned at how straightforward that would be.

Like all downloads from PortableApps.com installing Thunderbird Portable 2.0.0.18 was easy, just double click, point it at the correct drive and stand well back. Once installed, I started Thunderbird from the PortableApps menu (well the geek.menu fork, truth be told) and went through its initial set up, supplying dummy data when prompted. Delving around on the thumb drive then revealed that Thunderbird had created a folder of profile information at:

E:\PortableApps\Thunderbird Portable\Data\profile\

This folder is easily identified as it contains ‘Mail’ and ‘extensions’ sub-folders and a variety of ini, dat, rdf, js and db files.

Going back to my original Thunderbird installation the profile data was in the default:

C:\Documents and Settings\frog\Application Data\Thunderbird\Profiles\xxxxxxxx.default

folder (where xxxxxxxx is a random string of characters that, no doubt, hashes my password, inside leg measurement and all my credit card numbers.) Deleting the contents of the profile folder on the thumb drive, I copied the contents of the old

C:\Documents and Settings\frog\Application Data\Thunderbird\Profiles\xxxxxxxx.default

into the now empty

E:\PortableApps\Thunderbird Portable\Data\profile\

ignoring the fact that the two pathnames are structured rather differently.

Starting Thunderbird Portable appeared to work correctly, with all the old messages and folders appearing. However the status line seemed to indicate it was struggling to open a particular message. Exiting Thunderbird, which probably caused it to rewrite its config data, and restarting it solved the problem.

In total it took about ten minutes to move 16,000 archived messages, folder structures, and account settings to the thumb drive. Despite the difference in folder path structure it worked first time and I was impressed by how smoothly Thunderbird handled the change in profile.

Posted by frogplate at 11:19 PM

Prevent “Translating. domain server (255.255.255.255)” Messages after an Invalid Command is Entered on a Router

setrom — Sat, 25 Jul 2009 04:30:39 +0000

Introduction

This document addresses the issue of translating….. domain server (255.255.255.255) messages appearing on the router after an invalid command is entered in user or enabled mode.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

This document is not restricted to specific software and hardware versions.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Host to IP Address Translation

Why “Translating…. domain server (255.255.255.255)” Messages Occur

By default, when a command in user or enable mode is entered into a router and this command is not recognized, the router believes that this is the host name of a device that the user is attempting to reach using telnet. Therefore, the router tries to resolve the unrecognized command into an IP address by doing an IP domain lookup. If no specific domain server has been configured on the router, the router will issue a broadcast for the command to be translated into an IP address. It can take several seconds for the router prompt to return while the router waits for a response to its Domain Name System (DNS) broadcast.

Note: You can also use the transport preferred none command on the vty/con/aux lines to prevent the router from attempting to resolve an invalid command into an IP address. The DNS information is available in the output of other commands. However, when you have to initiate a telnet session from the router, place the telnet keyword before the hostname, since the router does not telnet automatically when you type a hostname. Remember to add the ip name-server command to specify the address of the name server.

The following are examples of the default router behavior in user and enable mode.

User Mode

R1>xxxx

Translating "xxxx"...domain server (255.255.255.255)

(255.255.255.255)

Translating "xxxx"...domain server (255.255.255.255)

% Unknown command or computer name, or unable to find computer address

R1>

Enable Mode

R1#xxxx

Translating "xxxx"...domain server (255.255.255.255)

(255.255.255.255)

Translating "xxxx"...domain server (255.255.255.255)

% Unknown command or computer name, or unable to find computer address

R1#

Disable Host to IP Address Translation to Prevent “Translating….. domain server (255.255.255.255)” Messages

To disable the default behavior of the router of attempting to resolve the invalid command into an IP address, enter the no ip domain-lookup command in global configuration mode.

Verify

To verify that the domain lookup has been disabled, enter an unknown command into the router in user or enable mode. The user will immediately receive a router prompt without the router issuing a DNS broadcast. Below is an example:

R1#xxxx

Translating "xxxx"

Translating "xxxx"

% Unknown command or computer name, or unable to find computer address

R1#

Telnet, Console and AUX Port Passwords on Cisco Routers Configuration Example

setrom — Sat, 25 Jul 2009 04:25:14 +0000

Introduction

This document provides sample configurations for configuring password protection for inbound EXEC connections to the router.

Prerequisites

Requirements

In order to perform the tasks described in this document, you must have privileged EXEC access to the router’s command line interface (CLI). For information on using the command line and for understanding command modes, see Using Cisco IOS Software.

For instructions on connecting a console to your router, refer to the documentation that accompanied your router, or refer to the online documentation for your equipment.

Components Used

The information in this document is based on these software and hardware versions:

Cisco 2509 router
Cisco IOS® Software Version 12.2(19)

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Background Information

The use of password protection to control or restrict access to the command line interface (CLI) of your router is one of the fundamental elements of an overall security plan.

Protecting the router from unauthorized remote access, typically Telnet, is the most common security that needs configuring, but protecting the router from unauthorized local access cannot be overlooked.

Note: Password protection is just one of the many steps you should use in an effective in-depth network security regimen. Firewalls, access-lists, and control of physical access to the equipmet are other elements that must be considered when implementing your security plan.

Command line, or EXEC, access to a router can be made in a number of ways, but in all cases the inbound connection to the router is made on a TTY line. There are four main types of TTY lines, as seen in this sample show line output:

2509#show line
   Tty Typ     Tx/Rx    A Modem  Roty AccO AccI   Uses   Noise  Overruns   Int
*    0 CTY              -    -      -    -    -      0       0     0/0       -
     1 TTY   9600/9600  -    -      -    -    -      0       0     0/0       -
     2 TTY   9600/9600  -    -      -    -    -      0       0     0/0       -
     3 TTY   9600/9600  -    -      -    -    -      0       0     0/0       -
     4 TTY   9600/9600  -    -      -    -    -      0       0     0/0       -
     5 TTY   9600/9600  -    -      -    -    -      0       0     0/0       -
     6 TTY   9600/9600  -    -      -    -    -      0       0     0/0       -
     7 TTY   9600/9600  -    -      -    -    -      0       0     0/0       -
     8 TTY   9600/9600  -    -      -    -    -      0       0     0/0       -
     9 AUX   9600/9600  -    -      -    -    -      0       0     0/0       -
    10 VTY              -    -      -    -    -      0       0     0/0       -
    11 VTY              -    -      -    -    -      0       0     0/0       -
    12 VTY              -    -      -    -    -      0       0     0/0       -
    13 VTY              -    -      -    -    -      0       0     0/0       -
    14 VTY              -    -      -    -    -      0       0     0/0       -

2509#

The CTY line-type is the Console Port. On any router, it appears in the router configuration as line con 0 and in the output of the show line command as cty. The console port is mainly used for local system access using a console terminal.

The TTY lines are asynchronous lines used for inbound or outbound modem and terminal connections and can be seen in a router or access server configuration as line x. The specific line numbers are a function of the hardware built into or installed on the router or access server.

The AUX line is the Auxiliary port, seen in the configuration as line aux 0.

The VTY lines are the Virtual Terminal lines of the router, used solely to control inbound Telnet connections. They are virtual, in the sense that they are a funtion of software – there is no hardware associated with them. They appear in the configuration as line vty 0 4.

Each of these types of lines can be configured with password protection. Lines can be configured to use one password for all users, or for user-specific passwords. User-specific passwords can be configured locally on the router, or you can use an authentication server to provide authentication.

There is no prohibition against configuring different lines with different types of password protection. It is, in fact, common to see routers with a single password for the console and user-specific passwords for other inbound connections.

Below is an example of router output from the show running-config command:

2509#show running-config
Building configuration...

Current configuration : 655 bytes
!
version 12.2
.
.
.

!--- Configuration edited for brevity


line con 0
line 1 8
line aux 0
line vty 0 4
!
end

Configure Passwords on the Line

To specify a password on a line, use the password command in line configuration mode. To enable password checking at login, use the login command in line configuration mode.

Note: To find additional information on the commands used in this document, use the Command Lookup Tool (registered customers only) .

Configuration Procedure

In this example, a password is configured for all users attempting to use the console.

From the privileged EXEC (or “enable”) prompt, enter configuration mode and then switch to line configuration mode using the following commands. Notice that the prompt changes to reflect the current mode.
```
router#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
router(config)#line con 0
router(config-line)#
```

Configure the password, and enable password checking at login.

router(config-line)#password letmein
router(config-line)#login

Exit configuration mode.
```
router(config-line)#end
router#
%SYS-5-CONFIG_I: Configured from console by console
```
Note: Do not save configuration changes to line con 0 until your ability to log in has been verified.

Note: Under the line console configuration, login is a required configuration command to enable password checking at login. Console authentication requires both the password and the login commands to work.

Verify the Configuration

Examine the configuration of the router to verify that the commands have been properly entered:

Certain show commands are supported by the Output Interpreter Tool (registered customers only) , which allows you to view an analysis of show command output.

show running-config – displays the current configuration of the router.
```
router#show running-config
Building configuration...
...

!--- Lines omitted for brevity


!
line con 0
password letmein
login
line 1 8
line aux 0
line vty 0 4
!
end
```
To test the configuration, log off the console and log in again, using the configured password to access the router:
```
router#exit

router con0 is now available

Press RETURN to get started.

User Access Verification
Password:

!--- Password entered here is not displayed by the router


router>
```
Note: Before performing this test, ensure that you have an alternate connection into the router, such as Telnet or dial-in, in case there is a problem logging back into the router.

Troubleshoot Login Failure

If you cannot log back into the router and you have not saved the configuration, reloading the router will eliminate any configuration changes you have made.

If the configuration changes were saved and you cannot login to the router, you will have to perform a password recovery. See Password Recovery Procedures to find instructions for your particular platform.

Configure Local User-Specific Passwords

To establish a username-based authentication system, use the username command in global configuration mode. To enable password checking at login, use the login local command in line configuration mode.

Configuration Procedure

In this example, passwords are configured for users attempting to connect to the router on the VTY lines using Telnet.

From the privileged EXEC (or “enable”) prompt, enter configuration mode and enter username/password combinations, one for each user for whom you want to allow access to the router:

router#configure terminal
	Enter configuration commands, one per line.  End with CNTL/Z.
	router(config)#username russ password montecito
	router(config)#username cindy password belgium
	router(config)#username mike password rottweiler

Switch to line configuration mode, using the following commands. Notice that the prompt changes to reflect the current mode.
```
router(config)#line vty 0 4
router(config-line)#
```
Configure password checking at login.
```
router(config-line)#login local
```
Exit configuration mode.
```
router(config-line)#end
router#
%SYS-5-CONFIG_I: Configured from console by console
```
Note: In order to disable auto Telnet when you type a name on the CLI, configure no logging preferred on the line that is used. While transport preferred none provides the same output, it also disables auto Telnet for the defined host that are configured with the ip host command. This is unlike the no logging preferred command, which stops it for undefined hosts and lets it work for the defined ones.

Verify the Configuration

Examine the configuration of the router to verify that the commands have been properly entered:

show running-config – displays the current configuration of the router.

router#show running-config
Building configuration...
!

!--- Lines omitted for brevity



!
username russ password 0 montecito
username cindy password 0 belgium
username mike password 0 rottweiler
!

!--- Lines omitted for brevity



!
line con 0
line 1 8
line aux 0
line vty 0 4
 login local
!
end

To test this configuration, a Telnet connection must be made to the router. This can be done by connecting from a different host on the network, but you can also test from the router itself by telnetting to the IP address of any interface on the router that is in an up/up state as seen in the output of the show interfaces command.

Here is a sample output if the address of interface ethernet 0 were 10.1.1.1:

router#telnet 10.1.1.1
Trying 10.1.1.1 ... Open

User Access Verification

Username: mike
Password:

!--- Password entered here is not displayed by the router



router

Troubleshoot User-specific Password Failure

Usernames and passwords are case-sensitive. Users attempting to log in with an incorrectly cased username or password will be rejected.

If users are unable to log into the router with their specific passwords, reconfigure the username and password on the router.

Configure AAA Authentication for Login

To enable authentication, authorization, and accounting (AAA) authentication for logins, use the login authentication command in line configuration mode. AAA services must also be configured.

Configuration Procedure

In this example, the router is configured to retrieve users’ passwords from a TACACS+ server when users attempt to connect to the router.

Note: Configuring the router to use other types of AAA servers (RADIUS, for example) is similar. See Configuring Authentication for additional information.

Note: This document does not address configuration of the AAA server itself. Refer to Security Server Protocols for information on configuring the AAA server.

From the privileged EXEC (or “enable”) prompt, enter configuration mode and enter the commands to configure the router to use AAA services for authentication:

	router#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
router(config)#aaa new-model
router(config)#aaa authentication login my-auth-list tacacs+
router(config)#tacacs-server host 192.168.1.101
router(config)#tacacs-server key letmein

Switch to line configuration mode using the following commands. Notice that the prompt changes to reflect the current mode.
```
router(config)#line 1 8
router(config-line)#
```

Configure password checking at login.

router(config-line)#login authentication my-auth-list

Exit configuration mode.

router(config-line)#end
router#
%SYS-5-CONFIG_I: Configured from console by console

Verify the Configuration

Examine the configuration of the router to verify that the commands have been properly entered:

show running-config – displays the current configuration of the router.

router#write terminal
Building configuration...

Current configuration:
!
version 12.0
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname router
!
aaa new-model
aaa authentication login my-auth-list tacacs+
!

!--- Lines omitted for brevity



...
!
tacacs-server host 192.168.1.101
tacacs-server key letmein
!
line con 0
line 1 8
 login authentication my-auth-list
line aux 0
line vty 0 4
!
end

To test this particular configuration, an inbound or outbound connection must be made to the line. See the Modem – Router Connection Guide for specific information on configuring async lines for modem connections.

Alternately, you can configure one or more VTY lines to perform AAA authentication and perform your testing thereupon.

Troubleshoot AAA Login Failure

Before issuing debug commands, see Important Information on Debug Commands.

To troubleshoot a failed login attempt, use the debug command appropriate to your configuration:

Reset a Cisco Router to Factory Default Settings

setrom — Fri, 24 Jul 2009 09:09:58 +0000

Introduction

This document explains how to restore a Cisco router to its original factory default settings.

Prerequisites

Requirements

In order to perform the procedures described in this document, you must have “enable” (also known as “privileged EXEC”) access on the router command line interface.

Components Used

This document is not restricted to specific software and hardware versions.

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Instructions to Reset a Cisco Router Back to Factory Defaults

There are two main methods to return a Cisco router to its original factory defaults. These two methods are described below.

Method 1

This method uses the config-register 0×2102 command in global configuration mode.

Check the configuration register on the router by issuing the show version command. The configuration register setting is displayed in the last line of the show version command output, and should be set to 0×2102. If this is not the case, enter the config-register 0×2102 command once in global configuration mode.
```
router# configure terminal
router(config)# config-register 0x2102
router(config)# end
router#
```
If the show version command is issued again, the same line in the command output will have ‘(will be 0×2102 at next reload)‘ appended to the current register setting.
Erase the current start-up configuration on the router with the write erase command.

Reload the router with the reload command. When prompted to save the configuration, DO NOT save.

router#reload
System configuration has been modified. Save? [yes/no]: n
Proceed with reload? [confirm]

Once the router reloads, the user will be presented with a ‘System Configuration Dialog’ as shown below. The router is now reset back to the original factory defaults.
```
         --- System Configuration Dialog ---
Would you like to enter the initial configuration dialog? [yes/no]:
```

Method 2

This method uses the config-register 0×2142 command in global configuration mode.

Enter the config-register 0×2142 command in global configuration mode.
```
router(config)# config-register 0x2142
```
This causes the router to ignore the start-up configuration on the next reload. If a show version is issued, the last line in the command output will have ‘(will be 0×2142 at next reload)‘ appended to the current configuration register setting.
Reload the router using the reload command in enable mode. It is not necessary to save when prompted to save the system configuration.
```
router#reload
System configuration has been modified. Save? [yes/no]: n
Proceed with reload? [confirm]
```
After the router has reloaded, the user will be presented with the ‘System Configuration Dialog’. Enter no to the question ‘Would you like to enter initial configuration dialog?’
Change the configuration register setting to 0×2102 by entering the config-register 0×2102 command once in global configuration mode.
Issue the write memory command in enable mode to overwrite the existing start-up configuration with the current running configuration.
Reload the router with the reload command in enable mode.Once the router reloads, the user will be presented again with a ‘System configuration Dialog’ as shown below. The router is now reset back to the original factory defaults.
```
         --- System Configuration Dialog ---
Would you like to enter the initial configuration dialog? [yes/no]:
```

Verify

This section provides information you can use to verify that your router has been returned to the factory defaults.

Certain show commands are supported by the Output Interpreter Tool ( registered customers only) , which allows you to view an analysis of show command output.

show running-config – used to verify that the previous running configuration has been erased. The user should be left with a skeleton configuration. For example, there should be no IP addresses configured under any interface on the router.
show version – used to verify that the configuration register is set to the default value of 0×2102.

Reset password CISCO

Konfigurasinya adalah :

Yang jelas yang paling pertama hidupkan dulu Router Cisco -nya

Tekan Break atau Ctrl+Break di terminal keyboard sekitar 10-60 detik pertam pada saat power up. Dan router akan masuk mode ROMMON. Ketik confreg 0×2142 pada rommon 1>. Register 0×2142 akan mem-by pass nvram (yg berisi startup configuration dimana password tersimpan).

rommon 1>confreg 0×2142

Ketik reset pada rommon 2>. Disini Router akan reboot, tapi mengabaikan startup configuration-nya.

rommon 2>reset

Apabila ada pertanyaan tentang initial setup procedure, jawablah dengan no atau ctrl+c
Sekarang sudah masuk ke Router> prompt.
ketikkan enable untuk masuk ke privilege exec mode (anda tidak akan diminta password). Prompt akan berganti ke Router#

Router>enable

Ketik copy startup-config running-config untuk mengkopi semua konfigurasi yang ada di NVRAM ke RAM. Jangan Sampai terbalik !!!

Router#copy startup-config running-config

Untuk mengganti password, ketikkan configure terminal. Prompt akan berganti ke Router(config)#

Router#configure terminal

Gantilah password dengan mengetikkan perintah

Router(config)#enable secret your_new_password_here

Hasil pengkopian configurasi dari NVRAM tadi akan menyebabkan semua interface down. Untuk menghidupkannya kembali, seperti biasa #config terminal -> interface fastEthernet0/0 -> no shutdown. Demikian pula dengan netwrok interface yg lain.

Masih di configure terminal (konfigurasi global). Kembalikan router ke register awal (dalam hal ini register 0×2120).

Router(config)#config-register 0×2102
Router(config)#end

selanjutnya kopikan konfigurasi yg sedang jalan ke NVRAM dg perintah #copy running-config startup-config

Router#copy running-config startup-config

Reload Router Cisco 2600 Series-nya

Router#reload

Sekarang dah selesai dech…

“%Error opening tftp://255.255.255.255/network config” Error Message Prevention

setrom — Thu, 23 Jul 2009 08:34:14 +0000

Contents

Introduction

Prerequisites
- Requirements
- Components Used
- Conventions

Problem: Service Configuration Error Messages

Solution

NetPro Discussion Forums – Featured Conversations

Related Information

Introduction

This document provides explanations of service configuration errors encountered during initial hardware bootup when you run Cisco IOS® software.

Prerequisites
Requirements

There are no specific requirements for this document.
Components Used

This document is not restricted to specific software and hardware versions.

Refer to Cisco Technical Tips Conventions for more information on document conventions.
Problem: Service Configuration Error Messages

Occasionally, during bootup of Cisco hardware through Cisco IOS software, error messages similar to these are displayed:

*

%Error opening tftp://255.255.255.255/network-confg (Socket error)
*

%Error opening tftp://255.255.255.255/cisconet.cfg (Socket error)
*

%Error opening tftp://255.255.255.255/3620-confg (Socket error)
*

%Error opening tftp://255.255.255.255/3620.cfg (Socket error)

These error messages are related to the default service configuration option built into Cisco IOS software, which attempts to access the service configuration files from a network Trivial File Transfer Protocol (TFTP) server.
Solution

In order to disable this feature, issue the no service config global command.

Router#config terminal
Enter configuration commands, one per line.

Router(config)#no service config

Router(config)#exit

Router#copy running-config startup-config

These error messages no longer appear at the next bootup of the router.