sexta-feira, 19 de abril de 2013

How to add Printer manually in your Windows 7 Operating System computer?



There are two methods to Add Printer manually in your Windows 7 Operating System computer.

Method 1: How to install local printer in Windows 7 Operating System?


For installing local printer, you may follow the steps given below:

1. First, Click on the Start button in your screen, further click on Control Panel button and then double click on Devices and Printers button.
2. Then click on Add a Printer button in the menu.
3. Further select the Add a local printer button from the available menu.
4. Then choose an existing LPT port and click Next button .
5. Further select the correct driver from the driver list menu for your printer. Suppose if the requisite driver is not available then click on the Windows Update button. After the Windows 7 Update installation finishes in your computer, once again search for the appropriate driver for your printer.

Method 2: How to install network printer in Windows 7 Operating System?


The following are the steps for adding a shared printer in your Windows 7 Operating System computer:

1. First, click on the Start button in your screen, further, click on Control Panel button and then double click on Devices and Printers button.
2. Then click on Add a Printer button in the menu.
3. Further select the Add a local printer button from the next available menu.
4. Then select the Create a new port button in the menu. Further choose the Local Port button as the type of the port in the existing menu.
5. Then go to the box with title Enter a port name and then type the address in the following format:

\\[I.P. address of your host computer]\[Share Name of the printer in the computer][Please remove the - [] - and substitute it with - "<>" while actually doing it].
and then click Next button in the menu.

6. Go and select the appropriate driver for your printer from the driver list available there. In case of the required driver is not available, you may click on the Windows Update button for updating your Windows 7 Operating System. Soon after the update for Windows 7 Operating System finishes, you can once again search for the appropriate driver for your printer.
Reference www.microsoft.com

segunda-feira, 12 de novembro de 2012

FireFox Homepage won´t change


Home page won't set to my home page

 

change firefox homepage always revert to old page that was set:

You need to remove the file local-settings.js to stop using mozilla.cfg
local-settings.js..(Program files\Mozilla Firefox\defaults\pref) 
See:


all link: http://support.mozilla.org/en-US/questions/906803

 

segunda-feira, 23 de julho de 2012

LDAP OVER SSL for connecting ASA VPN USers TO Active Directory

Users connected through ASA 5510 VPN remote access configured with LDAP. 


When they connect to AD, user and password appear clear on the internal Sniffer.

Try to resolve this with:

1. Ldap over SSL configured on the ASA side

2. LDap over SSL in active directory:  


http://www.christowles.com/2010/11/enable-ldap-over-ssl-ldaps-on-windows.html






Test LDAP SSL: 


To confirm that LDAP over SSL is configured successfully

 Open the Ldp snap-in. 
To open Ldp, click Start. In Start Search, type ldp. Right-click the Ldp icon on the Start menu, and then click Run as administrator. 

If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes. 

Click the Ldp Connection menu, and then click Connect.
 In Server, type the host name of the server to which you want to connect. Ensure that Port is set to 636, the Connectionless check box is cleared, and the SSL check box is selected, and then click OK. 

If you receive a message that says “Cannot open connection,” LDAP-over-SSL binding is not configured properly.
 Click the Connection menu, click Bind, and then click OK. 

The command output should display the user name and domain name that you used for binding, if LDAP over SSL is configured properly.

quarta-feira, 11 de janeiro de 2012

GBIC SHOW SERIAL COMMAND ERS8600

ERS-8610:5# show sys pluggable-optical-modules info 1/15 detail




http://blog.michaelfmcnamara.com/2010/06/digital-diagnostic-monitoring-interface-on-ers-8600/

sexta-feira, 14 de outubro de 2011

Callpilot Manager Reset Password

Re: CALLPILOT Manager Password Reset

Start -> Programs -> CallPilot -> System Utilities -> Support Tools

Username :distributor(all lowercase)
Password : dst.CP4 (all case sensitive)

Start -> Programs -> CallPilot -> System Utilities -> Support Tools
select (9) Database Utilities
Select (3) Database API Utility

At the CI> prompt, type resetadminpwd and press

After reset you should login to manager with:

mailbox: 000000
pass: 124578

sexta-feira, 23 de setembro de 2011

Configuring Cisco ASA VPN with Active Directory Authentication

http://theitjanitor.com/configuring-cisco-asa-vp-with-active-directory-authentication/

I recently deployed a Cisco ASA 5510 as VPN solution. We were replacing an old SideWinder VPN. There were a few post out on the internet, but I didn’t...

http://www.blogger.com/img/blank.gif
http://www.blogger.com/img/blank.gifhttp://www.blogger.com/img/blank.gif
I recently deployed a Cisco ASA 5510 as VPN solution. We were replacing an old SideWinder VPN. There were a few post out on the internet, but I didn’t find a good step-by-step how to guide, so I figured I’d write one.

This tutorial assumes a few things:

You have a working VPN tunnel using local authentication – You can use the VPN Wizard to do this. I will user connection profile “Test.”
You have created a Active Directory Group – I will user VPN USERS in this example.
You have created a read-only Active Directory user – I will use vpn user in this example.
You have the DN’s for both the vpn user, and your base DN. You can use dsquery to obtain them – I will use the domain cisco.com in this example.

This configuration was performed on an ASA 5510 and and ASA 5505 version 8.2(2) with ASDM 6.25.
Adding the Active Directory server to the ASA

On ASDM navigate to Configuration –>Remote Access VPN –>AAA/Local Users –>AAA Server Groups
Under AAA Server Groups click add.
Under name, give it a name. Select LDAP for the protocol.
Select Reactivation mode Depletion.
Dead Time 10 Minutes.
Max Failed Attempts 3.
Click OK and then click apply.

Highlight the new server you just created, and click add under Servers in the Selected Group.
Select the interface in which the server sits behind, this would normally be the inside interface.
Server Type: Microsoft.
Base DN: DC=,DC= ie DC=cisco,DC=com, of course you would put your own domain instead of cisco.
Scope: All levels beneath the Base DN
Naming Attributes: sAMAccountName – be careful this is case sensitive.
Login:CN=vpn user,CN=Users,DC=CISCO,DC=COM – This is the user you created .
Login Password: Password for the user.
LDAP Attribute Map : None.
Leave the other LDAP Parameters blank and click OK and apply your configuration.



Adding the VPN Access Policy

Navigate to Configuration –> Remote Access VPN –> Network (Client) Access –> Dynamic Access Policies.
Select the DfltAccessPolicy and select edit.
Change the Action to Terminate, and click ok. This will deny any connection by default.
Click the Add button to create a new Access Policy.
Specify a description.
Under selection Criteria select User has ANY of the following Attributes, and click Add.
Under AAA Attribute Type select LDAP.
Attribute ID: memberOf, and click Get AD Groups
All your Active Directory groups should populate, select the VPN USERS Group, and click ok.

Under Action make sure continue is selected, and click ok and apply.

Navigate to Configuration –> Remote Access VPN –> IPsec Connection Profiles.
Either create a new profile or edit an existing profile.
Under Server Group, choose LDAP, this is the server we added earlier.



Click ok and apply your configuration.
At this point you should be able to VPN and Authenticate via Active Directory, provided you are a member of the VPN Users group.

segunda-feira, 19 de setembro de 2011

port Mirror Cisco Switch (SNIFFER)

via cli

monitor session 1 source interface Fa0/47
monitor session 1 destination interface Fa0/43

via cisco network assistant: