I partially answered my own question. Yes for option one but I am using identical servers. What if the servers were not identical? Should the VM work when moved?
Anyway, if it helps anyone, here is what I did to move a Win2000 VM from a kvm-based Ubuntu 9.04-server amd64 to a server running proxmox 1.4 beta2. My transfer medium was an external usb drive formatted using ext3.
#Backup On Prod Server
# Plug in usb drive and locate drive. You might want to use fdisk to help. In fdisk type 'p' to list partitions. 'm' for help.
fdisk /dev/sdb
# mount drive if not mounted
mkdir /mnt/drive2
sudo mount /dev/sdb1 /mnt/drive2
# Find LVM file to copy
sudo lvdisplay
sudo dd if=/dev/vmgroup/vm52 of=/mnt/drive2/vm_2000.dd
ls -lh /mnt/drive2/
sudo umount /mnt/drive2
#Migrate to New Server
# Plug in usb drive and locate drive. See directions above
mkdir /mnt/drive2
sudo mount /dev/sdb1 /mnt/drive2
ls -lh /mnt/drive2/
# Locate desired VM to replace and rename. They are in the images folder.
ls -hl /var/lib/vz/images/103
mv /var/lib/vz/images/103/*.raw /var/lib/vz/images/103/vm-103-disk-1.raw.back
# Copy the external usb file to the proxmox lvm
dd if=/mnt/drive2/vm_2000.dd of=/var/lib/vz/images/103/vm-103-disk-1.raw
# Clean-up
rm /var/lib/vz/images/103/vm-103-disk-1.raw.back
# Unmount
sudo umount /mnt/drive2
Enjoy!
Oslo
sábado, 19 de octubre de 2013
lunes, 12 de agosto de 2013
zimbra How to renew certificate after 365 days
Error you get ...
Unable to determine enabled services from ldap.
Enabled services read from cache. Service list may be inaccurate.
Starting logger...Failed.
Starting logswatch...ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.net.ssl.SSLHandshakeException sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed)
zimbra logger service is not enabled! failed.
'''Solution is:'''
as su - zimbra
zmcontrol stop
as root
cd /opt/zimbra/bin
./zmcertmgr createcrt -new -days 365
./zmcertmgr deploycrt self
./zmcertmgr viewdeployedcrt
cd /opt/zimbra/libexec
./zmfixperms
Unable to determine enabled services from ldap.
Enabled services read from cache. Service list may be inaccurate.
Starting logger...Failed.
Starting logswatch...ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.net.ssl.SSLHandshakeException sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed)
zimbra logger service is not enabled! failed.
'''Solution is:'''
as su - zimbra
zmcontrol stop
as root
cd /opt/zimbra/bin
./zmcertmgr createcrt -new -days 365
./zmcertmgr deploycrt self
./zmcertmgr viewdeployedcrt
cd /opt/zimbra/libexec
./zmfixperms
sábado, 20 de julio de 2013
RALINK 5360 ..how to install dwa 525 with chipset ralink 5360 on ubuntu 10.04
Re: RALINK 5360 ..how to install dwa 525 with chipset ralink 5360 on ubuntu 10.04..
I love a challenge and so will you, I hope. This is a relatively new device and we are going to have to experiment a bit. Please download RT539x PCIe here: http://www.ralinktech.com/en/04_supp...ort.php?sn=501
Download it to your desktop. Right-click it and select 'extract here.' It is handily a bz2.bz2 file, so you may have to 'extract here' a couple of times. Good work, Ralink! Now open a terminal and, with an internet connection, do:Open the folder you extracted and drill down to os/linux/config.mk and with a text editor change:Code:sudo apt-get install linux-headers-generic build-essentialProofread, save and close the text editor. Now open the file os/linux/pci_main_dev.c with a text editor. Make the addition I've highlighted here:Code:HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y
Everything before and after is unchanged. Spacing, punctuation, brackets, etc. are crucial. Proofread carefully twice before you save and close the text editor. Now back to the terminal:Code:#ifdef RT5390 {PCI_DEVICE(NIC_PCI_VENDOR_ID, NIC5390_PCIe_DEVICE_ID)}, {PCI_DEVICE(NIC_PCI_VENDOR_ID, NIC539F_PCIe_DEVICE_ID)}, {PCI_DEVICE(NIC_PCI_VENDOR_ID, NIC5392_PCIe_DEVICE_ID)}, {PCI_DEVICE(NIC_PCI_VENDOR_ID, NIC5362_PCI_DEVICE_ID)}, {PCI_DEVICE(NIC_PCI_VENDOR_ID, NIC5360_PCI_DEVICE_ID)}, #endif /* RT5390 */
Press Tab and the rest will fill in automagically. Press Enter.Code:cd Desktop/2011Your wireless should now be working.Code:sudo su make make install modprobe rt5390sta echo rt5390sta >> /etc/modules exit
jueves, 11 de julio de 2013
sábado, 29 de junio de 2013
instalar xubuntu+postgresql+pgadmin
wget -O -- http://apt.postgresql.org/pub/repos/apt/ACCC4CF8.asc > ok.key
sudo apt-key add ok.key
http://www.ubuntugeek.com/how-to-install-postgresql-9-2-on-ubuntu-13-04-server.html
recovery postgres password http://www.netstorming.com.ar/2009/10/15/resetear-password-de-root-en-postgresql/
Installing PostgreSQL 9.1 on Ubuntu 10.04
27 Replies
PostgreSQL 9.0 final was released on 2010/09/20 which I’ve been waiting for to begin playing with it and evaluating it. The mainline Ubuntu Lucid apt repositories only have 8.4. According to the package maintainer, Martin Pitt, the postgresql-9.0 package won’t be added until Ubuntu Natty. Thankfully, he setup a backports repo for Ubuntu that we can pull from.
This is a very quick and painless process. If you have not done so already, make your life easier by installing python-software-properties:
sudo apt-get install python-software-properties
Next up is adding the backports repo and updating apt:
sudo add-apt-repository ppa:pitti/postgresql
sudo apt-get update
UPDATE: In the comments, Jason Froebe points out that if you already have an earlier version of PostgreSQL installed, you can just upgrade it:
sudo apt-get upgrade
Finally install postgresql-9.1:
The libpq-dev package is for compiling wrappers/clients against libpq.
sudo apt-get install postgresql-9.1 libpq-dev
The libpq-dev package is for compiling wrappers/clients against libpq.
There you’re done!
jueves, 27 de junio de 2013
web shell
https://code.google.com/p/shellinabox/
Basic HTTPS Shell In A Box
First we download and install Shell In A Box. You can download .deb file for your operating systems architecture here by visition Shell In A Box official page here.
Next thing is to install Shell In A Box:
sudo dpkg -i shellinabox*.deb |
Now we need to add a few options to Shell In A Box .conf file:
sudo gedit /etc/default/shellinabox |
You need to replace line:
SHELLINABOX_ARGS="--no-beep" |
with line:
SHELLINABOX_ARGS="--no-beep --disable-ssl" |
martes, 14 de mayo de 2013
How to configure BonitaSoft engine with Tomcat and Mysql database
To do configuration we need to have following software install.
1)Download the Apache tomcat from the bonitasoft site and unzip it.http://www.bonitasoft.com/products/BPM_downloads (In "Bundle" tab you can find "Tomcat" with download link)
2)Download and install the Mysql database. You can download mysql community edition fromhttp://dev.mysql.com/downloads/mysql/
3) you should have JDK ( JDK- 1.6 and JDK -1.7) on your machine. If you don’t have one you can download and install it from - http://www.oracle.com/technetwork/java/javase/downloads/index.html
4)Download the Bonita Soft from the bonitasoft site and unzip it.http://www.bonitasoft.com/products/BPM_downloads (In "Bonita Open Solution" tab you can find "Bonita soft" with download link)
1)Download the Apache tomcat from the bonitasoft site and unzip it.http://www.bonitasoft.com/products/BPM_downloads (In "Bundle" tab you can find "Tomcat" with download link)
2)Download and install the Mysql database. You can download mysql community edition fromhttp://dev.mysql.com/downloads/mysql/
3) you should have JDK ( JDK- 1.6 and JDK -1.7) on your machine. If you don’t have one you can download and install it from - http://www.oracle.com/technetwork/java/javase/downloads/index.html
4)Download the Bonita Soft from the bonitasoft site and unzip it.http://www.bonitasoft.com/products/BPM_downloads (In "Bonita Open Solution" tab you can find "Bonita soft" with download link)
Following are step to install bonita soft
Step 1. Create two databases named bonita_history and bonita_journal.
Commands:
Create database bonita_history;
Create database bonita_journal;
Step 1. Create two databases named bonita_history and bonita_journal.
Commands:
Create database bonita_history;
Create database bonita_journal;
Step 2. Create user “bonita” with password as “bpm” and grant all permissions for above created two databases.
Commands:
CREATE USER 'bonita'@'localhost' IDENTIFIED BY 'bpm';
GRANT ALL ON bonita_history.* TO 'bonita'@'localhost';
GRANT ALL ON bonita_journal.* TO 'bonita'@'localhost';
Commands:
CREATE USER 'bonita'@'localhost' IDENTIFIED BY 'bpm';
GRANT ALL ON bonita_history.* TO 'bonita'@'localhost';
GRANT ALL ON bonita_journal.* TO 'bonita'@'localhost';
Step3. Essentially the downloaded Apache tomcat with BOS configuration uses H2 database and it internally uses hibernate framework for database interaction, and these two file store the database properties required by the BOS . So, we need to modify these two files.
Modify BOS configuration files names bonita-journal.properties and bonita-history.properties, as mentioned below:
(Note:Tthese two files are located at –“ BOS-5.9.1-Tomcat-6.0.35\bonita\server\default\conf”)
Comment the “hibernate.dialect” of H2 database. (Note: To comment out in properties file we use “#”)
Comment “bonita.hibernate.interceptor” attribute as well.
Un comment “hibernate.dialect” and “bonita.hibernate.interceptor” from “Examples- MYSQL” , make sure that the values of these 2 attributes are “org.hibernate.dialect.MySQL5InnoDBDialect” and “org.ow2.bonita.env.interceptor.MySQLDescNullFirstInterceptor” respectively for Mysql database.
Also we need to configure the hibernate properties in context.xml file which is located at “BOS-5.9.1-Tomcat-6.0.35\conf”, the properties which needs to be configured is as shown below (This needs to be done twice for both databases under name – “bonita/default/journal” and “bonita/default/history”) :
Comment the “hibernate.dialect” of H2 database. (Note: To comment out in properties file we use “#”)
Comment “bonita.hibernate.interceptor” attribute as well.
Un comment “hibernate.dialect” and “bonita.hibernate.interceptor” from “Examples- MYSQL” , make sure that the values of these 2 attributes are “org.hibernate.dialect.MySQL5InnoDBDialect” and “org.ow2.bonita.env.interceptor.MySQLDescNullFirstInterceptor” respectively for Mysql database.
Also we need to configure the hibernate properties in context.xml file which is located at “BOS-5.9.1-Tomcat-6.0.35\conf”, the properties which needs to be configured is as shown below (This needs to be done twice for both databases under name – “bonita/default/journal” and “bonita/default/history”) :
type="javax.sql.DataSource"
maxActive="100"
minIdle="10"
maxWait="10000"
initialSize="1"
maxPoolSize="15"
minPoolSize="3"
maxConnectionAge="0"
maxIdleTime="1800"
maxIdleTimeExcessConnections="120"
idleConnectionTestPeriod="30"
acquireIncrement="3"
testConnectionOnCheckout="true"
removeAbandoned="true"
logAbandoned="true"
username="root"
password="root"
driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost:3306/bonita_journal?dontTrackOpenResources=true"/>
url="jdbc:mysql://localhost:3306/bonita_journal?dontTrackOpenResources=true"/>
type="javax.sql.DataSource"
maxActive="100"
minIdle="10"
maxWait="10000"
initialSize="1"
maxPoolSize="15"
minPoolSize="3"
maxConnectionAge="0"
maxIdleTime="1800"
maxIdleTimeExcessConnections="120"
idleConnectionTestPeriod="30"
acquireIncrement="3"
testConnectionOnCheckout="true"
removeAbandoned="true"
logAbandoned="true"
username="root"
password="root"
driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost:3306/bonita_history?dontTrackOpenResources=true"/>
Step5:Once the above configuration is done, add mysql-jdbc diver (http://dev.mysql.com/downloads/connector/j/ ) into “BOS-5.9.1-Tomcat-6.0.35\lib\bonita” location and remove h2-1.2.139.jar from this location as it is no more required.
step6: Start the tomcat server by navigating to “BOS-5.9.1-Tomcat-6.0.35\bin” location and running command startup.bat from the windows command prompt.
Step7:Once the tomcat server starts hit this url http://localhost:8080/bonita/ , use default credentials user – “admin” and password- “bpm” to login. If you are able to login with no errors then the configuration is fine.(if not login clear browser cache)
Step8:Bonita creates almost 69 tables into the above 2 created database, to verify execute command “select * from bonita_journal;” from the mysql client.
step9:After the first run you need to comment “hibernate.hbm2ddl.auto” property from bonita-journal.properties and bonita-history.properties files as it is needed to create the table only at first run.
Note:If you have created process in bonita soft studio after that export that process from bonita soft studio and
go in http://localhost:8080/bonita/ in that left side "Administration " link where processes link there to install new process in that
go in http://localhost:8080/bonita/ in that left side "Administration " link where processes link there to install new process in that
jueves, 28 de marzo de 2013
Instant Messaging Services with Openfire on Ubuntu 12.04 LTS (Precise Pangolin)
Openfire is an open source real-time collaboration (instant messaging) server, built on the XMPP protocol and available for multiple platforms. This guide will help you get started with Openfire on your Ubuntu 12.04 LTS (Precise Pangolin) Linux VPS.
If you haven't done so already, please follow the steps outlined in our getting started guide before following these instructions, and make sure your system is fully updated. Initial configuration steps will be performed through the terminal; please make sure you're logged into your Linode as root via SSH.
Contents
Prerequisites
Before installing Openfire, make sure your system is up to date. Enter the following commands, one by one, and install any available updates:
sudo apt-get update sudo apt-get upgrade
Openfire requires a Java runtime engine (JRE). This tutorial uses the OpenJDK provided by the Ubuntu repository. Please note that although alternate Java runtime engines are available, Openfire may not work with them. Enter the following command to install the OpenJDK:
sudo apt-get install openjdk-7-jre
OpenJDK will be installed, along with a series of dependencies it requires.
Adjusting Firewall Settings
If you employ a firewall to specify what ports can be accessed on your VPS, verify that you have the following ports open:
- 3478 - STUN Service (NAT connectivity)
- 3479 - STUN Service (NAT connectivity)
- 5222 - Client to Server (standard and encrypted)
- 5223 - Client to Server (legacy SSL support)
- 5229 - Flash Cross Domain (Flash client support)
- 7070 - HTTP Binding (unsecured HTTP connecitons)
- 7443 - HTTP Binding (secured HTTP connections)
- 7777 - File Transfer Proxy (XMPP file transfers)
- 9090 - Admin Console (unsecured)
- 9091 - Admin Console (secured)
Additional ports may need to be opened later to support more advanced XMPP services, but these are the ports that Openfire will use by default.
Installing Openfire
Installing Openfire is relatively easy and can be completed in just a couple of steps. Here's how to install Openfire:
- Visit the download page for the Openfire RTC server and click the link for the .tar.gz file. You will be taken to another page, which will start the download to your workstation. You may cancel this download, as a manual download link will be presented that you may copy to your clipboard and paste in to the wget command in the next step.
- Use wget on your Linode to retrieve the package (substitute the link for the current version in the command below).
wget http://www.igniterealtime.org/downloadServlet?filename=openfire/openfire_3_7_1.tar.gz
- Change the name of the download by entering the following command:
mv downloadServlet\?filename\=openfire%2Fopenfire_3_7_1.tar.gz openfire_3_7_1.tar.gz
- Untar the software by entering the following command:
tar -xvzf openfire_3_7_1.tar.gz
- Move the openfire folder to /opt by entering the following command:
mv openfire /opt/
- Edit the configuration file /opt/openfire/conf/openfire.xml, inserting your Linode's public IP address in the <interface> section, and removing the "<!---->" comment markers that surround the <network> section. While not required, this action is helpful if your Linode has multiple IP addresses, and you wish to limit access to a single address.File excerpt:/opt/openfire/conf/openfire.xml
<interface>12.34.56.78</interface>
- Add a symbolic link for the daemon script to /etc/init.d so that you can start the daemon with a call to service:
ln -s /opt/openfire/bin/openfire /etc/init.d/
- Start Openfire with the following command:
service openfire start
This completes the initial installation steps for Openfire. Next, we'll continue with configuration through a web browser.
Configuring Openfire
Configuring Openfire is relatively easy and can be completed in just a couple of steps. Here's how to configure Openfire:
- Direct your browser to your Linode's IP address or FQDN (fully qualified domain name, if an entry in DNS points to your Linode's IP) on port 9090. As an example, if your Linode's IP address were 12.34.56.78, you would visit http://12.34.56.78:9090 in your web browser. The webpage shown below appears:
- Configure your domain and ports for administration. Use the fully qualified domain name you have assigned to your Linode in DNS. For more infomation: configuring DNS with the Linode Manager).
- You may choose to use Openfire's internal database for account management, or you may connect to an external database. Most users will want to choose the built-in option.
- User profiles may be stored in the server database, or they may be pulled from LDAP or Clearspace. Most users will want to choose the default option.
- Enter the email address of the default administrative user and select a strong password.
- After the initial web-based configuration is complete, restart the Openfire server before attempting to log in with the default "admin" user account. Enter the following commands, one by one:
service openfire stop service openfire start
If you're experiencing difficulty using the credentials you just created to log in, please use "admin/admin" as the username/password. You'll need to update your credentials immediately afterward for security purposes. Congratulations! You've successfully installed the Openfire RTC server on Ubuntu 12.04 LTS.
More Information
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
miércoles, 27 de marzo de 2013
Install alfresco 4.0 on ubuntu 11.04 using command line
Requirement software for Alfresco
- Java JDK 6 jdk
- OpenOffice
- ImageMagick
- Flash Player
- SWF tools
- TinyMCE language packs
- Alfresco Module Package
- Firefox extension
Install JDK 6
You may need to setup the jdk packages for ubuntu in the official repository.
Setup the jdk repository
root@htvlc:~#add-apt-repository ppa:ferramroberto/java root@htvlc:~#apt-get update
Install jdk
root@htvlc:~#apt-get install sun-java6-jdk
Install OpenOffice
root@htvlc:~#apt-get install openoffice.org
Install ImageMagick
root@htvlc:~#apt-get install imagemagick
Install Flash Player
- first remove all the old flash plugin
- secondly install the new flash plugin
root@htvlc:~#apt-get remove flashplugin-* --purge root@htvlc:~#apt-get install flashplugin-nonfree
Install SWF Tools
Before you install the swf tool, make sure the linux compilers and other depend packages are installed.
Install dependent packages
root@htvlc:~#apt-get install gsfonts libart-2.0-2 libc6 libfreetype6 libgcc1 libgif4 libjpeg62 libstdc++6 libt1-5 zlib1g gs-common
Install swf tools and setup repository
/etc/apt/sources.list
Add the following in the /etc/apt/sources.list
deb http://ubuntu.mirror.cambrium.nl/ubuntu/ hardy main universe
update the repository
root@htvlc:~#apt-get update
Install swf tools
root@htvlc:/home/sophal# apt-get install swftools
Install TinyMCE language packs
root@htvlc:/home/sophal# apt-get install tinymce
Download Lastest Alfresco
The current version of alfresco that I used to install is Alfresco v4. You may have a newer version. Or you visit the alfresco website athttp://www.alfresco.com/try/ Download to download the alfresco.
Install Alfresco
root@htvlc:/home/sophal# ./alfresco-community-4.0.c-installer-linux-x64.bin Language Selection Please select the installation language [1] English - English [2] French - Français [3] Spanish - Español [4] Italian - Italiano [5] German - Deutsch [6] Japanese - 日本語 [7] Dutch - Nederlands Please choose an option [1] : 1 ---------------------------------------------------------------------------- Welcome to the Alfresco Community Setup Wizard. ---------------------------------------------------------------------------- Installation Type [1] Easy - Installs servers with the default configuration [2] Advanced - Configures server ports and service properties.: Also choose optional components to install. Please choose an option [1] :
miércoles, 20 de marzo de 2013
Encender / Apagar remotamente un PC (Shutdown / Wake On Lan)
Shutdown / Wake On Lan
¿Sabías que es posible encender / apagar un PC de manera remota? Efectivamente, esto es posible y es muy sencillo.
Probado con Windows XP profesional
Shutdown
Requisitos
Es necesario que estés en la misma red de área local (LAN) que el PC objetivo, es decir el que deseas apagar de manera remota. Además debes saber el nombre de usuario y la contraseña de una sesión del PC objetivo.Puerto 445
Lo primero que debes hacer es comprobar que el puerto TCP 445 esté abierto en el cortafuegos de Windows del PC objetivo.Para ello, haz lo siguiente:
- Dirígete a Inicio > Panel de control: Centro de seguridad
- Haz clic en Cortafuegos de Windows luego dirígete a la pestaña Excepciones
- Normalmente aparece una línea "Compartir archivos e impresoras", marca la casilla y haz clic en "Aceptar"
- Si no te aparece la línea "Compartir archivos e impresoras", haz clic en "Agregar un puerto..." y selecciona el puerto 445 TCP
- Luego dirígete a Inicio > Panel de control: Sistema en la pestaña "Uso de manera remota". Marca la casilla "Autorizar a los usuarios a conectarse de manera remota a este PC"
Comando
net use
Para obtener los privilegios necesarios para poder ejecutar un comando shutdown en el PC objetivo, debes ejecutar el comando net use. Es necesario obtener la dirección de la máquina objetivo, lo necesitaremos para ejecutar el comando. Para ello:- Dirígete a Inicio > Ejecutar (o presiona las teclas Windows + R)
- Escribe cmd luego haz clic en Aceptar
- Aparece una ventana DOS, escribe: net use \\ip_máquina_objetivo
- Ingresa el nombre de usuario de una sesión de la maquina objetivo. Luego la contraseña
- Aparecerá un mensaje indicando que el comando se ha terminado correctamente
shutdown
Ahora podemos pasar al comando en sí mismo.El comando es de este tipo: shutdown -s -f -t 30 - m \\192.168.3.4
- -s: Apaga el PC
- -f: Fuerza el cierre de las aplicaciones que se están ejecutando
- -t xx: Define una cuenta en segundos
- -m \\xxx.xxx.xxx.xxx: Precisa la dirección IP de la maquina objetivo.
Interfaz gráfica disponible ejecutando: shutdown -i
- Para obtener ayuda sobre este comando, ejecuta shutdown /?
Además existen muchos programas que realizan lo mismo.
Si todo se llevo a cabo correctamente, el PC objetivo recibirá un mensaje indicando el cierre del sistema.
WakeOnLan
- El Wake On Lan como su nombre lo indica, consisten en encender un ordenador de manera remota a través de la red, enviando un Magic Packet a la tarjeta de red del ordenador objetivo.
- Importante: no todas las tarjetas de red ni las BIOS son compatibles con la recepción de los Magic Packet.
Requisitos
Para realizar esta operación es necesario que el PC de origen se encuentre en la misma red de area local (LAN) que el ordenador objetivo (el que quieres encender de manera remota)También es necesario conocer la dirección física (MAC) y la dirección IP del ordenador objetivo.
MAC & IP
Lo primero que debes hacer es conseguir la dirección IP y la dirección MAC del ordenador objetivo:- Dirígete a Inicio > Ejecutar o presiona simultáneamente la tecla de Windows + R
- Escribe cmd y haz clic en Aceptar
- En la ventana DOS que aparece, escribe ipconfig/all
- Toma nota de la dirección física (MAC) y la dirección IP
Tarjeta de red
Para ver si tu tarjeta de red es compatible, sigue estos pasos:- Haz clic derecho sobre Equipo y selecciona Administrar
- Entra a Administrador de dispositivos > Adaptadores de red
- Haz clic derecho sobre tu tarjeta de red y selecciona "Propiedades"
- Una vez en Propiedades, debes buscar las palabras "Magic Packet", "Wake On Magic Packet", "Wake On Lan". Comprueba que todas las opciones estén activadas.
- Si no encuentras estas opciones, quizás necesites actualizar tu tarjeta de red. Dirígete a la página del fabricante de la tarjeta.
- Reinicia el ordenador objetivo.
BIOS
Para ver si tu BIOS es compatible, haz lo siguiente:
- Reinicia el PC y entra a la BIOS presionando la tecla necesaria según la BIOS (ESC, F2, F5, F12, DEL)
- Una vez en la BIOS, entra a las opciones de alimentación (POWER) y activa la opción Wake-on-Lan, o similar.
Cortafuegos
Abre el puerto 8900 del mismo modo que el puerto 445.WOL
- Lo primero que debes hacer es descargar en el PC de origen, un pequeño programa Wake-on-Lan (WOL) de aquí
- Esta es su interfaz:
- Rellena los campos con la información obtenida más arriba
- Mac Adress: dirección MAC (de la máquina objetivo)
- Internet Adress: dirección IP local (de la máquina objetivo)
- Subnet Mask: 255.255.255.255
- Send Options: Local Subnet
- Remote Port Number: 8900
- Haz clic en el botón Wake Me Up
Una vez recibido el paquete, el PC objetivo debería encenderse.
Desde Internet
En teoría, es posible encender el PC desde Internet, tan solo hay que configurar el router para redirigir un paquete UDP de un puerto especifico a todos los PCs de la red. En la práctica, solo es posible en algunos routers. Si envías el magic packet a tu dirección IP publica y al puerto correcto mediante el programa mencionado más arriba, tu PC se encenderá. Una sola configuración del router servirá para todos los PCs, pero cada PC será encendido independientemente de los otros, gracias a su magic packet personalizado.Por teléfono
Si deseas encender tu PC sin que te encuentres en casa, necesitarás un modem RTC externo sobre puerto serie RS-232 (un poco antiguo). Conecta el modem a tu PC, y activa la opción de tu BIOS "wake on modem ring" . De este modo, cuando el modem esté encendido, si tu teléfono suena, tu PC se encenderá...Este modem se conecta muy bien en la línea telefónica IP del router, tu teléfono deberá ser conectado en paralelo al modem.El inconveniente es que tu PC se encenderá (si el modem está encendido) a cada llamada telefónica...Personalmente yo ejecuto el comando siguiente en "Inicio > Ejecutar":
shutdown -s -t 300 que apaga el PC al cabo de 5 minutos. Un acceso directo del comando shutdown -aen el escritorio permite anular el apagado cuando estás delante del PC. El comando de anulación puede ser lanzado de manera remota mediante VNC, un script PHP (exec), o cualquier otro método de ejecución de código de manera remota.
Suscribirse a:
Entradas (Atom)