Se pueden descargar de las URL's siguientes:
VMware PowerPoint Icons and Images - 3Q10 1 of 2
VMware PowerPoint Icons and Images - 3Q10 2 of 2
jueves 30 de diciembre de 2010
VMware PowerPoint iconos e imagenes
Para aquellos que les gusta trabajar realizando sus propios diagramas de su infraestructura, VMware pone a disposición de todos unos PowerPoint con iconos y gráficos de dispositivos para ser utilizados.
Se pueden descargar de las URL's siguientes:
VMware PowerPoint Icons and Images - 3Q10 1 of 2
VMware PowerPoint Icons and Images - 3Q10 2 of 2
Se pueden descargar de las URL's siguientes:
VMware PowerPoint Icons and Images - 3Q10 1 of 2
VMware PowerPoint Icons and Images - 3Q10 2 of 2
miércoles 29 de diciembre de 2010
Error Id:10016 DCOM y Kaspersky Antivirus (y 3)
En este post simplemente voy a indicar como aplicar de forma automática el paquete que proporciona Kaspersky Napfix.zip para habilitar o deshabilitar NAP bajo los equipos en los que saca el error 10016 en el visor de eventos.
Nos dirigimos al Administration Kit y sobre el servidor de Administración que tengamos le damos al botón derecho para desplegar el menú.
Seleccionamos "Todas las tareas" y dentro de este "Instalar aplicación".
Nos saldrá un asistente. Le damos a "Siguiente".
La siguiente pantalla nos saldrán todas las aplicaciones que podemos lanzar desde nuestro panel. Le daremos al botón "Nuevo" para crear una nueva. Nos saldrá otro asistente. En la primera pantalla le daremos a "Siguiente". Primero nos pedirá un nombre para la tarea. Le asignamos por ejemplo "Desactivar NAP" y le damos a "Siguiente".
En la siguiente pantalla nos dará a escoger 2 opciones. Escogemos "Crear unpaquete de instalación para el archivo ejecutable especificado". Luego en el botón seleccionar escogemos "disablenap.exe" que será el archivo que ejecutaremos.
Y luego le damos a "Siguiente". "Siguiente" otra vez para acabar de crear la tarea en el servidor. Una vez cargado nos saldrá la opción de "Finalizar".
Una vez le damos a "Finalizar" podremos observar como la tarea nueva que hemos creado ya está preparada para distribuir a los grupos que queramos. Seleccionamos "Desactivar NAP" y luego al botón "Siguiente".
Luego nos dejará escoger si queremos distribuir a un grupo o seleccionar los grupos. Si tenemos ya grupos creados nos resultará más comodo. Una vez seleccionada la opción le damos a "Siguiente" y seleccionamos los equipos administrados. Le damos a "Siguiente" nuevamente y nos cargará una pantalla con 3 opciones. Recomiendo dejar las 3 marcadas y luego darle al botón "Siguiente". Luego nos pedirá el usuario con que distribuirlo. Lo introducimos y le damos a "Siguiente" y "Siguiente hasta finalizar todos los pasos que quedan.
Una vez acabada comprobamos que se ejecuta correctamente.
Nos dirigimos al Administration Kit y sobre el servidor de Administración que tengamos le damos al botón derecho para desplegar el menú.
Seleccionamos "Todas las tareas" y dentro de este "Instalar aplicación".
Nos saldrá un asistente. Le damos a "Siguiente".
La siguiente pantalla nos saldrán todas las aplicaciones que podemos lanzar desde nuestro panel. Le daremos al botón "Nuevo" para crear una nueva. Nos saldrá otro asistente. En la primera pantalla le daremos a "Siguiente". Primero nos pedirá un nombre para la tarea. Le asignamos por ejemplo "Desactivar NAP" y le damos a "Siguiente".
En la siguiente pantalla nos dará a escoger 2 opciones. Escogemos "Crear unpaquete de instalación para el archivo ejecutable especificado". Luego en el botón seleccionar escogemos "disablenap.exe" que será el archivo que ejecutaremos.
Y luego le damos a "Siguiente". "Siguiente" otra vez para acabar de crear la tarea en el servidor. Una vez cargado nos saldrá la opción de "Finalizar".
Una vez le damos a "Finalizar" podremos observar como la tarea nueva que hemos creado ya está preparada para distribuir a los grupos que queramos. Seleccionamos "Desactivar NAP" y luego al botón "Siguiente".
Luego nos dejará escoger si queremos distribuir a un grupo o seleccionar los grupos. Si tenemos ya grupos creados nos resultará más comodo. Una vez seleccionada la opción le damos a "Siguiente" y seleccionamos los equipos administrados. Le damos a "Siguiente" nuevamente y nos cargará una pantalla con 3 opciones. Recomiendo dejar las 3 marcadas y luego darle al botón "Siguiente". Luego nos pedirá el usuario con que distribuirlo. Lo introducimos y le damos a "Siguiente" y "Siguiente hasta finalizar todos los pasos que quedan.
Una vez acabada comprobamos que se ejecuta correctamente.
martes 28 de diciembre de 2010
Deshabilitar la hibernación en Windows 2008
En algún momento, bajo Windows 2008 si tenemos algún controlador de dominio y nos quedamos sin espacio, podemos deshabilitar la hibernacion. Con esto conseguiremos 2Gb o más de espacio.
Para ello podemos seguir los siguientes pasos.
Para ello podemos seguir los siguientes pasos.
- Abriremos una ventana de MS-DOS en modo Administrador.
- Ejecutamos el siguiente comando: powercfg.exe /hibernate off
- Ejecutamos Intro
martes 21 de diciembre de 2010
Gira Up To Secure 2011
La Gira Up to Secure 2011 ya está aquí. Un año más recorrerá 10 ciudades españolas abordando temas de actualidad relativos a seguridad informática y, para ello, contará con la participación de expertos en la materia aportados por empresas profesionalizadas en Seguridad Informática
- 11 de Enero, Pamplona
- 12 de Enero, Zaragoza
- 13 de Enero, Barcelona
- 18 de Enero, Valladolid
- 19 de Enero, Vigo
- 20 de Enero, A Coruña
- 25 de Enero, Valencia
- 26 de Enero, Madrid
- 27 de Enero, Tenerife
09:00 – 09:30 Registro
09:30 – 10:15 Mac OS X & Malware en tu empresa
Durante esta sesión se mostrará como aquellos tiempos en que se podía pensar que vivir con sistemas operativos Mac OS X sin riesgo a sufrir una mala experiencia con el malware han terminado. Si a esto le añadimos la cada día más creciente participación de los equipos de Apple en las empresas, el riesgo se dispara. En esta sesión verás cómo poder proteger también esa tecnología sin necesidad de cambiar la forma en que gestionas tu empresa. Desde Bitdefender obtendremos soluciones.
10:15 – 11:00 Protege tus teléfonos móviles... forever!
Los aún llamados “teléfonos móviles” son equipos informáticos de gama alta que almacenan datos privados, secretos comerciales y mucho más. Son una herramienta de trabajo que nos acompaña de viaje en el tren, avión e, incluso, navegando en vacaciones. ¿Quieres proteger tus datos y tu dispositivo aun cuando lo hayas perdido? En esta sesión, los profesionales de Telefónica te darán soluciones.
11:00 – 11:45 Café
11:45 – 12:30 Quest Software: ¿Son seguras las soluciones en “la Nube”?
El uso de soluciones basadas en Cloud Computing se está extendiendo rápidamente. Pero no todo el mundo confía en la seguridad que ofrecen las distintas compañías de servicios y muchos clientes temen por la integridad de sus datos. Quest Software quiere desmitificar las ideas relativas a la carencia de seguridad en la Nube y mostrar sus soluciones Quest OnDemand bajo plataforma Windows Azure.
12:30 – 13:15 La seguridad Sí importa: Windows Live & IE9
Hoy en día, la gran mayoría de profesionales cuenta con correos personales que coordina con los correos corporativos, correos personales que extienden la vida personal y profesional de los usuarios a través de Internet. En esta sesión veremos los problemas de seguridad y las herramientas que ofrecen los servicios de Windows Live para protegernos del spam, los ataques de spoofing, el robo de contraseñas y los ataques de botnets. Sí, ven a verlo. Esta charla será impartida por Chema Alonso, Microsoft MVP en Enterprise Security, de Informática64 y escritor del blog “Un informático en el lado del Mal” http://www.elladodelmal.com.
13:15 – 13:30 Preguntas & Respuestas
viernes 17 de diciembre de 2010
Imagen ISO Microsoft de seguridad de diciembre de 2010
Detalles rápidos
Versión: 913086
Boletines de seguridad: MS10-070 MS10-077 MS10-083 MS10-090 MS10-091 MS10-092 MS10-094 MS10-095 MS10-096 MS10-097 MS10-098 MS10-099 MS10-100 MS10-101 MS10-102
Artículos de Knowledge Base (KB): KB2160841 KB2207559 KB2296199 KB2305420 KB2345316 KB2385678 KB2416400 KB2416472 KB2423089 KB2436673 KB2440591 KB2442962 KB2443105 KB2447961 KB979688
Descargar imagen ISO
Versión: 913086
Boletines de seguridad: MS10-070 MS10-077 MS10-083 MS10-090 MS10-091 MS10-092 MS10-094 MS10-095 MS10-096 MS10-097 MS10-098 MS10-099 MS10-100 MS10-101 MS10-102
Artículos de Knowledge Base (KB): KB2160841 KB2207559 KB2296199 KB2305420 KB2345316 KB2385678 KB2416400 KB2416472 KB2423089 KB2436673 KB2440591 KB2442962 KB2443105 KB2447961 KB979688
Descargar imagen ISO
martes 7 de diciembre de 2010
Códigos de respuesta de SMTP
A veces, cuando enviamos un e-mail, este puede darnos un error en el envío con un código.
Cada código tiene un significado. A continuación en una URL que he encontrado, detalla el listado.
Connection Manager Automatic & Manual Blocks:
Spool Manager:
Attachment Manager:
Cada código tiene un significado. A continuación en una URL que he encontrado, detalla el listado.
- 451 not currently accepting mail from your ip - psmtp
- 550 mailbox unavailable - psmtp
- 552 storage allocation exceeded - psmtp
- 553 mailbox name not allowed - psmtp
- 554 mailbox limit exceeded - psmtp
- 554 no relaying allowed - psmtp
- 554 transaction failed - psmtp
- 571 spam source blocked - psmtp
- 571 incorrect ip - psmtp
Delivery Manager:
- 421 low on resources - psmtp
- 421 Mail process is restarting. Please try sending your message again - psmtp
- 421 Process restarting, please try again - psmtp
- 421 please try again - psmtp
- 421 Timeout - psmtp
- 451 Archive storage failure - psmtp
- 451 can’t connect to domain - psmtp
- 451 Can't deliver to end ISP, try again - psmtp
- 451 Client timed out - psmtp
- 451 Could not connect to %s port %d\r\n",host,port) - psmtp
- 451 Failed in remote data - psmtp
- 451 Failed in remote data xmission - psmtp
- 451 failed to connect to quarantine - psmtp
- 451 Failed to reconnect to ", self->domain)) - psmtp
- 451 Failed in remote RSET - psmtp
- 451 Internal timeout - psmtp
- 421 Mail process is restarting. Please try sending your message again - psmtp
- 451 recipient not currently accepting mail from your ip - psmtp
- 451 Recipient not in same HALO group - psmtp
- 451 Recipients not all at same mail host - psmtp
- 451 Reinject host DATA failed - psmtp
- 451 Reinject host failed in DATA - psmtp
- 451 Reinject host not reachable - psmtp
- 451 Reinject host refused helo - psmtp
- 451 Reinject host refused mail from: - psmtp
- 451 Remote connection lost - psmtp
- 451 Remote connection lost in HELO - psmtp
- 451 Remote connection lost in MAIL FROM: - psmtp
- 451 Remote connection lost in RCPT TO: - psmtp
- 451 Remote connection lost in DATA - psmtp
- 451 Remote connection lost at . - psmtp
- 451 Remote connection lost in QUIT - psmtp
- 451 Remote connection lost in RSET - psmtp
- 451 Remote connection lost in NOOP - psmtp
- 451 Temporary cache delay - psmtp
- 451 Temporary failure - psmtp
- 451 Temporary transmission problem, try again - psmtp
- 451 Too many invalid recipients per session - psmtp
- 451 Too many recipients for one session - psmtp
- 451 Transmission incomplete, try again later - psmtp
- 451 can’t connect to domain - psmtp
Non Account Bouncing:
- 550 no such user - psmtp
Blatant Spam Blocking:
- 571 message refused - psmtp
Virus Blocking:
- 451 Possible Virus Detected, try again later - psmtp
- 451 Please try again for virus detection - psmtp
- 571 Virus Blocked - psmtp
Content Manager:
- 582 This message violates our email policy - psmtp
- 582 custom error message - psmtp
- 552 Message too large - psmtp
- 582 The file attached violates our email policy - psmtp
- 582 custom error message - psmtp
TLS:
- 451 Failed in remote STARTTLS - psmtp
- 451 failed to initialize TLS connection to quarantine - psmtp
- 451 Remote connection lost in STARTTLS - psmtp
- 451 Remote refuses STARTTLS by policy - psmtp
- 451 STARTTLS is required for this sender - psmtp
- 451 STARTTLS is required for this recipient - psmtp
- 451 TLS-only recipient mixed in with non-TLS recipients - please retry this recipient - psmtp
SMTP Codes Generated by MTAs and Relayed by Message Security Service
SMTP codes that the message security service simply passes on behalf of sending or receiving MTAs do not contain the - psmtp suffix.
Here is a list of SMTP codes generated by MTAs (along with brief explanations).
101 Cannot open connection (The sending MTA cannot open a connection to the receving MTA)
200 Nonstandard success response (see rfc876)
211 System status or System help reply (Mail server status, or reply to request for Help information)
214 Help message (Reply to Help command, URL to information about the SMTP software running on the server)
220 domain Service ready (The mail service is running)
221 domain Service closing transmission channel (Server is ending mail session, no more mail to send)
250 Requested mail action okay, completed (Message successfully delivered)
251 User not local; will forward to (The specified user is not local to the server, but the server will forward the mail message)
252 Cannot VRFY user, but will accept message and attempt delivery (Address appears valid but server cannot verify; server will attempt to deliver message)
354 Start mail input; end with. (Server has received From and To information, and is asking for message body)
421 domain Service not available, closing transmission channel (Mail transfer service is unavailable)
450 Requested mail action not taken: mailbox unavailable (Server could not deliver message, mailbox unavailable, possibly due to server maintenance on mailbox or server down)
451 Requested action aborted: local error in processing (Indicates different problems like bad configuration of sending server, resource constraint on sending server, local firewall stripping out SMTP commands)
452 Requested action not taken: insufficient system storage (Server disk space is full)
500 Syntax error, command unrecognized (Last command not recognized as valid SMTP command, command improperly formatted, command too long)
501 Syntax error in commands or arguments (Correct command but bad syntax in commands or arguments, often a malformed email address)
502 Command not implemented (Last command recognized, but not implemented by server)
503 Bad sequence of commands (Last command sent out of sequence, for example, DATA sent before RECV, possibly due to dropped packet)
550 Requested action not taken: mailbox unavailable (Mailbox can't be found or you don't have access rights)
551 User not local; please try forward path (The specified user is not local to the server and the message was not delivered, but the server returns a forwarding address)
552 Requested mail action aborted:exceeded storage allocation (Mailbox has exceeded storage allocation)
553 Requested action not taken: mailbox name not allowed (Email address was not syntactically correct)
554 Transaction failed (Transaction failed for unknown reason)
SMTP Reply Codes Grouped by SMTP Command
The following list groups the SMTP reply codes by the SMTP commands with which they can be associated. This can help you identify at what point the process failed.
HELO
250, 421, 500, 501, 504, 521
EHLO
250, 421, 500, 501, 504, 521
MAIL
250, 421, 451, 452, 500, 501, 552
RCPT
250, 251, 421, 450, 451, 452, 500, 501, 503, 521, 550, 551, 552, 553
DATA
354, 421, 451, 500, 501, 503, 554
SEND
250, 421, 451, 452, 500, 501, 502, 552
SOML
250, 421, 451, 452, 500, 501, 502, 552
SAML
250, 421, 451, 452, 500, 501, 502, 552
RSET
200, 250, 421, 500, 501, 504
VRFY
250, 251, 421, 500, 501, 502, 504, 550, 551, 553
EXPN
250, 421, 500, 501, 502, 504, 550
HELP
211, 214, 421, 500, 501, 502, 504
NOOP
200, 250, 421, 500
QUIT
221, 500
TURN
250, 500, 502, 503
Enhanced SMTP Reply Codes
The following list contains enhanced SMTP reply codes used by some mail servers. It also contains some notes and recommendations regarding Microsoft Exchange Server.
2.0.0 (nonstandard success response, see rfc876).
2.1.1 System status, or system help reply.
2.1.4 Help message.
2.2.0 Service ready.
2.2.1 Service closing transmission channel.
2.5.0 Requested mail action okay, completed.
2.5.1 User not local; will forward to.
3.5.4 Start mail input; end with ". "
4.2.1 Service not available, closing transmission channel.
4.2.2 The recipient has exceeded their mailbox limit. It could also be that the delivery directory on the Virtual server has exceeded its limit (default: 22 MB).
4.3.1 Not enough disk space on the delivery server. Microsoft says this NDR may be reported as an out-of-memory error.
4.3.2 Classic temporary problem: the Administrator has frozen the queue.
4.4.1 Intermittent network connection. The server has not yet responded. Classic temporary problem. If it persists, you will also receive a 5.4.x status code.
4.4.2 The server started to deliver the message but the connection was broken.
4.4.6 Too many hops. The message is likely looping.
4.4.7 Problem with a timeout. Check receiving server connectors.
4.4.9 A DNS problem. Check your smart host setting on the SMTP connector. For example, verify that the SMTP format is correct. Also, use square brackets in the IP address [197.89.1.4]. You can get this same NDR error if you have been deleting routing groups.
4.5.0 Requested mail action not taken: mailbox unavailable.
4.5.1 Requested action aborted: local error in processing.
4.5.2 Requested action not taken: insufficient system storage.
4.6.5 Multi-language situation. Your server does not have the correct language code page installed.
5.0.0 Syntax error, command unrecognized. You receive this NDR when you try to send email via telnet and make a typing mistake. More likely, a routing-group error, no routing connector, or no suitable address space in the connector. (Try adding * in the address space.)
5.0.1 Syntax error in parameters or arguments.
5.0.2 Command not implemented.
5.0.3 Bad sequence of commands.
5.0.4 Command parameter not implemented.
5.1.x Problem with email address.
5.1.0 Often seen with contacts. Check the recipient address.
5.1.1 Another problem with the recipient address. Possibly the user was moved to another server in Active Directory. Maybe an Outlook client replied to a message while offline.
5.1.3 Another problem with contacts. Address field maybe empty. Check the address information.
5.1.4 Two objects have the same address, which confuses the categorizer.
5.1.5 Destination mailbox address invalid.
5.1.6 Problem with homeMDB or msExchHomeServerName - check how many users are affected. Sometimes running RUS (Recipient Update Service) cures this problem. Mailbox may have moved.
5.1.7 Problem with senders mail attribute, check properties sheet in ADUC.
5.2.x NDR caused by a problem with the large size of the email.
5.2.1 The message is too large. Else it could be a permissions problem. Check the recipient’s mailbox.
5.2.2 Sadly, the recipient has exceeded their mailbox limit.
5.2.3 Recipient cannot receive messages this big. Server or connector limit exceeded.
5.2.4 Most likely, a distribution list or group is trying to send an email. Check where the expansion server is situated.
5.3.0 Problem with MTA. Someone may have been editing the registry to disable the MTA / Store driver.
5.3.1 Mail system full. Possibly a Standard edition of Exchange reached the 16 GB limit.
5.3.2 System not accepting network messages. Look outside Exchange for a connectivity problem.
5.3.3 Remote server has insufficient disk space to hold email. Check SMTP log.
5.3.4 Message too big. Check limits, System Policy, connector, virtual server.
5.3.5 Multiple Virtual Servers are using the same IP address and port. See Microsoft TechNet article: 321721 Sharing SMTP. Email probably looping.
5.4.0 DNS Problem. Check the Smart host, or check your DNS. It means that there is no DNS server that can resolve this email address. Could be a Virtual Server SMTP address.
5.4.1 No answer from host. Not Exchange’s fault, check connections.
5.4.2 Bad connection.
5.4.3 Routing server failure. No available route.
5.4.4 Cannot find the next hop. Check the Routing Group Connector. Perhaps you have Exchange servers in different Routing Groups, but no connector.
5.4.6 Looping problem A contact has the same email address as an Active Directory user. One user is probably using an Alternate Recipient with the same email address as a contact.
5.4.7 Delivery time-out. Message is taking too long to be delivered.
5.4.8 Microsoft advises to check your recipient policy. SMTP address should be cp.com NOT server.cp.com.
5.5.0 Requested action not taken: mailbox unavailable. Underlying SMTP 500 error. Sending server tried EHLO, the recipient’s server did not understand and returned a 550 or 500 error. Set up SMTP logging.
5.5.2 Possibly the disk holding the operating system is full. Or "Requested mail action aborted: exceeded storage allocation" if you are executing an SMTP.
5.5.3 More than 5,000 recipients. Check the Global Settings, Message Delivery properties. Or "Requested action not taken: mailbox name not allowed" if you are executing an SMTP.
5.5.4 Transaction failed.
5.5.5 Wrong protocol version.
5.6.3 More than 250 attachments.
5.7.1 Permissions problem. For some reason the sender is not allowed to email this account. Perhaps an anonymous user is trying to send mail to a distribution list.
Check SMTP Virtual Server Access Tab. Allow computers that successfully authenticate to relay.
User may have a manually created email address that does not match a System Policy.
Exchange 2003 SBS gives this error if IMF is set to "reject" and the message falls into that top threshold. Click System Manager > Global Settings > Message Delivery (right click > Properties) > Intelligent Message Filtering; then set "When blocking messages", to No Action, and see if that message goes away. The threshold might need to be set higher if it's happening a lot.
5.7.2 Distribution list cannot expand and so is unable to deliver its messages.
5.7.3 Check external IP address of ISA server. Make sure it matches the SMTP publishing rule.
5.7.4 Extra security features not supported. Check delivery server settings.
5.7.5 Cryptographic failure. Try a plain message with encryption.
5.7.6 Certificate problem, encryption level maybe to high.
5.7.7 Message integrity problem.
Note: See rfc2821 for the basic specification of SMTP; see also rfc1123 for important additional information. See rfc1893 and rfc2034 for information about enhanced status codes. Check the RFC index for further mail-related RFCs.
SMTP codes that the message security service simply passes on behalf of sending or receiving MTAs do not contain the - psmtp suffix.
Here is a list of SMTP codes generated by MTAs (along with brief explanations).
101 Cannot open connection (The sending MTA cannot open a connection to the receving MTA)
200 Nonstandard success response (see rfc876)
211 System status or System help reply (Mail server status, or reply to request for Help information)
214 Help message (Reply to Help command, URL to information about the SMTP software running on the server)
220 domain Service ready (The mail service is running)
221 domain Service closing transmission channel (Server is ending mail session, no more mail to send)
250 Requested mail action okay, completed (Message successfully delivered)
251 User not local; will forward to (The specified user is not local to the server, but the server will forward the mail message)
252 Cannot VRFY user, but will accept message and attempt delivery (Address appears valid but server cannot verify; server will attempt to deliver message)
354 Start mail input; end with
421 domain Service not available, closing transmission channel (Mail transfer service is unavailable)
450 Requested mail action not taken: mailbox unavailable (Server could not deliver message, mailbox unavailable, possibly due to server maintenance on mailbox or server down)
451 Requested action aborted: local error in processing (Indicates different problems like bad configuration of sending server, resource constraint on sending server, local firewall stripping out SMTP commands)
452 Requested action not taken: insufficient system storage (Server disk space is full)
500 Syntax error, command unrecognized (Last command not recognized as valid SMTP command, command improperly formatted, command too long)
501 Syntax error in commands or arguments (Correct command but bad syntax in commands or arguments, often a malformed email address)
502 Command not implemented (Last command recognized, but not implemented by server)
503 Bad sequence of commands (Last command sent out of sequence, for example, DATA sent before RECV, possibly due to dropped packet)
550 Requested action not taken: mailbox unavailable (Mailbox can't be found or you don't have access rights)
551 User not local; please try forward path (The specified user is not local to the server and the message was not delivered, but the server returns a forwarding address)
552 Requested mail action aborted:exceeded storage allocation (Mailbox has exceeded storage allocation)
553 Requested action not taken: mailbox name not allowed (Email address was not syntactically correct)
554 Transaction failed (Transaction failed for unknown reason)
SMTP Reply Codes Grouped by SMTP Command
The following list groups the SMTP reply codes by the SMTP commands with which they can be associated. This can help you identify at what point the process failed.
HELO
250, 421, 500, 501, 504, 521
EHLO
250, 421, 500, 501, 504, 521
250, 421, 451, 452, 500, 501, 552
RCPT
250, 251, 421, 450, 451, 452, 500, 501, 503, 521, 550, 551, 552, 553
DATA
354, 421, 451, 500, 501, 503, 554
SEND
250, 421, 451, 452, 500, 501, 502, 552
SOML
250, 421, 451, 452, 500, 501, 502, 552
SAML
250, 421, 451, 452, 500, 501, 502, 552
RSET
200, 250, 421, 500, 501, 504
VRFY
250, 251, 421, 500, 501, 502, 504, 550, 551, 553
EXPN
250, 421, 500, 501, 502, 504, 550
HELP
211, 214, 421, 500, 501, 502, 504
NOOP
200, 250, 421, 500
QUIT
221, 500
TURN
250, 500, 502, 503
Enhanced SMTP Reply Codes
The following list contains enhanced SMTP reply codes used by some mail servers. It also contains some notes and recommendations regarding Microsoft Exchange Server.
2.0.0 (nonstandard success response, see rfc876).
2.1.1 System status, or system help reply.
2.1.4 Help message.
2.2.0 Service ready.
2.2.1 Service closing transmission channel.
2.5.0 Requested mail action okay, completed.
2.5.1 User not local; will forward to.
3.5.4 Start mail input; end with ". "
4.2.1 Service not available, closing transmission channel.
4.2.2 The recipient has exceeded their mailbox limit. It could also be that the delivery directory on the Virtual server has exceeded its limit (default: 22 MB).
4.3.1 Not enough disk space on the delivery server. Microsoft says this NDR may be reported as an out-of-memory error.
4.3.2 Classic temporary problem: the Administrator has frozen the queue.
4.4.1 Intermittent network connection. The server has not yet responded. Classic temporary problem. If it persists, you will also receive a 5.4.x status code.
4.4.2 The server started to deliver the message but the connection was broken.
4.4.6 Too many hops. The message is likely looping.
4.4.7 Problem with a timeout. Check receiving server connectors.
4.4.9 A DNS problem. Check your smart host setting on the SMTP connector. For example, verify that the SMTP format is correct. Also, use square brackets in the IP address [197.89.1.4]. You can get this same NDR error if you have been deleting routing groups.
4.5.0 Requested mail action not taken: mailbox unavailable.
4.5.1 Requested action aborted: local error in processing.
4.5.2 Requested action not taken: insufficient system storage.
4.6.5 Multi-language situation. Your server does not have the correct language code page installed.
5.0.0 Syntax error, command unrecognized. You receive this NDR when you try to send email via telnet and make a typing mistake. More likely, a routing-group error, no routing connector, or no suitable address space in the connector. (Try adding * in the address space.)
5.0.1 Syntax error in parameters or arguments.
5.0.2 Command not implemented.
5.0.3 Bad sequence of commands.
5.0.4 Command parameter not implemented.
5.1.x Problem with email address.
5.1.0 Often seen with contacts. Check the recipient address.
5.1.1 Another problem with the recipient address. Possibly the user was moved to another server in Active Directory. Maybe an Outlook client replied to a message while offline.
5.1.3 Another problem with contacts. Address field maybe empty. Check the address information.
5.1.4 Two objects have the same address, which confuses the categorizer.
5.1.5 Destination mailbox address invalid.
5.1.6 Problem with homeMDB or msExchHomeServerName - check how many users are affected. Sometimes running RUS (Recipient Update Service) cures this problem. Mailbox may have moved.
5.1.7 Problem with senders mail attribute, check properties sheet in ADUC.
5.2.x NDR caused by a problem with the large size of the email.
5.2.1 The message is too large. Else it could be a permissions problem. Check the recipient’s mailbox.
5.2.2 Sadly, the recipient has exceeded their mailbox limit.
5.2.3 Recipient cannot receive messages this big. Server or connector limit exceeded.
5.2.4 Most likely, a distribution list or group is trying to send an email. Check where the expansion server is situated.
5.3.0 Problem with MTA. Someone may have been editing the registry to disable the MTA / Store driver.
5.3.1 Mail system full. Possibly a Standard edition of Exchange reached the 16 GB limit.
5.3.2 System not accepting network messages. Look outside Exchange for a connectivity problem.
5.3.3 Remote server has insufficient disk space to hold email. Check SMTP log.
5.3.4 Message too big. Check limits, System Policy, connector, virtual server.
5.3.5 Multiple Virtual Servers are using the same IP address and port. See Microsoft TechNet article: 321721 Sharing SMTP. Email probably looping.
5.4.0 DNS Problem. Check the Smart host, or check your DNS. It means that there is no DNS server that can resolve this email address. Could be a Virtual Server SMTP address.
5.4.1 No answer from host. Not Exchange’s fault, check connections.
5.4.2 Bad connection.
5.4.3 Routing server failure. No available route.
5.4.4 Cannot find the next hop. Check the Routing Group Connector. Perhaps you have Exchange servers in different Routing Groups, but no connector.
5.4.6 Looping problem A contact has the same email address as an Active Directory user. One user is probably using an Alternate Recipient with the same email address as a contact.
5.4.7 Delivery time-out. Message is taking too long to be delivered.
5.4.8 Microsoft advises to check your recipient policy. SMTP address should be cp.com NOT server.cp.com.
5.5.0 Requested action not taken: mailbox unavailable. Underlying SMTP 500 error. Sending server tried EHLO, the recipient’s server did not understand and returned a 550 or 500 error. Set up SMTP logging.
5.5.2 Possibly the disk holding the operating system is full. Or "Requested mail action aborted: exceeded storage allocation" if you are executing an SMTP.
5.5.3 More than 5,000 recipients. Check the Global Settings, Message Delivery properties. Or "Requested action not taken: mailbox name not allowed" if you are executing an SMTP.
5.5.4 Transaction failed.
5.5.5 Wrong protocol version.
5.6.3 More than 250 attachments.
5.7.1 Permissions problem. For some reason the sender is not allowed to email this account. Perhaps an anonymous user is trying to send mail to a distribution list.
Check SMTP Virtual Server Access Tab. Allow computers that successfully authenticate to relay.
User may have a manually created email address that does not match a System Policy.
Exchange 2003 SBS gives this error if IMF is set to "reject" and the message falls into that top threshold. Click System Manager > Global Settings > Message Delivery (right click > Properties) > Intelligent Message Filtering; then set "When blocking messages", to No Action, and see if that message goes away. The threshold might need to be set higher if it's happening a lot.
5.7.2 Distribution list cannot expand and so is unable to deliver its messages.
5.7.3 Check external IP address of ISA server. Make sure it matches the SMTP publishing rule.
5.7.4 Extra security features not supported. Check delivery server settings.
5.7.5 Cryptographic failure. Try a plain message with encryption.
5.7.6 Certificate problem, encryption level maybe to high.
5.7.7 Message integrity problem.
Note: See rfc2821 for the basic specification of SMTP; see also rfc1123 for important additional information. See rfc1893 and rfc2034 for information about enhanced status codes. Check the RFC index for further mail-related RFCs.
jueves 2 de diciembre de 2010
Agregar LUN's de forma manual en un ESX porque no aparecen automáticamente
Si cuando reinstalamos un servidor ESX y al reconfigurarlo no detecta nuestras LUN’s correctamente, deberemos acceder por SSH o desde la propia consola de la máquina y realizar los siguientes pasos:
Listamos las LUN’s disponibles con el comando
Como podemos observar en este caso, ha listado 4 LUN’s.
Para agregarlas deberemos ejecutar el comando esxcfg-volume –M “NOMBRE DE LA LUN” (comillas incluidas). En el nombre de la LUN deberemos escribirlo tal cual nos ha salido en el listado.
LUN01-vmware.vm1 (1)
LUN02-vmware.util
LUN04-vmware.vm2
LUN07-vmware.vm3
Listamos las LUN’s disponibles con el comando
[root@vmware05 ~]# esxcfg-volume –lA continuación nos listará las LUN’s.
[root@vmware05 ~]# esxcfg-volume -l
VMFS3 UUID/label: 49e8ddc8-c12cfa3d-04bc-001a64962ff4/LUN01-vmware.vm1 (1)
Can mount: Yes
Can resignature: No (the volume is being actively used)
Extent name: naa.60060160852227004093f96a5712df11:1 range: 0 - 511743 (MB)
VMFS3 UUID/label: 48db75dd-748b6cb1-2eb3-001a6498d508/LUN02-vmware.util
Can mount: Yes
Can resignature: Yes
Extent name: naa.6006016085222700e6f873d05212df11:1 range: 0 - 35327 (MB)
VMFS3 UUID/label: 48e48d6b-e6b03286-77cb-001a6498d506/LUN04-vmware.vm2
Can mount: Yes
Can resignature: No (the volume is being actively used)
Extent name: naa.6006016085222700140e45945712df11:1 range: 0 - 412159 (MB)
VMFS3 UUID/label: 49955d41-92cb8ac1-9005-001a649634d4/LUN07-vmware.vm3
Can mount: Yes
Can resignature: No (the volume is being actively used)
Extent name: naa.600601608522270006fd13cb5712df11:1 range: 0 - 204543 (MB)
Como podemos observar en este caso, ha listado 4 LUN’s.
Para agregarlas deberemos ejecutar el comando esxcfg-volume –M “NOMBRE DE LA LUN” (comillas incluidas). En el nombre de la LUN deberemos escribirlo tal cual nos ha salido en el listado.
LUN01-vmware.vm1 (1)
LUN02-vmware.util
LUN04-vmware.vm2
LUN07-vmware.vm3
[root@vmware05 ~]# esxcfg-volume -M "LUN01-vmware.vm1 (1)"
Persistently mounting volume LUN01-vmware.vm1 (1)
Una vez agregadas, si nos vamos a nuestro VirtualCenter, nos dirigimos a la máquina ESX, la pestaña Configuration y el menú Storage. Le damos a la opción “Rescan all…” para que la detecte. Debería aparecer después de esta acción.
Suscribirse a:
Entradas (Atom)