Forwarding messages from outlook to gmail

I have been asked to help some one to forward all his mail messages from Outlook exchange account to his Gmail folder.
So to achieve that you need to open your outlook.
Go to Tools->Rules and Alerts…

Then you need to create a new rule. in the window that popped up you click on the new rule button.

Then you get the rule window with templates in it.
Click on next and you get the default rule that you are about to customize.
Change the marked item in the list of “Step 1:” to “through the specified account”

Click on the first link in the “Step 2:” box.

Select the account you want to forward

Click on OK.
Then click on next and change the selection to “forward it to people or distribution list”

Go to “Step 2:” and click on the second link
In the window that opens type the email account you want to forward it to

Now click on OK and Finish.
That is it. test the forward with an email self addressed.

Configure SquidGuard-Example

This summary is not available. Please click here to view the post.

Traceroute through Cisco ASA Firewall

To allow inside hosts to be visible to outside hosts use following:

access-list OUTSIDE-IN extended permit icmp any any echo

Following lines will make inside hosts visible to outside using taceroute:

access-list OUTSIDE-IN extended permit icmp any any echo-reply
access-list OUTSIDE-IN extended permit icmp any any source-quench
access-list OUTSIDE-IN extended permit icmp any any time-exceeded

Service policy on the firewall also needs to be updated to inspect ICMP traffic

policy-map global_policy
class inspection_default

set connection decrement-ttl

inspect icmp
inspect icmp error

 

Add Access-list to access-group

access-group OUTSIDE-IN in interface outside

How to play song in Hole Mode PABX TD1232(SMC)

Connect main phone to with PABX TD1232
===============================
Connect Audio cable to Music2 on PABX TD1232
====================================

On main phone: Press  Program ==> *#1234567

Press code: 803

Click: SP-Phone = Enter

Select : Hode = Music 2
Select : BGM = Music 2

=================

Step-by-Step Guide to Remote Assistance

Using Remote Assistance via saving a file

This section shows how to initiate a Remote Assistance invitation by saving the request as a file. This allows you to use Remote Assistance via Web-based e-mail such as Hotmail or other similar services.
In this scenario, user Jon Grande initiates the same request as explained above.

1. Jon clicks Start, clicks Help and Support, and under the Ask for assistance heading, he clicks Invite a friend to connect to your computer with Remote Assistance. The Remote Assistance page appears as shown in Figure 7 below.
   
   
   Figure 7: Inviting someone to help you
2. Jon clicks Invite someone to help you and selects Save Invitation as a file.
   
3. Jon enters his message and clicks Continue.
   
4. The Save File dialog box appears and Jon is prompted to save the file in his My Documents folder as shown in Figure 8 below.
   
   
   Figure 8: Saving the Remote Assistance file
5. Jon opens his Hotmail e-mail, attaches the file from his My Documents folder and sends the message to Cynthia Randall.
   
6. Cynthia opens Jon's message, saves the attached file to her My Documents folder and opens it. The Remote Assistance Invitation box appears as shown in Figure 9 below.
   
   
   Figure 9: Accepting the Remote Assistance request
7. Cynthia enters the password and clicks Yes.
   Note: Paul will have needed to let Cynthia know what the password is in a separate communication such as a phone call or secure e-mail. Typically, users should relay the password via a phone call.
   
8. The Attempting to Start Remote Assistance Session with Paul West box appears. Cynthia is able to begin Remote Assistance as explained in the previous example.
   

No Terminal Server Client access licenses

Solution:
- start>run>regedit>hkey_local_machine\software\microsoft\mslicensing......once here delete the mslicensing folder.

try to connect after deleting said folder...

Weldone :-)

How To: Transfer your PuTTY settings between computer

Putty stores its settings in the Windows registry. To save a backup of your Putty settings, you'll need to export this registry key to a file.

HKEY_CURRENT_USER\Software\SimonTatham

(Simon Tatham is the original developer responsible for PuTTy)

1. Click Start->Run and type "RegEdt32" in the "Open" dialog. Click "Ok"

2. One RegEdt32 starts, you'll be presented with an application which looks something like:

3. Press "Ctrl+F" to bring up the Find dialog. Enter the name of the key, "SimonTratham" in the "Find What" field, and make sure only "Keys" is checked in the "Look At" section of the dialog. Finally, click "Find Next"




4. The search may take a while, reminding us that the Windows Registry is a large and mysterious place where dragons be. Let's use these few seconds to reflect on the fact that you should never, ever, never change things in the registry unless you are absolutely, positively, totally, completely, 100% dead sure that you know exactly what you're doing. When the search completes we'll see the key name for which we're looking.



5. Click File->Export. Give your file an appropriate name like, "putty.reg" and click "Save"

6. We're done! Save the putty.reg file somewhere safe. The file doesn't contain any passwords or actual SSH key values so, it's relatively safe from prying eyes. Still, it does contain your configuration and that kind of data is a private matter.

Importing Your PuTTy Configuration

To import your saved PuTTy configuration on any other Windows computer simply copy your exported registry key, right click on the file and click "Merge"

Windows will ask you for confirmation that you want to import this set of registry values. We know this file is safe, because we created it but, you should never import registry information from an unknown source.

That's all you need to know about moving your PuTTy configuration from one machine to another. This can be really useful information when upgrading to a new PC or, if you're an office IT guy where your users all have a standard list of servers they need to connect via SSH, you can create a reference configuration on once machine and "share" it between every computer in the office.

End