Sophos Enterprise Console

Guía rápida de inicio:

http://www.sophos.com/es-es/medialibrary/PDFs/documentation/sec_52_qsgeng.pdf

Guía de migración de servidor:

http://www.sophos.com/es-es/medialibrary/PDFs/documentation/sec_51_mgeng.pdf

OSPF Easy by David Davis

Review the basics

OSPF is an internal routing protocol. (While primarily used inside a single company, it can span multiple sites.) Based on RFC 2328, it's an open standard. Because of this, OSPF is available on Microsoft's Windows Server 2003 OS,Linux, and many other network devices—unlike Cisco's EIGRP routing protocol. Like other dynamic routing protocols, OSPF enables routers to disclose their available routes to other routers.

OSPF is a link-state routing protocol that runs Dijkstra's algorithm to calculate the shortest path to other networks. Taking the bandwidth of the network links into account, it uses cost as its metric. OSPF works by developing adjacencies with its neighbors, periodically sending hello packets to neighbors, flooding changes to neighbors when a link's status changes, and sending "paranoia updates" to neighbors of all recent link state changes every 30 minutes.

While OSPF is an excellent routing protocol for networks of all sizes, one of its weaknesses is that it can be quite complex to configure. On the other hand, it offers more features than simpler protocols such as RIP.

Here are some of OSPF's strengths:

• It converges quickly, compared to a distance-vector protocol.
• Routing update packets are small, as it doesn't send the entire routing table.
• It's not prone to routing loops.
• It scales very well for large networks.
• It recognizes the bandwidth of a link and takes this into account in link selection.
• It supports variable-length subnet masks (VLSM) orClassless Inter-Domain Routing (CIDR).
• It supports a long list of optional features that many others don't.

Configure OSPF

Some may find OSPF configuration intimidating, so let's look at how to make it easy. Let's start with a basic network: Our network example has two routers—one in San Diego (192.168.1.0 /24) and one in Dallas (192.168.2.0 /24). Between these two routers, there's a point-to-point T1 circuit with IP network address 1.1.1.0/30. The San Diego router's WAN interface is 1.1.1.1, and the Dallas router's WAN interface is 1.1.1.2.

We'll begin by configuring the router in San Diego. The first step to configuring OSPF is to use the router ospfcommand when in Global Configuration Mode. Here's an example:

Router(config)# router ospf {process number}
Router(config-router)#

While it doesn't matter which process number you use, I recommend keeping it the same on all OSPF routers on your network. I usually use 100 to keep everything simple. However, if you use different process numbers, OSPF will still work and exchange all routes—unlike EIGRP.

After entering OSPF Configuration Mode, the most common next step is to specify which networks OSPF will advertise, which you can do using the network command. Here's an example:

Router(config-router)# network 192.168.1.0 0.0.0.255 area 0
Router(config-router)# network 1.1.1.0 0.0.0.3 area 0

The first parameter is the network ID, and the second parameter is the inverse mask. The inverse mask—or wildcard mask—is the inverse of the subnet mask. It tells OSPF what range of interfaces the IP addresses given will apply to. Therefore, you can have one network statement that covers multiple interfaces.

You also need to specify the area, which is how OSPF organizes networks. All traffic must flow through area 0. In a small network, it's logical to put all networks in area 0, as we did in the example.

After you've configured each side of the network, the routers will exchange routes and form adjacencies. You should see a statement in the log file or console that looks something like the following:

*Mar  1 02:53:33.370: %OSPF-5-ADJCHG: Process 100, Nbr 1.1.1.1 
  on Ethernet0/0 from LOADING to FULL, Loading Done

To make sure you see these types of messages, use thelog-adjacency-changes command in your OSPF router configuration. This command causes OSPF to enter information into the router's log file whenever it loses or regains connectivity with its neighbors. Here's an example:

Router(config-router)# log-adjacency-changes

Check the status of OSPF

After you've configured OSPF, you need to know how to check its status. Here are some common OSPF commands, along with links to their Cisco documentation and sample output from our example:

• show ip ospf— Listing A displays the output.
• show ip ospf neighbor— Listing B displays the output.
• show ip ospf interface— Listing C displays the output.
• show ip route ospf— Listing D displays the output.

Configurar router Comtrend VG8050 en modo BRIDGE

configuración correcta para internet es PPPoE, 

La única manera de conectarlo sería configurar el Comtrend VG8050 con la VLAN de internet en modo bridge y conectarle el router no telefonica configurado con el PPPoE.

Sólo podrás poner la VLAN de internet en bridge si no dispones del servicio Movistar TV ya que si lo haces y tienes Movistar TV, no podrás verla.

Lo pirmero que has de hacer es sacar el router de Movistar de la gestión del portal alejandra, para ello has de entrar en el portal alejandra: Acceso portal alejandra (http://www.movistar.es/particulares/internet/movistar-adsl/ya-tengo-adsl/servicios/ficha/configuracion-routers-portal-alejandra)y cuando ya estés en la información de tu router, has de buscar la pestaña de cambiarle la contraseña, pon una contraseña que te sea fácil de recordar y aplica los cambios.

Una vez que ya tenemos el router fuera de gestión:

Estos datos son para los menús del router Comtrend 5813 así que puede que algún nombre del menú del Comtrend VG8050 varíe. Si tienes dudas sobre los menús del router, aquí tienes el manual: User Manual Comtrend VG8050(http://www.movistar.es/rpmm/estaticos/residencial/fijo/banda-ancha-adsl/manuales/router-inalambrico-movistar-futura-ftth/Manual-usuario-fabricante-Router-Fibra-Optica-Comtrend-VG-8050.pdf)

Abrimos el navegador y ponemos la IP del router, (de fábrica es 192.168.1.1  (router en modo local)

Nos pide usuario y password  (usuario: 1234 password el que acabas de poner en el portal )

Accedemos a la pantalla inicial del configurador WEB.

Seleccionamos Advanced Setup -> WAN Service del menú de la izquierda.

Marcamos la casilla de la derecha correspondiente a la Interfaz PPPoE y pulsamos el botón Remove para borrarla.

Ahora pulsamos el botón Add para crear una nueva interfaz WAN

En la siguiente pantalla dejamos el valor por defecto (eth0/ETHWAN) y pulsamos el botón Next

Marcamos la opción Brindging,  en la casilla Enter 802.1P Priority [0-7] escribimos 1 y en la casilla Enter 802.1Q VLAN ID [0-4095]escribimos 6, después pulsamos el botón Next

Vemos el resumen de la configuración, para aplicar los cambios pulsamos el botón Apply/Save

Aparece una nueva línea en la lista con la interfaz Wan que acabamos de crear.

El dispositivo que conectemos a la Lan del router (el nuevo router) debe de tener abilitado el Cliente PPPoE para iniciar sesión de navegación.

Los datos para el cliente PPPoE:

usuario: adslppp@telefonicanetpa

pass : adslppp

Implantación nuevo Servidor

https://drive.google.com/file/d/0B7XR1Ppl2sAESkREbGktU2VrZEE/edit?usp=sharing
https://drive.google.com/file/d/0B7XR1Ppl2sAEZnp0dUxlbVFRNzg/edit?usp=sharing

Cómo quitar datos en Active Directory después de una degradación sin éxito de un controlador de dominio

Cómo quitar datos en Active Directory después de una degradación sin éxito
de un controlador de dominio

https://drive.google.com/file/d/0B7XR1Ppl2sAESkREbGktU2VrZEE/edit?usp=sharing

Cambios por comandshell

Cambio de IP estatica a dinamica(DHCP)  en XP
netsh interface ip set address "Conexión de área local" dhcp

Desinstalar ISA 2004 desde un Server 2003

Desinstalar ISA 2004 desde un Server 2003


http://msmvps.com/blogs/kwsupport/archive/2008/09/07/uninstalling-isa-2004.aspx