Archived community.zenoss.org | full text search
Skip navigation
Up to Discussions in zenoss-windows
26247 Views 10 Replies Latest reply: Jan 23, 2014 3:49 AM by Shobhit Nirala RSS
jhei Newbie
jhei
2 posts since
Mar 8, 2010
Currently Being Moderated

Mar 8, 2010 5:04 AM

zenwin & zeneventlog error NT_STATUS_IO_TIMEOUT

Hi,

i just installed Zenoss and tryed to configure Zenoss to interact with Windows 2008 Server by WMI.

I get error from zenwin & zeneventlog:

"Could not read Windows services (NT_STATUS_IO_TIMEOUT). Check your username/password settings and verify network connectivity."

 

What could be the problem?

wmic  from zenoss shell works without any problems

  • alzoo Rank: White Belt
    alzoo
    74 posts since
    May 11, 2009
    Currently Being Moderated
    1. Mar 8, 2010 9:11 AM (in response to jhei)
    Re: zenwin & zeneventlog error NT_STATUS_IO_TIMEOUT

    I'm having this same issue with my 2003 servers in our DMZ.

  • jmp242 ZenossMaster
    jmp242
    4,060 posts since
    Mar 7, 2007
    Currently Being Moderated
    2. Mar 8, 2010 12:38 PM (in response to jhei)
    Re: zenwin & zeneventlog error NT_STATUS_IO_TIMEOUT

    Do you have your username and password entered correctly in the zProperties?

    --

    James Pulver

    Information Technology Area Supervisor

    LEPP Computer Group

    Cornell University

     

     

     

    jhei wrote, On 3/8/2010 5:04 AM:

    Hi,

    i just installed Zenoss and tryed to configure Zenoss to interact with Windows 2008 Server by WMI.

    I get error from zenwin & zeneventlog:

    "Could not read Windows services (NT_STATUS_IO_TIMEOUT). Check your username/password settings and verify network connectivity."

     

    What could be the problem?

    wmic  from zenoss shell works without any problems

    >

  • jhei Newbie
    jhei
    2 posts since
    Mar 8, 2010
    Currently Being Moderated
    3. Mar 9, 2010 1:46 AM (in response to jmp242)
    Re: zenwin & zeneventlog error NT_STATUS_IO_TIMEOUT

    username and password checked many times. tryed different formats with username like .\Administrator etc.

    Is there something that needs to be configured on the server side, this server is member of workgroup, not domain?

    and it doesnt have snmp configured.

  • jmp242 ZenossMaster
    jmp242
    4,060 posts since
    Mar 7, 2007
    Currently Being Moderated
    4. Mar 9, 2010 8:05 AM (in response to jhei)
    Re: zenwin & zeneventlog error NT_STATUS_IO_TIMEOUT

    Hmm, well if wmic works, you don't have connectivity problems. It sounds

    like a permission problem of some sort. Unfortunately, I don't think

    I've seen this error answered before.

     

    docs/DOC-2520

    has the common errors. If you do figure this out, let me know so I can

    add it to the list.

    --

    James Pulver

    Information Technology Area Supervisor

    LEPP Computer Group

    Cornell University

     

     

     

    jhei wrote, On 3/9/2010 1:46 AM:

    username and password checked many times. tryed different formats with username like .\Administrator etc.

    Is there something that needs to be configured on the server side, this server is member of workgroup, not domain?

    and it doesnt have snmp configured.

    >

  • mmladin Newbie
    mmladin
    1 posts since
    Apr 4, 2011
    Currently Being Moderated
    5. Apr 4, 2011 3:35 AM (in response to jhei)
    Re: zenwin & zeneventlog error NT_STATUS_IO_TIMEOUT

    I had the same problem. On monitored server event log showed failed login attempts, although password was correctly entered in zenoss. It turned out that server was configured to accept only NTLMv2, so I resolved this issue with enabling use of NTLMv2 in zeneventlog daemon configuration.

  • hk_stuey Rank: White Belt
    hk_stuey
    13 posts since
    Dec 16, 2009
    Currently Being Moderated
    6. Apr 6, 2011 5:57 AM (in response to jhei)
    Re: zenwin & zeneventlog error NT_STATUS_IO_TIMEOUT

    I have the same problem.  It works fine against two servers (both Windows Server 2003), but doesn't work against four others (3 x Server 2003 & 1 Server 2008).  Each of the servers is remote from my Zenoss box and is a standalone box in a workgroup.  I've double-checked all the usual possibilities (Username & password, firewall rules, AV software).  I've installed Wireshark on one of the servers and all it sees is the incoming SYN on TCP/135.  The server doesn't respond.  The Windows Event Log reveals nothing unusual.  I deleted one of the servers from Zenoss and re-added it.  It made no difference.

  • psonenberk Rank: White Belt
    psonenberk
    30 posts since
    Oct 13, 2008
    Currently Being Moderated
    7. Apr 11, 2011 8:59 AM (in response to hk_stuey)
    Re: zenwin & zeneventlog error NT_STATUS_IO_TIMEOUT

    Hello,

    I've got similar (the same problem) - if you want, you can find

    "Problem with wmi - Zenoss WMIC" on users forums.

    I would like to find right solution .............

    Have a nice day.

    P.Sonenberk

  • mbullen Newbie
    mbullen
    1 posts since
    Apr 14, 2011
    Currently Being Moderated
    8. Apr 14, 2011 8:20 PM (in response to jhei)
    Re: zenwin & zeneventlog error NT_STATUS_IO_TIMEOUT

    I had the same error on my W2K8 R2 install. I initially added the device using FQDN but removed/added using IP address, then renamed to FQDN. So far I haven't encountered the error.

  • hk_stuey Rank: White Belt
    hk_stuey
    13 posts since
    Dec 16, 2009
    Currently Being Moderated
    9. Apr 21, 2011 4:20 AM (in response to mbullen)
    Re: zenwin & zeneventlog error NT_STATUS_IO_TIMEOUT

    Thanks for the tip, it didn't resolve the issue for me, but thanks anyway.

  • Shobhit Nirala Newbie
    Shobhit Nirala
    1 posts since
    Dec 17, 2012
    Currently Being Moderated
    10. Jan 23, 2014 3:49 AM (in response to jhei)
    Re: zenwin & zeneventlog error NT_STATUS_IO_TIMEOUT

    Hi, I am getting same error,  not sure if any one managed to get resolution

     

    Please suggest for "Error collecting perofrmance data:NT_STATYS_IO_TIMEOUT"

     

    Although device is discovered with cpu data, filesystem data, windows services...

     

    but its performance data not accessible

     

    Please suggest

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points