an error occurs if you try to provision a share remotely and if the highly available service or the application group is not local to the cluster node. You may receive the following error message:
<Client_Access_Point_Name>: Virtual Disk Service initialization failed. It is possible that the connection is blocked by Windows firewall. A VDS (Virtual Disk Service) error occurred while performing the requested operation.
To enable the provision shares functionality remotely, modify Windows Firewall on all nodes in the cluster. To do this, follow these steps:
| 1. |
Click Start, click Control Panel, and then double-click Windows Firewall. |
| 2. |
Click Change settings. |
| 3. |
Click the Exception tab, click to select the Remote Volume Management check box. |
| 4. |
Click OK. |
You can find additional instructions to disable Teredo in this TechNet article: http://technet2.microsoft.com/WindowsVista/en/library/91d35c9f-3049-44f4-b711-743dc152c7c31033.mspx?mfr=true.
ERROR
Verifying that a node does not have multiple adapters connected to the same subnet.
Verifying that each node has at least one adapter with a defined default gateway.
Verifying that there are no node adapters with the same EUI-48 physical address.
Verifying that there are no duplicate IP addresses between any pair of nodes.
Found duplicate IP address fe80::100:7f:fffe%12 on node twilk-amd1.twilk-dom2.com adapter Local Area Connection* 8 and node twilk-amd2.twilk-dom2.com adapter Local Area Connection* 8.
Checking that nodes are consistently configured with IPv4 and/or IPv6 addresses.
SOLUTION
Si alguna vez se te colgo un servicio o quedo en estado START_PENDING y no sabias como matarlo.... Aca te paso la solucion
- Go to the command-prompt and query the service (e.g. the SMTP service) by using sc:
sc queryex SMTPSvc
- This will give you the following information:
SERVICE_NAME: SMTPSvc
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE, PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
PID : 388
FLAGS :
or something like this (the "state" will mention stopping).
- Over here you can find the process identifier (PID), so it's pretty easy to kill the associated process either by using the task manager or by using taskkill:
taskkill /PID 388 /F
where the /F flag is needed to force the process kill (first try without the flag).
Despues de instalar el ULTIMO update relacionado con DNS, las personas que tienen zone alarm instalado, esperimentan problemas de navegacion.
Tanto Microsoft como Zonealarm están trabajando de manera activa para resolver este problema. En una entrevista reciente a un representante de Zonealarm, se informó que estarán liberando un parche para solucionar este problema. Zonealarm puede ser contactado en http://www.zonealarm.com/
NO recomendamos desintalar la actualización de seguridad, pues dejaría a la máquina vulnerable.
Mas info pero del lado del Vendor:
http://download.zonealarm.com/bin/free/pressReleases/2008/LossOfInternetAccessIssue.html
Ya esta diponible la version 8 de Internet Explorar, para testear en desarrollo que todas las aplicaciones sigan funcionando. El mismo trae varios cambios en el paradigma de objetos, por lo que se recomienda probarlo.
http://www.microsoft.com/windows/products/winfamily/ie/ie8/default.mspx
Si perdiste las PASS del usuario anonimo y no te funciona tu sitio, podes obtener las misma con el siguiente script.
Script VBS
Dim IIsObject, SiteObject
Set IIsObject = GetObject ("IIS://localhost/w3svc")
Wscript.Echo Get_IUSR_Password(IIsObject)
Wscript.Echo Get_IWAM_Password(IIsObject)
Function Get_IUSR_Password(IIsObject)
on error resume Next
Dim Out
Out = Out & vbCrLf & "<br>AnonymousUserName = " & IIsObject.Get("AnonymousUserName")
Out = Out & vbCrLf & "<br>AnonymousUserPass = " & IIsObject.Get("AnonymousUserPass")
If err=0 Then Out = vbCrLf & "<br>Path:" & IIsObject.AdsPath & Out
Get_IUSR_Password = Out
End Function
Function Get_IWAM_Password(IIsObject)
on error resume Next
Dim Out
Out = Out & vbCrLf & "<br>WAMUserName = " & IIsObject.Get("WAMUserName")
Out = Out & vbCrLf & "<br>WAMUserPass = " & IIsObject.Get("WAMUserPass")
If err=0 Then Out = vbCrLf & "<br>Path:" & IIsObject.AdsPath & Out
Get_IWAM_Password = Out
End Function
Resultado
C:\>cscript get.vbs
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
<br>Path:IIS://localhost/w3svc
<br>AnonymousUserName = IUSR_sarasa
<br>AnonymousUserPass = O2SOgx7JPZ-4Ph
<br>Path:IIS://localhost/w3svc
<br>WAMUserName = IWAM_sarasa
<br>WAMUserPass = JLgR8BZg8_&7Ki
HttpWatch is an HTTP viewer and debugger that integrates with Internet Explorer to provide seamless HTTP and HTTPS monitoring without leaving the browser window.
http://www.httpwatch.com/?utm_source=iis.net&utm_medium=banner&utm_content=slot2&utm_campaign=iis.net+slot2
Queria compartir con ustedes un problema que se me presento en un FARM de IIS 6.0. El mismo consta de 3 IIS 6.0 como FrontEnd y un cluster windows 2003R2 para alojar los contenidos, que son accedidos via UNC.
Uno de los sistemas de FrontEnd cada tanto dejaba de atender los request de HTTP. Y no se presentaban sintomas de carga tanto de CPU como RED... Luego de investigar un tiempo encotre que existen ciertos valores de registry que deben ser modificados cuando se configura IIS con los contenidos via UNC.
Esta nota se encontro a raiz de un evento en particular que se encotro en el IIS, el cual paso a detallar.
Event ID 101 on IIS server:
Event Type:Warning
Event Source:W3SVC
Event Category:None
Event ID:101
Date:9/5/2002
Time:8:07:28 AM
User:N/A
Computer:<server name>
Description:
The server was unable to add the virtual root '/<virtual dir name>' for the directory '\\<servername>\<share>\' due to the following error: The network BIOS command limit has been reached. The data is the error code. For additional information specific to this message please visit the Microsoft Online Support site located at: http://search.support.microsoft.com/search/?adv=1.
La solucion a este problema se encuentra detallada en el KB 221790 http://support.microsoft.com/kb/221790/
Espero a alguien le sirva.