Objective: Copy my switches/routers running-config to TFTP server(which is on my laptop)
Error: TFTP: error code 11 received - 18025
Attempts: Login to another workstation that's on the same LAN, DLed the TFTPd64 application and successfully utilizes the TFTP to copy the running-config file of the switch. Then I know it's SOMETHING on my computer.
Solution: That something is the "WinAgents TFTP Service 4" service started automatically, so I had to disable that service. WOOHOO the TFTP is working again!
Note: The solution fits my environment, so it may helped you out and it may not. Which I hope it will.
Friday, April 26, 2013
Thursday, April 25, 2013
Steps to configure Cisco Console, Telnet and Auxiliary port passwords
Follow these steps to configure console passwords.
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 in to the router.
Step 1. From the privileged EXEC (enable) prompt, enter configuration mode ((config)) and then switch to line configuration mode ((config-line), by issuing the following commands:
Note: Notice that the prompt changes to reflect the current mode.
Step 2. Configure the password, and enable password checking at login.
Step 3. Exit configuration mode.
Note: Do not save your configuration changes until your ability to log in has been verified.
Step 4. Verify the configuration.
Examine the configuration of the router to make sure that the commands have been properly entered by issuing the show running-config command.
To test the configuration, log off the console with the exit command and log in again, using the configured password to access the router.
Step 5. Save your configuration.
Perform these steps to configure Telnet passwords.
Note: Before performing this test, ensure that you have an alternate connection into the router, such as console or dial-in, in case there is a problem logging back in to the router.
Step 1. From the privileged EXEC (or enable) prompt, enter configuration mode (or (config)) and then switch to line configuration mode ((config-line)), by issuing the following commands:
Note: Notice that the prompt changes to reflect the current mode.
Step 2. Configure the password, and enable password checking at login.
Step 3. Step 3. Exit configuration mode.
Note: Do not save your configuration changes until your ability to log in has been verified.
Step 4. Verify the configuration.
Examine the configuration of the router to make sure that the commands have been properly entered, by issuing the show running-config command.
Test the configuration by making a Telnet connection to the router.
This can be done by connecting from a different host on the network, but you can also do so 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.
Step 5. Save your configuration.
Follow these steps to configure Auxiliary (AUX) port passwords.
Note: before performing this test, ensure that you have an alternate connection into the router, such as console or Telnet, in case there is a problem logging back in to the router.
Step 1. From the privileged EXEC (or enable) prompt, enter configuration mode ((config)) and then switch to line configuration mode ((config-line)), by issuing the following commands:
Note: Notice that the prompt changes to reflect the current mode.
Step 2. Configure the password, and enable password checking at login.
Step 3. Exit configuration mode.
Note: Do not save your configuration changes until your ability to log in has been verified.
Step 4. Verify the configuration. Examine the configuration of the router to make sure that the commands have been properly entered by issuing the show running-config command. Test the configuration by making an inbound or outbound connection to the line.
Step 5. Save your configuration.
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 in to the router.
Step 1. From the privileged EXEC (enable) prompt, enter configuration mode ((config)) and then switch to line configuration mode ((config-line), by issuing the following commands:
Note: Notice that the prompt changes to reflect the current mode.
router#conf t !--- Enter configuration commands, one per line. End with CNTL/Z. router(config)#line con 0 router(config-line)#
Step 2. Configure the password, and enable password checking at login.
router(config-line)#passwordrouter(config-line)#login
Step 3. Exit configuration mode.
router(config-line)#end router# %SYS-5-CONFIG_I: Configured from console by console
Note: Do not save your configuration changes until your ability to log in has been verified.
Step 4. Verify the configuration.
Examine the configuration of the router to make sure that the commands have been properly entered by issuing the show running-config command.
To test the configuration, log off the console with the exit command and log in again, using the configured password to access the router.
router#exit router con0 is now available Press RETURN to get started.
Step 5. Save your configuration.
router#write memory
Perform these steps to configure Telnet passwords.
Note: Before performing this test, ensure that you have an alternate connection into the router, such as console or dial-in, in case there is a problem logging back in to the router.
Step 1. From the privileged EXEC (or enable) prompt, enter configuration mode (or (config)) and then switch to line configuration mode ((config-line)), by issuing the following commands:
Note: Notice that the prompt changes to reflect the current mode.
router#conf t !--- Enter configuration commands, one per line. End with CNTL/Z. router(config)#line vty 0 4 router(config-line)#
Step 2. Configure the password, and enable password checking at login.
router(config-line)#passwordrouter(config-line)#login
Step 3. Step 3. Exit configuration mode.
router(config-line)#end router# %SYS-5-CONFIG_I: Configured from console by console
Note: Do not save your configuration changes until your ability to log in has been verified.
Step 4. Verify the configuration.
Examine the configuration of the router to make sure that the commands have been properly entered, by issuing the show running-config command.
Test the configuration by making a Telnet connection to the router.
This can be done by connecting from a different host on the network, but you can also do so 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.
router#telnet
Step 5. Save your configuration.
router#write memory
Follow these steps to configure Auxiliary (AUX) port passwords.
Note: before performing this test, ensure that you have an alternate connection into the router, such as console or Telnet, in case there is a problem logging back in to the router.
Step 1. From the privileged EXEC (or enable) prompt, enter configuration mode ((config)) and then switch to line configuration mode ((config-line)), by issuing the following commands:
Note: Notice that the prompt changes to reflect the current mode.
router#conf t !--- Enter configuration commands, one per line. End with CNTL/Z. router(config)#line aux 0 router(config-line)#
Step 2. Configure the password, and enable password checking at login.
router(config-line)#passwordrouter(config-line)#login
Step 3. Exit configuration mode.
router(config-line)#end router# %SYS-5-CONFIG_I: Configured from console by console
Note: Do not save your configuration changes until your ability to log in has been verified.
Step 4. Verify the configuration. Examine the configuration of the router to make sure that the commands have been properly entered by issuing the show running-config command. Test the configuration by making an inbound or outbound connection to the line.
Step 5. Save your configuration.
router#write memory
Thursday, April 18, 2013
Upgrading ConfigMgr 2012 from Evaluation version (Enter SCCM 2012 License Key)
In System Center 2012 Configuration Manager it is really easy to upgrade an installation that was made using the Evaluation option when you installed it to a fully licensed installation by simply entering the Product key.
It is done by using the “Configuration Manager Setup” which can be found on the Start menu or by simply running install from the installation source.
When the setup starts select the “Perform sitemaintenance or reset this Site” in the following wizard you can convert the installation from an evaluation to a fully licensed installation.
Here is a step-by-step guide:
3. Then you get the option to “Convert from Evaluation to Full Product Version. Enter your 25-character product key:”
4. In the next screen accept the license agreement
5. Finished!
It is done by using the “Configuration Manager Setup” which can be found on the Start menu or by simply running install from the installation source.
When the setup starts select the “Perform site
Here is a step-by-step guide:
- Start Configuration Manager Setup either from the start menu or the installation source.
- Select the “Perform
site maintenance or reset Site” option
3. Then you get the option to “Convert from Evaluation to Full Product Version. Enter your 25-character product key:”
4. In the next screen accept the license agreement
5. Finished!
- Then you get the option to “Convert from Evaluation to Full Product Version. Enter your 25-character product key:”
Tuesday, March 19, 2013
How to uninstall Reporting Services on SQL 2008 R2?
From SQL Server Reporting Services(SSRS) 2008, the SSRS is Internet Information Server(IIS) independence. This means there is no directory for Reporting Services under IIS.
In this case, please make sure the SSRS service is running, otherwise, we are not able to configure the Web Service URL and the Report Manager URL(means configuring the virtual directories).
Anyway, in order to uninstall SQL Server Reporting Services without uninstalling other SQL Server components, please follow this guide:
In this case, please make sure the SSRS service is running, otherwise, we are not able to configure the Web Service URL and the Report Manager URL(means configuring the virtual directories).
Anyway, in order to uninstall SQL Server Reporting Services without uninstalling other SQL Server components, please follow this guide:
- In Add/Remove programs
- Click the 'Uninstall/Change' button for "SQL Server 2008 R2"
- In the coming dialog, click 'Remove'
- Click 'OK'
- In the 'Select Instance' dialog, select the appropriate instance, and then click 'Next'
- In the 'Select Features' dialog, please only select 'Reporting Services'
- Then click 'Next' and 'Next' till the uninstalling process starting
Thursday, March 14, 2013
DHCP on VLAN
Switch>enable
Switch#conf t
Switch(config)#vlan 200
Switch(config-vlan)#name TEST_VLAN
Switch(config-vlan)#exit
Switch#conf t
Switch(config)#vlan 200
Switch(config-vlan)#name TEST_VLAN
Switch(config-vlan)#exit
Switch(config)#int fa0/1
Switch(config-if)#switchport mode
access
Switch(config-if)#switchport
access vlan 200
Switch(config-if)#exit
Switch(config)#int fa0/2
Switch(config-if)#switchport mode
access
Switch(config-if)#switchport
access vlan 200
Switch(config-if)#exit
Switch(config)#int vlan 200
Switch(config-if)#ip address 192.168.200.1 255.255.255.0
Switch(config-if)#description DHCP_POOL_4TEST
Switch(config-if)#exit
Switch(config-if)#ip address 192.168.200.1 255.255.255.0
Switch(config-if)#description DHCP_POOL_4TEST
Switch(config-if)#exit
Switch(config)#ip routing
Switch(config)#ip dhcp pool vlan200
Switch(config)#ip dhcp pool vlan200
Switch(dhcp-config)#network
192.168.200.0 255.255.255.0
Switch(dhcp-config)#default-router
192.168.200.1
Switch(dhcp-config)#exit
Switch(config)#ip dhcp
excluded-address 192.168.200.1
Switch(config)#exit
Wednesday, March 6, 2013
Copy files to desktop in SCCM 2012
Copy files to desktop in SCCM 2012
1.
Create a parent folder in your source file
repository (I created DesktopTools).
2.
Create a sub-folder in the folder just created
called Files2Copy and place the files you are going to copy to desktop in this
folder.
if not exist "%1" md "%1"
copy /y "%~dp0Files2Copy\*.*" "%1"
3.
Create a batch file called filecopy.bat (if you’re
not sure how to create a batch file here’s a quick instructions - A. open
notepad and copy paste those 2 lines in below B. save as then point to the
DesktopTools folder, name it filecopy.bat) with the below two lines and place
it in the parent directory created in step 1. This batch file will create a
folder specified on the command-line (if it doesn’t already exist) and copy the
files from the Files2Copy folder into it.
So it should looks like below
4.
Create a package in SCCM 2012 using the parent
directory created in step 1 as the source file location
a) Open SCCM 2012 console=> Software Library => Application management => Right click Packages => Create Package =>
a) Open SCCM 2012 console=> Software Library => Application management => Right click Packages => Create Package =>
5.
6.
7.
8.
The rest of screens are default so just Next,
Next , & Close.
9.
Right click on the “Desktop Tools” package=>
Distribute Content => Add the selection point. Then ext.
10.
Right click on the “Desktop Tools” package=>
Deploy => Collection – just browse to one you would like to advertise to
then Next => You can make it available or required, in my case I chose
required because the files/shortcut must be copied to newly deployed laptops/desktops.
11.
Assignment schedule I made it As soon as
possible.
12.
The rest of screens are default so just Next,
Next Close.
13.
Done
Tuesday, March 5, 2013
Deploy SQL Server 2008 R2 Native Client x64 via SCCM 2012
1. Created application in SCCM 2012 with the MSI
2. Right click properties and select "Deployment Types" tab
3. click on highlight the MSI package and click edit
4. In the Program tab
5. Installation program: added the line " IACCEPTSQLNCLILICENSETERMS=YES" so should looks like this
msiexec /i "sqlncli_X64(2008 R2).msi" /q IACCEPTSQLNCLILICENSETERMS=YES
2. Right click properties and select "Deployment Types" tab
3. click on highlight the MSI package and click edit
4. In the Program tab
5. Installation program: added the line " IACCEPTSQLNCLILICENSETERMS=YES" so should looks like this
msiexec /i "sqlncli_X64(2008 R2).msi" /q IACCEPTSQLNCLILICENSETERMS=YES
Subscribe to:
Posts (Atom)



















