Authentication Method: choose "LDAP Authentication"
Guest User: "No User" (if not allow)
User Template: "guest" (my choice)
Server: "xxx.xxx.xxx.xxx" (input your ad server's ip here)
Port Standard: "389" (no change)
Port SSL: "636" (no change)
Protocol Version: "Version 3"
Encryption: "none"
Referrals: "Disabled"
Mode: "Specific Searching"
Distinguished Name (DN): "
Search Base: "dc=mydomain,dc=com"
Search Filter: "(&(objectclass=user)(objectcategory=user)(userPrincipalName=
Search Distingished Name (DN): "ldapuser@mydomain.com"
Search Password: "********" (password of your Search Distingished Name)
Autenticación de Cacti contra Windows 2003 AD
Como ejecutar firestarter al arrancar
Buscando por internet todo lo que encontraba se basaba en modificar el sudoers.
Pero existe otra forma. Ejecutar esto en un terminal
1.- gksudo gedit /etc/firestarter/firestarter.sh
2.- Localizar el parrafo (esta casi al principio):
if [ "$MASK" = "" -a "$1" != "stop" ]; then
echo "External network device $IF is not ready. Aborting.."
exit 2
fi
3.- modificarlo por (añadir los #):
#if [ "$MASK" = "" -a "$1" != "stop" ]; then
#echo "External network device $IF is not ready. Aborting.."
#exit 2
#fi
4.- Reiniciar
esta sacado de http://ubuntuforums.org/showthread.php?t=542756
Como ejecutar FlashFXP bajo Linux con Win
Despues de varios intentos (gftpd, etc..) he decidido montar FlashFXP sobre Wine. ninguno de los programas de FTP actuales para linux, que he encontrado, tiene la versatilidad de FlashFXP.
Si lo instalas con Wine, la mayoria de las versiones no funcionan incluyendo las últimas (wine 1.1.2 y FlashFXP 3.6).
En esta web hay un workaround. Una vez instalado, basta ejecutar lo siguiente en una consola:
wget http://kegel.com/wine/winetricks
sh winetricks cc580
De esta forma, podremos listar contenido y descargar. Ahora solo falta que pueda subir ficheros.
Con la versión 2.0 sin fichero de ayuda funciona!!
Configurar NFS Server en Windows
En castellano: http://bevirtual.blogspot.com/2007/04/nota-tcnica-usando-windows-server-como.html
Using Windows-based NFS in VI3
Jason Mattox from vizioncore has provided the following information for people looking to use some of the low-cost storage alternatives available in VI3. This particular setup uses a Windows machine and Windows Services for UNIX to create an NFS share that can be mounted to an ESX host for Virtual Machine, Template or ISO storage. I will follow this article up shortly with a free software iSCSI setup that runs extremely well for lab/test usage. The following URL also has a detailed description of NFS Authentication when using WSFU and was utilized to create this quick-start guide:http://www.microsoft.com/technet/interopmigration/unix/sfu/nfsauth.mspx
The main steps in this process are:
1. Installing Windows Services for UNIX (WSFU)
2. Copying the ESX Server password and group files to Windows
3. Configuring WSFU for accepting ESX Server connections
4. Sharing the Windows folder for NFS compatibility
5. Configuring the ESX Server to mount the Window NFS Share as Datastore.
1. Installing Windows Services for UNIX (WSFU)
Download windows services for UNIX at:
http://www.microsoft.com/windowsserversystem/sfu/downloads/default.mspx
Install WSFU on the desired machine
Add in the following options
NFS + Server for NFS
Authentication tools for NFS + user name mapping
After installation, open services control panel applet and change the service ‘User Name Mapping’ to startup automatically and then start the service
2. Copy the ESX Server password and group files to Windows
Use a program like WinSCP or similar process to copy the following files to your local system where WSFU is installed
You can get WinSCP from the fowling location.
http://winscp.net/eng/download.php#download2
Transfer the file /ect/password and the file /ect/group to C:\SFU or to the location where you installed WSFU
3. Configure WSFU to accepting ESX Server connections
Click Start, Programs, Windows Services for UNIX, Services for UNIX Administration
Go to user name mappings then configuration
Click password and group files
Then browse for the password and group files that you copied, from the browse dialog box for both the password and group fields
Click apply
Then go to maps
Click show maps
List windows users and list Unix users
Then select a local administrator user on the left that will be mapped to the root account and the root user on the right.
Then click apply (upper right)
My path is \\myserver.mydomain.int\NFS-VMFS01 for the windows share and NFS share on the windows host with WSU installed.
4. Sharing the Windows folder for NFS compatibility
Right click the local folder you wish to share via NFS
Share the folder by clicking NFS sharing
Type in the name for the share i.e. NFS-VMFS01
Remove allow anonymous access
Click permissions
Now Change type of access to “Read+Write” then check allow root access.
5. Configure the ESX Server to mount the Window NFS Share as VMFS
Open the VC client and highlight the Vi3 host
In the Configure tab choose Networking
Add networking, VMKernel then pick a vSwitch, then give the VMkernel an IP that is accessible via the NFS host.
Now open the storage option for this host
Click add storage, > Network File System
In the Server Field enter in myserver.mydomain.int
In the Folder field enter /NFS-VMFS01
For the Datastore I also used NFS-VMFS01
Improving Putty settings on Windows
Greetings goes to Planet CentOS
Configure your Putty first, then make entries:
This is important advice. First configure your environment before you start using it. This is especially true for Putty, since you always start of from the default, it is important to configure the default entry before you create entries from these defaults. It will save you a lot of time afterwards to get things straight.
So before you make any changes, open the default template in Category: Session by selecting Default Settings and pressing the Load button.
Make SSH the default.
If you have an older version of Putty, chances are that you have Telnet as the default protocol. Changing it to SSH will probably save you some time when you start Putty out-of-the-blue. For this go to Category: Session and select SSH.
Increase scrollback buffer.
By default Putty buffers 200 lines of output, which is too little in lots of circumstances. And the moment you actually need this number increased, chances are you already lost some information you wanted. So it is wise to increase this number. What I do is go to Category: Window and increase Lines of scrollback to 20000.
Choose a good font.
The newer Putty binaries are able to make use of ClearType which drastically improves the font quality compared to Antialiased. Go to Category: Window > Appearance, choose ClearType and a nice font. I prefer Lucida Console, 9-point.
When you are there, you might want to change the Gap between text and window edge to 3 pixels.
Use proper character encoding.
Nowadays all Linux systems are able to use Unicode (UTF-8) so to make sure that the output in Putty (especially everything non-ascii) looks fine, go to Category: Window > Translation and change the character set to UTF-8, make sure that also the line drawing characters use Unicode as well.
Linux copy-and-pasting.
I prefer to do an implicit copy when selecting and using the middle mouse button for pasting. So I go to Category: Window > Selection and set the Action of mouse buttons to xterm (Right extends, Middle pastes)
When you are there, also enable the option Paste to clipboard in RTF as well as plain text, which is nice when you are copy-and-pasting to emails or text documents that allow fonts and colours. Your console output will look much the same as it does on your screen!
Change dark colours on a black background.
One of the more annoying things with terminal applications (xterm has the same issue) is that by default dark-blue is too dark to be visible on a black background. Not only is this frustrating, it makes the experience for new users so bad that they prefer to disable colours (or hate the ls colour output or syntax highlighting in vim).
So if you are like me, go to Category: Window > Colours and select ANSI Blue in the Select a colour to adjust to Red:74 Green:74 Blue:255. I do the same for ANSI Blue Bold to Red:140 Green:140 Blue:255.
Keeping idle sessions active.
Another frustrating problem is induced by the time-to-live of inactive or idle TCP sessions on firewall or switch configurations. At some companies this is put aggressively low so that TCP sessions that have no activity for 1 minute or even 30 seconds are being dropped. If you are using an SSH connection over such a network device, you have to take care to send keep-alive packets over your idle session. To do this go to Category: Connection and set Seconds between keepalives (0 to turn off) to 25.
Enable X11 forwarding.
Together with Xming, Putty allows you to run graphical Linux applications on your Windows system, so enabling X11 forwarding by default can be useful. To enable this, got to: Connection > SSH > X11 and enable Enable X11 forwarding.
Also dynamic forwarding is very useful to connect to systems on a remote network, even when you do not know in advance having it enabled can be useful. This option however reserves a local port on the system so enabling it by default is not really practical. However you can still enable it from a running Putty by selecting Change settings.
Finally, saving the default.
Now, don't forget to save the changes you just made to the default template. If you loaded the Default Settings at the start, return back to Category: Session and press the Save button. Now you are done !
Putty settings summary.
Category: Session
Connection type: SSH
Category: Window
Lines of scrollback: 20000
Category: Window > Appearance
Font: Lucida Console, 9-point
Font quality: ClearType
Gap between text and window edge: 3
Category: Window > Translation
Character set: UTF-8
Handling of line drawing characters: Unicode
Category: Window > Selection
Action of mouse buttons: xterm (Right extends, Middle pastes)
Paste to clipboard in RTF as well as plain text: enabled
Category: Window > Colours
ANSI Blue: Red:74 Green:74 Blue:255
ANSI Blue Bold: Red:140: Green:140 Blue:255
Category: Connection
Seconds between keepalives (0 to turn off): 25
Category: Connection > SSH > X11
Enable X11 forwarding: enabled