Re: WMI works on one server but not another
From: Tim Munro (Excelsior_at_Liamtoh.moc)
Date: 02/24/05
- Next message: Larry Combs: "KB article 835517"
- Previous message: baopakxan: "what is WMI erro?"
- In reply to: Tim Munro: "Re: WMI works on one server but not another"
- Next in thread: alexbalaev_at_yahoo.com: "Re: WMI works on one server but not another"
- Reply: alexbalaev_at_yahoo.com: "Re: WMI works on one server but not another"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 24 Feb 2005 12:05:35 -0500
Seems I got ahead of myself. Opening TCP port 135 didn't make any
difference. Does any one know which ports WinMgmt uses? One of the problems
is that I am trying to lock down my DCs (NT4) using port filtering. I need
open ports for Winmgmt and Legato Networkr.
Any help would be greatly appreciated.
-- Tim "Tim Munro" <Excelsior@Liamtoh.moc> wrote in message news:%23oH%23wWnGFHA.3156@TK2MSFTNGP10.phx.gbl... > Well, yes installing DID help, but after the fact. The actual error I was > getting was really refering to the fact that TCP port 135 was closed > (don't ask). Once I opened up the port I got a second error which was in > fact due to WMI not being installed. With WMI there and port 135 open all > is well. > > Thanks very much for your help. > -- > Tim. > > "Tim Munro" <Excelsior@Liamtoh.moc> wrote in message > news:%23i3jqQcGFHA.3912@TK2MSFTNGP10.phx.gbl... >> Thanks very much. I expect this'll help greatly. >> >> -- >> Tim >> >> <alexbalaev@yahoo.com> wrote in message >> news:1109172325.235035.235530@o13g2000cwo.googlegroups.com... >>> Tim, >>> 1. WMI is not a part of the NT 4.0 by default. You need to install it >>> from here >>> http://www.microsoft.com/downloads/details.aspx?FamilyID=c174cfb1-ef67-471d-9277-4c2b1014a31e&DisplayLang=en >>> Maybe one box has it and another one doesn't... Try to search for >>> framedyn.dll on the box. If you can find it - it's a sign that WMI is >>> there >>> 2. Try to connect to WMI from, say, Win2K (and up) box using >>> wbemtest.exe on the W2K box. Provide user account that is in admin >>> group on the NT 4.0 box while connecting... And see what error you'll >>> get back. >>> 3. CIM Studio is usefull for testing. Get it here >>> http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=6430F853-1120-48DB-8CC5-F2ABDC3ED314 >>> Hope that helps, >>> Alex. >>> >>> Tim Munro wrote: >>>> Hi, >>>> >>>> I have two NT 4.0 servers configured (close to) the same >>> (PDC,BDC). No >>>> other services run on these machines. On one, I can use WMI to >>> remotely >>>> access certain information (services list). On the other one it >>> fails. From >>>> what I can tell and what I remember they are both set up the same >>> way. ADSI, >>>> and WSH are installed both machines. The error I am getting is: >>>> >>>> R:\Servers\Services.vbs(81, 3) Microsoft VBScript runtime error: The >>> remote >>>> server machine does not exist or is unavailable: 'GetObject' >>>> >>>> I can dir to it's C$, I can remote edit the registry, but WMI >>> thinks >>>> it's not available. Am I missing some really simple? Any ideas? >>>> >>>> -- >>>> Tim. >>> >> >> > >
- Next message: Larry Combs: "KB article 835517"
- Previous message: baopakxan: "what is WMI erro?"
- In reply to: Tim Munro: "Re: WMI works on one server but not another"
- Next in thread: alexbalaev_at_yahoo.com: "Re: WMI works on one server but not another"
- Reply: alexbalaev_at_yahoo.com: "Re: WMI works on one server but not another"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
