In Exchange 2010/2007, these tasks remain the same. However, instead of using ADUC to accomplish them, you use the EMC or the Shell (aka “EMS“). The new term for a Contact is MailContact.
Create a MailContactCreate a MailContact using the EMC:
Alternatively, use the Shell to create a new MailContact:
New-MailContact -Name “Foo User” -ExternalEmailAddress “foo@externaldomain.com
Next, we set the recipient’s Delivery Options to deliver to the alternate recipient.
Forward mail for a recipient to the MailContactNow that we have a MailContact created for the external recipient’s email address, we can forward mail for the Exchange recipient to the MailContact. To configure mail forwarding using the EMC:
To configure mail forwarding using the Shell:
Set-Mailbox “Joe Adams” -ForwardingAddress “foo@externaldomain.com”
To deliver a copy to the mailbox (in addition to the external email address – equivalent of step 4 above):
Set-Mailbox “Joe Adams” -ForwardingAddress “foo@externaldomain.com” -DeliverToMailboxAndForward $true
This command lists mailboxes with auto forwarding enabled:
Get-Mailbox | where {$_.ForwardingAddress -ne $null} | ft name,forwardingaddress
Remote Domains define a bunch of settings, such as message formats, character sets, and OOFS for messages sent to specified domains outside your Exchange organization. The default Remote Domain setting for the address space * (the asterisk character) applies to all external domains except the ones for which you’ve created a Remote Domain for.
Figure 3: The Allow automatic forward setting for remote domains only impacts client-side automatic forwarding using mechanisms like Inbox Rules, and is disabled by default.
The Allow automatic forward setting for remote domains applies only to client-side forwarding using mechanisms like Inbox Rules. For instance, if a user creates a rule in Microsoft Outlook to automatically forward mail to an external email address, the default setting (for address space *) doesn’t allow it. To enable automatic client-side forwarding of mail to external addresses, select the Allow automatic forward checkbox in a remote domain’s properties | Format of original message sent as attachment to journal report tab (Yes, in Exchange 2007 the tab is mislabeled. It is the “Message Formats” tab… 🙂.
Sometime in terminal server you don’t have mail applet in control panel. You can create profile using method below.
c:\Program Files (x86)\Microsoft Office\Office14\outlook.exe /profile nameofprofile
—
To Reset Outlook 2010 to First Run Settings
1. Use the command line switch /profile xxx
2. Outlook will report that there is no such profile and prompt for another.
3. Click “New” and name a new profile.
4. Presto! Go ahead and enter your new mail account settings under the newly created profile.
5. One more step: using the command line switch /profiles open start Outlook and select your new profile as the default by expanding Options and selecting “Set as default”
Shrew Soft have a Mac OSX port of the VPN client based on the head ( 2.2.x ) sources. It seems that it requires more testing, but it appears to be more or less stable.
There are two requirements / dependency before running the native install package (.dmg file)
1) Install the LGPL Qt Framework for Mac OSX.
http://files.linux-addicted.net/qtproject/archive/qt/4.7/qt-mac-opensource-4.7.1.dmg
2) Install the current release of the TUN/TAP driver for Mac OSX.
http://tuntaposx.sourceforge.net/download.xhtml
3. The finally, install the Shrew Soft VPN client.
http://www.shrew.net/download/vpn/vpn-client-install.dmg
You should now find the VPN Access manager in the Application folder. This have been tested to work on Lion and Mountain Lion.
When setting up a VPN, you can run into problems with VPN pass through. If you are using a Virgin Media SuperHub you have the added challenge that is by default, your speedy SuperHub will block outgoing VPN traffic meaning that with all the correct details it just doesn’t work. To fix this, just follow the below steps:
This allows the traffic through for VPN authentication and should now allow your VPN to connect as normal.
Lync Server 2013 Role: Lync Edge
Base Operating System: Windows Server 2012
You attempt to start your Lync Server 2013’s Edge server’s Lync Server Access Edge service but notice that the service fails with the following message:
Windows could not start the Lync Server Access Edge on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to the service-specific error code -2146762487.
Solution
Check Event Log
Reviewing the System logs on the Edge server show event ID 7024 errors logged:
The Lync Server Access Edge service terminated with the following service-specific error: A Certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
Download the certificate root server certificate for your Access Edge Server, I used GoDaddy cert for my Edge server so from the link below I have downloaded the root server certificate, and this resolved the issue.
Adjusting Mail Mark As Read Behavior from the Command Line
Launch the Terminal
Set the delay to 2 seconds with the following: defaults write com.apple.Mail MarkAsReadDelay 2
Replace the two on the end with any number to change the delay to that many seconds.
You can also remove the delay with the following defaults write command: defaults write com.apple.Mail MarkAsReadDelay 0
Return to the default setting with the following defaults delete command: defaults delete com.apple.Mail MarkAsReadDelay
It is important to ensure the integrity of the image key itself before you load it on the Juniper Networks security device. You can confirm the image key’s integrity by comparing the checksum of the imagekey.cer certificate file to the value below. A tool such as md5sum, sha1sum, andsha256sum for Unix/Linux can be used.
$ md5sum imagekey.cer 99def4b80b75ed65aad52a5fc3ed1131 imagekey.cer $ sha1sum imagekey.cer 06c3c15b88de548b18814d4389d18a20f65a5845 imagekey.cer $ sha256sum imagekey.cer 02b107f0679bc5d5aa0ab49be52043bb31f2a010a980573c53dc3fc815e1d7f3 imagekey.cer
$ md5sum imagekey.cer ccfcd027e20c9cc38b5d8dac17c7199f imagekey.cer $ sha1sum imagekey.cer 2af0d97abbb58821650445cd517050fd0cfa2684 imagekey.cer $ sha256sum imagekey.cer bab2f722cbba13a73d9af4c17af9c34d62ac71b4c9e8bbb9bac5df1fdceb0261 imagekey.cer
There are no code or contents changes on the newly released boot loaders and ScreenOS firmwares, these files are signed with the new image key only. Therefore, the version numbers are same as before.
In order to distinguish whether the device is running with old ScreenOS firmware that is signed with the old image key, you can check the non-zero values of the image key using hidden CLI exec pki test skey command. Refer to 2. Checking the Installed Image Key. Also you can refer to KB29296 – ScreenOS and Boot Loader Checksum Values Signed by Old and New Image Key.
Finally when you feel confident about the integrity of the new image key and know that the currently running ScreenOS firmware is signed by the old image key, you can follow the below steps to install the new image key, and boot loader/ScreenOS firmware that are signed with the new image key.
Before you proceed the following steps, please make sure to backup the configuration, you can do it through either the WebUI and the CLI.
On the WebUI, navigate to Configuration > Update > Config File > click “Save to File”
On the CLI, type save config to tftp <IP address of TFTP server> <config filename>
SSG550-> save config to tftp 172.22.152.251 ssg550_config_backup Read the current config. Save configurations (3064 bytes) to ssg550_config_backup on TFTP server 172.22.152.251. !!!!!!!!!!!!!! tftp transferred records = 6 tftp success! TFTP Succeeded
If an image key is already installed, you will see output similar to the below (non-zero values). If the output shows all zero (0), then there is no installed image key.
NOTE: The device cannot store more than one image key. When you install the new image key, it overwrites the previous key. The installation status of the image key can be checked through hidden CLI exec pki test skey command only.
SSG550-> exec pki test skey (snip) KEY1 N/A len =432 308201ac02010002818100fd7f53811d75122952df4a9c2eece4e7f611b7523cef4400c31e3f80b651 magic1 = f7e9294b magic2=0 KEY2 N/A len =432 308201ac02010002818100fd7f53811d75122952df4a9c2eece4e7f611b7523cef4400c31e3f80b651 magic1 = f7e9294b magic2=0 KEY3 N/A len =432 308201ac02010002818100fd7f53811d75122952df4a9c2eece4e7f611b7523cef4400c31e3f80b651 magic1 = f7e9294b magic2=0
NOTE: The above non-zero values are indicating the old image key (308201ac ….). If you wish to update the image key to the new key, then go to next step 3. Updating the Image Key. The new image key’s values are starting with (308201ad ….) from left to right direction. If the new image key is installed already, then go to step 4. Upgrading ScreenOS.
The following example shows that an image key is not installed (all zero values).
SSG550-> exec pki test skey (snip) KEY1 N/A len =0 0000000000000000000000000000000000000000000000000000000000000000000000000000000000 magic1 = f7e9294b magic2=dead1234 KEY2 N/A len =0 0000000000000000000000000000000000000000000000000000000000000000000000000000000000 magic1 = f7e9294b magic2=dead1234 KEY3 N/A len =0 0000000000000000000000000000000000000000000000000000000000000000000000000000000000 magic1 = f7e9294b magic2=dead1234
NOTE: If no image key is installed and you do not want to authenticate the boot loader (for ISG Series and NetScreen Series only) and ScreenOS in future, skip Step 3. Updating the Image Key.
If a WebUI access or a TFTP server is available, you can install the new image key through the WebUI or the CLI.
On the WebUI :
On the CLI :
SSG550-> save image-key tftp 172.22.152.251 new/imagekey.cer Load file from TFTP 172.22.152.251 (file: new/imagekey.cer). !!!!! tftp received octets = 863 tftp success! Done TFTP Succeeded
If the image key is installed successfully, you will see output similar to the below (non-zero values). If the output shows all zero (0), then the image key is not installed.
SSG550-> exec pki test skey (snip) KEY1 N/A len =433 308201ad02010002818100fd7f53811d75122952df4a9c2eece4e7f611b7523cef4400c31e3f80b651 magic1 = f7e9294b magic2=0 KEY2 N/A len =433 308201ad02010002818100fd7f53811d75122952df4a9c2eece4e7f611b7523cef4400c31e3f80b651 magic1 = f7e9294b magic2=0 KEY3 N/A len =433 308201ad02010002818100fd7f53811d75122952df4a9c2eece4e7f611b7523cef4400c31e3f80b651 magic1 = f7e9294b magic2=0
If only a CLI access is available without TFTP server, you cannot install the new image key, then delete the installed old image key using CLI delete crypto auth-key command and go to next step 4. Upgrading ScreenOS.
The following example shows that no image key is available after deleting the image key.
SSG550-> delete crypto auth-key SSG550-> exec pki test skey (snip) KEY1 N/A len =0 0000000000000000000000000000000000000000000000000000000000000000000000000000000000 magic1 = f7e9294b magic2=0 KEY2 N/A len =0 0000000000000000000000000000000000000000000000000000000000000000000000000000000000 magic1 = f7e9294b magic2=0 KEY3 N/A len =0 0000000000000000000000000000000000000000000000000000000000000000000000000000000000 magic1 = f7e9294b magic2=0
NOTE: Please do not execute CLI delete crypto file command. It will delete all crypto files in the device that might be used for other services.
NOTE: You cannot delete image key through WebUI.
On ISG1000/2000, NS5200/NS5400 (boot loader upgrade is required) :
You must have a console connection and a TFTP server that can be reachable through the ‘mgt’ interface because the device will prompt you to install a boot loader if it cannot authenticate the installed boot loader using the new image key.
While the device boots up, it checks the integrity of installed boot loader and ScreenOS firmware.
NOTE: If the old image key is deleted using CLI delete crypto auth-key command, the device skips integrity check of the boot loader and ScreenOS firmware while boots up. You will see Ignore image authentication! message on the console while the device boots up.
On the CLI :
ns5200-> save software from tftp 172.22.152.251 new/ns5000.6.3.0-M2A.r17.0 to flash Load software from TFTP 172.22.152.251 (file: new/ns5000.6.3.0-M2A.r17.0). !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! (snip) tftp received octets = 13541072 tftp success! TFTP Succeeded Save to flash. It may take a few minutes ...platform = 15, cpu = 16, version = 18 update new flash image (04243150,13541072) platform = 15, cpu = 16, version = 18 offset = 20, address = 4000000, size = 13540994 date = 71c0efb8, sw_version = 71c0efbc, cksum = c491f61c Image authenticated! Program flash (13541072 bytes) ... ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++done Done
NOTE: While the device boots up, it will generate the following messages on the console to guide you to install the boot loader that is signed by the new image key.
ns5200-> reset
System reset, are you sure? y/[n] y
In reset ...
Juniper Networks NS-5000-II BootROM Version 1.0.0 (Checksum: FE499CCD)
Copyright (c) 1998-2004 Juniper Networks, Inc.
Total physical memory: 2048MB
Test - Pass
Initialization................ Done
Hit key 'X' and 'A' sequentially to update OS Loader....
Loading OS Loader from on-board flash memory... ++++
Done!
********Invalid DSA signature <- The installed boot loader (OS Loader) cannot be authenticated using the new image key
********Bogus image - not authenticated
OS Loader File Name [new/ns5000.6.3.0-M2A.r17.0]: new/Load5000v104.d <- Boot loader file signed with the new image key
Self IP Address [172.19.50.252]: 172.22.152.49
TFTP IP Address [172.19.50.129]: 172.22.152.251
Save loader config (56 bytes)... Done
Loading file "new/Load5000v104.d"...
(snip)
Loaded successfully! (size = 447,576 bytes)
Image authenticated! <- Boot loader is authenticated using the new image key
Program OS Loader to on-board flash memory... ++++
Done!
Start loading...
....................
Done.
Juniper Networks NS-5000-II OS Loader Version 1.0.4
Initialize FBTL 0.. Done
Hit any key to load new firmware
Hit any key to load new firmware
Hit any key to load new firmware
Hit any key to load new firmware
Loading default system image from on-board flash disk...
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Done! (size = 13,631,488 bytes)
Image authenticated! <- ScreenOS firmware is authenticated using the new image key
Start loading...
(snip)
Done.
Configuring Imperial FPGA... Done
Juniper Networks, Inc
NS-5000 System Software
Copyright, 1997-2008
Version 6.3.0r17.0
(snip)
NOTE: After the device boots up successfully, you can check the version of the installed boot loader through the CLI get system command, look for the value of “OS Loader Version”.
ns5200-> get system Product Name: NetScreen-5200-II Serial Number: 0040012001000011, Control Number: 00000000 Hardware Version: 3010(0)-(04), FPGA checksum: 00000000, VLAN1 IP (0.0.0.0) Software Version: 6.3.0r17.0, Type: Firewall+VPN BOOT ROM Version: 1.0.0 OS Loader Version: 1.0.4 (snip)
On SSG 20/140/320M/350M/520/520M/550/550M :
It is not required to update the current boot loader because the integrity check of the boot loader is only done during the installation of a boot loader. During boot-up of the device there is no integrity check done for the boot loader using the image key. Therefore the existing boot loader on the SSG device will keep working correctly after updating the image key on the device.
NOTE: If the old image key is deleted using CLI delete crypto auth-key command, the device skips the integrity check of the ScreenOS firmware while the device boots up. You will see the Ignore image authentication! message on the console while the device boots up.
On the WebUI :
NOTE: If the device has the old image key and you try to install a ScreenOS firmware image that is signed by the new image key, the installation process will stop because the ScreenOS firmware cannot be authenticated using the old image key. You will see a pop-up window displaying “Firmware update failed”. In this case, you need to either install the new image key prior to installing the new ScreenOS firmware or delete the image key (refer to the above step 3. Updating the Image Key).
On the CLI :
SSG550-> save software from tftp 172.22.152.251 new/ssg500.6.3.0r17.0 to flash Load software from TFTP 172.22.152.251 (file: new/ssg500.6.3.0r17.0). !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! (snip) tftp received octets = 11627247 tftp success! TFTP Succeeded Save to flash. It may take a few minutes ...platform = 23, cpu = 11, version = 2 update new flash image (02572fd0,11627247) platform = 23, cpu = 11, version = 2 offset = 20, address = 0, size = 11627169 date = 9422, sw_version = 808031, cksum = 954806c3 Program flash (11627247 bytes) ... (snip)
NOTE: If the ScreenOS firmware is not successfully authenticated by the new image key during installation, the error messages “Invalid image!!!” and “Bogus image – not authenticated!!!” will be displayed. When the upgrade went successfully, on the next reboot the device will show ”Image authenticated!”on the console.
SSG550-> reset
System reset, are you sure? y/[n] y
In reset ...
(snip)
ScreenOS Saipanloader V1.0.7
Built Mar 19 2009/15:54:12
watchdog_probe, 1132 bus/dev/fn = 0/248 ich = 2640
boot_drive = 80
start1 = 0768, start2 = 3840
Hit 'X' and 'A' to upgrade bootloadermounting FAT16 partition
file size = 112
size = 112, sizeof(nvram_rec) = 112
Hit any key to load new firmware
Hit any key to load new firmware
Hit any key to load new firmware
Hit any key to load new firmware/$nsboot$.bin
file size = 11627247
hdr->magic_number = 81ba16ee, hdr->platform_type = 1700, hdr->cpu_type = 11
Image authenticated!
(snip)
NOTE: If the device has the old image key and you try to install ScreenOS firmware that is signed with the new image key, the installation process will stop because the ScreenOS firmware cannot be authenticated using the old image key. You will see output similar to the below. In this case, you need to either install the new image key prior to installing the ScreenOS firmware or delete the image key (refer to the above step 3. Updating the Image Key).
SSG550-> save software from tftp 172.22.152.251 new/ssg500.6.3.0r17.0 to flash
Load software from TFTP 172.22.152.251 (file: new/ssg500.6.3.0r17.0).
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
(snip)
tftp received octets = 11627247
tftp success!
TFTP Succeeded
Save to flash. It may take a few minutes ...platform = 23, cpu = 11, version = 2
update new flash image (02572fd0,11627247)
platform = 23, cpu = 11, version = 2
offset = 20, address = 0, size = 11627169
date = 9422, sw_version = 808031, cksum = 954806c3
********Invalid image!!! ********Bogus image - not authenticated!!!
(snip)
NOTE: If you would like to update the boot loader that is signed with the new image key on SSG Series, you must have a console connection and a TFTP server that can be reachable through the pre-assigned interface(s) in the boot loader mode (mostly ‘eth0/0’ interface) and manually interrupt the boot sequence by holding ‘Shift key’ and hit ‘X‘ and ‘A’ sequentially when the “Hit ‘X’ and ‘A’ to upgrade bootloader” message is shown on the console.
SSG550-> reset System reset, are you sure? y/[n] y In reset ... (snip) ScreenOS Saipanloader V1.0.7 Built Mar 19 2009/15:54:12 watchdog_probe, 1132 bus/dev/fn = 0/248 ich = 2640 boot_drive = 80 start1 = 0768, start2 = 3840 Hit 'X' and 'A' to upgrade bootloader <- Hold ‘Shift key’ and hit ‘X’ and ‘A’ in sequence Loader File Name:new/Loadssg500v107.d <- Bootloader filename signed with the new image key Self IP Address :172.22.152.35 <- TFTP client IP address TFTP IP Address :172.22.152.251 <- TFTP server IP address IP MASK :255.255.255.0 Gateway IP Address :172.22.152.1 Saipan motherboard proto 3 or later detected Probing...[Ethernet0/0 and Ethernet0/1] Initiating hardware and waiting for link up ... Initiating hardware and waiting for link up ... self_ip = 172.22.152.35, tftp_server_ip = 172.22.152.251 ip = 172.22.152.35 mask = 255.255.255.0 gw = 172.22.152.1 svr = 172.22.152.251 network_ready = 1 new/Loadssg500v107.d 121078 bytes downloaded from tftp server old img size = 121032, new img size = 121032, load = 121078, sig = 46 S Image authenticated! <- Bootloader is authenticated using the new image key mounting FAT12 partition file /boot2 size was 121079, new size is 121078 getting sector information boot1 size = 512 boot2 size = 512 boot1_sector = 807, boot2_sector = 1051 offset = 512 [1052][1053][1054][1055][1056][1057][1058][1059][1060][1061][1062][1063][1064][1065][1066][1067][1068][1069][1070][1071][1072][1073][1074][1075][1076][1077][1078][1079][1080][1081][1082][1083][1084][1085][1086][1087][1088][1089][1090][1091][1092][1093][1094][1095][1096][1097][1098][1099][1100][1101][1102][1103][1104][1105][1106][1107][1108][1109][1110][1111][1112][1113][1114][1115][1116][1117][1118][1119][1120][1121][1122][1123][1124][1125][1126][1127][1128][1129][1130][1131][1132][1133][1134][1135][1136][1137][1138][1139][1140][1141][1142][1143][1144][1145][1146][1147][1148][1149][1150][1151][1152][1153][1154][1155][1156][1157][1158][1159][1160][1161][1162][1163][1164][1165][1166][1167][1168][1169][1170][1171][1172][1173][1174][1175][1176][1177][1178][1179][1180][1181][1182][1183][1184][1185][1186][1187][1188][1189][1190][1191][1192][1193][1194][1195][1196][1197][1198][1199][1200][1201][1202][1203][1204][1205][1206][1207][1208][1209][1210][1211][1212][1213][1214][1215][1216][1217][1218][1219][1220][1221][1222][1223][1224][1225][1226][1227][1228][1229][1230][1231][1232][1233][1234][1235][1236][1237][1238][1239][1240][1241][1242][1243][1244][1245][1246][1247][1248][1249][1250][1251][1252][1253][1254][1255][1256][1257][1258][1259][1260][1261][1262][1263][1264][1265][1266][1267][1268][1269][1270][1271][1272][1273][1274][1275][1276][1277][1278][1279][1280][1281][1282][1283][1284][1285][1286][1287][1288][1289][1290] write boot2's start sector back at sector 1051 write mbr back at sector 0 mounting FAT16 partition file size = 112 size = 112, sizeof(nvram_rec) = 112 system rebooting... <- After successful bootloader installation, the device will automatically try to reboot (snip) ********Invalid DSA signature <- But if the previously installed ScreenOS firmware is signed with the old image key, the new image key cannot authenticate the ScreenOS firmware, then the device prompt to you install a ScreenOS firmware signed with the new image key ********Bogus image - not authenticated mounting FAT16 partition file size = 112 Serial Number []: READ ONLYc) = 112 BOM Version Number []: READ ONLY Self MAC Address [0000-0000-0000]: READ ONLYip = 1.1.1.1 svr = 1.1.1.2 self_ip_buf = 1.1.1.1, tftp_ip_buf = 1.1.1.2 Firmware File Name [old/ssg500.6.3.0r17.0]: new/ssg500.6.3.0r17.0 <- Type the ScreenOS firmware filename signed with the new image key Self IP Address [1.1.1.1]: 172.22.152.35 <- TFTP client IP address TFTP IP Address [1.1.1.2]: 172.22.152.251 <- TFTP server IP address IP MASK [255.255.255.0]: Gateway IP Address [172.22.152.251]: Save loader config (112 bytes)... Done Saipan motherboard proto 3 or later detected Probing...[Ethernet0/0 and Ethernet0/1] Initiating hardware and waiting for link up ... self_ip = 172.22.152.35, tftp_server_ip = 172.22.152.251 ip = 172.22.152.35 mask = 255.255.255.0 gw = 172.22.152.251 svr = 172.22.152.251 network_ready = 1 new/ssg500.6.3.0r17.0 offset = 0, maxposition = 11627247 11627247 bytes downloaded from tftp server hdr->magic_number = 81ba16ee, hdr->platform_type = 1700, hdr->cpu_type = 11 Image authenticated! ← ScreenOS is authenticated Save to on-board flash disk? (y/[n]/m) No <- You should press ‘n’ key Run downloaded system image? ([y]/n) Yes <- You should press ‘y’ key (snip) System change state to Active(1) login:
Untitled. (The Terminal command used here assumes the drive is named Untitled.) Also, make sure the Yosemite installer, called Install OS X Yosemite.app, is in its default location in your main Applications folder (/Applications). This means that if you moved it before installing Yosemite, you need to move it back before making your installer disk.sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction
You now have a bootable Yosemite install drive.
SA-MAIN:~ shiraj$
SA-MAIN:~ shiraj$ sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/OSX --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction
WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type "man sudo" for more information.
To proceed, enter your password, or type Ctrl-C to abort.
Password:
Erasing Disk: 0%... 10%... 20%... 30%...100%...
Copying installer files to disk...
Copy complete.
Making disk bootable...
Copying boot files...
Copy complete.
Done.
SA-MAIN:~ shiraj$
Follow these steps in order to recover your password:
Use these terminal settings:
Refer to these documents for information on how to cable and connect a terminal to the console port or the AUX port:
Note: The configuration register is usually set to 0x2102 or 0x102. If you can no longer access the router (because of a lost login or TACACS password), you can safely assume that your configuration register is set to 0x2102.
Important Notes:
If the break sequence does not work, refer to Standard Break Key Sequence Combinations During Password Recovery for other key combinations.
This step bypasses the startup configuration where the passwords are stored.
The router reboots, but ignores the saved configuration.
You are in enable mode and should see the Router# prompt.
Important: Do not type copy running-config startup-config or write. These commands erase your startup configuration.
The show running-config command shows the configuration of the router. In this configuration, the shutdown command appears under all interfaces, which indicates all interfaces are currently shut down. In addition, the passwords (enable password, enable secret, vty, console passwords) are in either an encrypted or unencrypted format. You can reuse unencrypted passwords. You must change encrypted passwords to a new password.
The hostname(config)# prompt appears.
hostname(config)#enable secret cisco
If you issue a show ip interface brief command, every interface that you want to use should display up up.
hostname(config)#config-register 0x2102
The hostname# prompt appears.
This brief tutorial will show you how to configure NAT overload or how to enable Internet access to multiple PCs of your LAN using only one public IP address. This type of NAT can easily be used at home when you have a Cisco 800 series xDSL router.
The first step is to define the addresses that will need to be NAT’d. This is done using a standard access-list:
access-list 1 permit your_lan_address_range
Example: access-list 1 permit 192.168.1.0
Now that we have defined the addresses that are allowed to use the NAT address, we will enable the actual NAT:
ip nat inside source list access-list number interface overload
Example: ip nat inside source list 1 dialer0 overload
This command states that it will use the addresses from the access-list we defined in Step 1 and NAT it to the Public IP address on the interface (e.g., serial 0, dialer 0, ethernet 1). The overload keyword specifies that multiple LAN addresses can be NAT’d to that address. The router uses the TCP and UDP ports of the hosts [LAN addresses] to translate the public IP address back to the originating local host address.
The last steps we need to configure are to tell the router which are our inside and outside addresses. This is achieved using the following commands:
For the inside
conf t interface ethernet | fastethernet number
ip nat inside
For the outside (assume we are dealing with an xDSL router)
conf t interface dialer0
ip nat outside
Now that NAT is configured, we can check to see which addresses are being used by using the show ip nat translations commands.