Re: WBEM ConnectServer taking too long.
From: Ivan Brugiolo [MSFT] (ivanbrug_at_online.microsoft.com)
Date: 04/21/04
- Next message: Ivan Brugiolo [MSFT]: "Re: Win32_Schedule and suspend"
- Previous message: Ryan Ackerman: "Re: Creating Remote processes"
- In reply to: Paul Hulatt: "WBEM ConnectServer taking too long."
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 21 Apr 2004 00:38:43 -0700
Try to use the IP address you have resolved beforehand.
The DCOM activation process against NT4 is really
a special case in RPCSS on the newer platforms.
-- This posting is provided "AS IS" with no warranties, and confers no rights. Use of any included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm "Paul Hulatt" <paul@hulatt.co.uk> wrote in message news:864b7ca4.0404190734.6a4e8f37@posting.google.com... > I have a requirement to connect to a remote server (in the same > domain) and modify a IIS (IIS6 on Win2003) websites IPDeny list and > WMI seems the best way to achieve this. > > I have a created a script which does exactly what I need which works > flawlessly on my development station (WinXP Pro), however when I copy > the script onto the target machine (NT4) and run it, it takes > approximately 6 minutes to connect to the remote machine > (ConnectServer call below). Once connected, everything works as > expected. > > Can anyone shed any light on why it takes so long for the > ConnectServer command to complete or what I can do to fix it? The > code I use is: - > > Set lctr = CreateObject("WbemScripting.swbemLocator") > Set IIS = lctr.Connectserver(txtServer.Text, > "root\MicrosoftIISv2", usr, pwd) > Set IISSec = IIS.get("IIsIPSecuritySetting='W3SVC/2/root'") > > Thanks in advance. > > Paul
- Next message: Ivan Brugiolo [MSFT]: "Re: Win32_Schedule and suspend"
- Previous message: Ryan Ackerman: "Re: Creating Remote processes"
- In reply to: Paul Hulatt: "WBEM ConnectServer taking too long."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
