2016年7月25日 星期一

How to configure HTTP access to a router using local authentication

How to configure HTTP access to a router using local authentication



Resolution

This is a sample configuration of local authentication with Cisco IOS  Software Releases 11.3.3.T or later:
aaa new-model
!---Enable Authentication, Authorization and Accounting (AAA).
aaa authentication login default local
!---By default, use local authentication.
aaa authorization exec default local
username one privilege 15 password one
!--- User one is given privilege Level 15 (L15) and can execute all L15 commands.
username three password three
username four privilege 7 password four
!--- User four is given privilege Level 7 (L7) and can execute all commands for L7.
ip http server
!--- Enable HTTP connectivity to the router.
ip http authentication local
!---Specify local authentication for HTTP connections.
privilege exec L7 clear line
!---Change the clear line command to a privilege L7 command (so user four can execute it).
The users configured experience this behavior when they attempt to connect:
User one:
  • The user passes Web authorization if the URL is entered as http://#.#.#.#.
  • After the user Telnets to the router, the user can perform all commands after login authentication.
  • After login, the user is in enable mode (the show privilege command is L15).
  • If command authorization is added to the router, the user still succeeds in all commands.
User three:
  • User fails Web authorization for not having a privilege level.
  • If there is a Telnet to the router, the user can perform all commands after login authentication.
  • User is in non-enable mode after login (The show privilege command is Level 1 [L1]).
  • If command authorization is added to the router, the user still succeeds in all commands.
User four:
    • L1 commands plus the L7 clear line command appears.
    • After a Telnet to the router, the user can perform all commands after login authentication.
    • User is at privilege L7 after login (The show privilege command is L7).
    • If command authorization is added to the router, the user still succeeds in all commands.
    To address HTTP authentication problems, issue one of these commands:
    • debug aaa authentication: Displays information on AAA and TACACS+ authentication.
    • debug aaa authorization: Displays information on AAA and TACACS+ authorization.
    • debug radius: Displays detailed debugging information associated with RADIUS.
    • debug tacacs: Displays information associated with TACACS.
    • debug ip http authentication: Displays the authentication method the router attempted and authentication-specific status messages.

    Cisco IOS Software Version

    • 12.0
    • 12.1
    • 12.2
    • 12.3

    Autonomous: Configure A Cisco AP To Provide DHCP Services

    http://www.my80211.com/cisco-auton-cli-commands/2010/3/8/autonomous-configure-a-cisco-ap-to-provide-dhcp-services.html

    Autonomous: Configure A Cisco AP To Provide DHCP Services



    1. Lets start with the client exclusion. We will exclude the following ranges, so that the AP doesn't assign these specific addresses out: 
    192.168.1.1 - 192.168.1.10
    192.168.1.200 - 192.168.1.254 
    ap#config t
    ap(config)#ip dhcp excluded-address 192.168.1.1 192.168.1.10
    ap(config)#ip dhcp excluded-address 192.168.1.200 192.168.1.254

    2. Next, we will name the DHCP Scope (pool) and set the network:
    ap(config)#ip dhcp pool WIRELESS
    ap(dhcp-config)#network 192.168.1.0
    3. Next, we will set the LEASE time for the addresses (3 days,4 hours, 20 min) , setup the gateway and DNS:
    ap(dhcp-config)#lease 3 4 20
    ap(dhcp-config)#default-router 192.168.1.1
    ap(dhcp-config)#dns-server 192.168.1.250
    4. Next, we connect a wired laptop to the switch on the VLAN and see the results:
    (Note this will also hand out Wireless DHCP as well)
    Ethernet adapter Local Area Connection:
    Connection-specific DNS Suffix  . :
            Description . . . . . . . . . . . : Intel(R) 82567LM Gigabit Network Connection
            Physical Address. . . . . . . . . : 00-2A-A1-13-C2-33
            Dhcp Enabled. . . . . . . . . . . : Yes
            Autoconfiguration Enabled . : Yes
            IP Address. . . . . . . . . . . . . . : 192.168.1.11  <-- This is the first IP in our Scope
            Subnet Mask . . . . . . . . . . . : 255.255.255.0 <-- Our class C 
            Default Gateway . . . . . . . . . : 192.168.1.1   <-- This is the GW we set up
            DHCP Server . . . . . . . . . . . : 192.168.1.2      <-- This is the IP of our AP
            DNS Servers . . . . . . . . . . . : 192.168.1.250  <-- This is the DNS we set up 
            Lease Obtained. . . . . . . . . . : Saturday, March 06, 2010 5:48:12 PM <--- This is our lease time we set up
            Lease Expires . . . . . . . . . . : Tuesday, March 09, 2010 10:08:12 PM

    2016年7月12日 星期二

    Use a TFTP Server to Backup and Restore a Configuration cisco

    CE_2#copy running-config tftp:
    Address or name of remote host []? 64.104.207.171
    Destination filename [ce_2-confg]? backup_cfg_for_my_router
    !!
    1030 bytes copied in 2.489 secs (395 bytes/sec)
    CE_2#

    Windows 7: Internet Explorer Zoom - Enable or Disable

    Through the Local Group Policy Editor
    1. Open the all usersspecific users or groups, or all users except administrators Local Group Policy Editor for how you want this policy applied.
    2. In the left pane, click/tap on to expand User ConfigurationAdministrative TemplatesWindows Components, andInternet Explorer. (see screenshot below)

    2016年7月1日 星期五

    Disable password complexity rule in Active Directory Windows 2008

    http://serverfault.com/questions/19611/disable-password-complexity-rule-in-active-directory

    Open Group Policy Management Console (Start / Run / GPMC.MSC), open the Domain, and right-click and Edit the "Default Domain Policy". Then dig into the "Computer Configuration", "Windows Settings", "Security Settings", "Account Policies", and modify the password complexity requirements setting.

    2016年6月30日 星期四

    enable Network Discovery in the Network and Sharing Center windows 2008

    You cannot turn on Network Discovery in Network and Sharing Center in Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012

    Symptoms
    Assume that you try to turn on Network Discovery on a computer that is running Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012. To do this, you change the Advanced sharing settings in Network and Sharing Center. However, the changes are not saved. Therefore, you cannot turn on Network Discovery, and you experience the following issues: 
    • You cannot browse or find any network share.
    • You cannot view shared folders on a local network.
    Cause
    This issue occurs for one of the following reasons:
    • The dependency services for Network Discovery are not running.  
    • The Windows firewall or other firewalls do not allow Network Discovery.  
    Resolution
    To resolve the issue, follow these steps:
    1. Make sure that the following dependency services are started:
      • DNS Client
      • Function Discovery Resource Publication
      • SSDP Discovery
      • UPnP Device Host
    2. Configure the Windows firewall to allow Network Discovery. To do this, follow these steps:
      1. Open Control Panel, click System and Security, and then click Windows Firewall.
      2. In the left pane, click Allow an app or feature through Windows Firewall if you are running Windows Server 2012. Or, click Allow a program or feature through Windows Firewall if you are running Windows Server 2008 or Windows Server 2008 R2.
      3. Click Change settings. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
      4. Select Network discovery, and then click OK.
    3. Configure other firewalls in the network to allow Network Discovery.
    4. Turn on Network Discovery in Network and Sharing Center.