Endpoint Protection

 View Only
  • 1.  Unable to change scan settings or update definitions on Netware server

    Posted Jul 29, 2010 10:54 AM
      |   view attached
    We are unable to change the scan settings or update definitions on netware server.When we try to access the server from SSC and error appears related to topolocy settings.Due to this the default scheduled scan is started when we run  the backups and the server gets frequent abend.Can some one suggest me on how to disable the scheduled scan from the netware command prompt Below given are the server details.

    Netware Server Details
    OS : Netware 6.5 SP8
    Symantec Version : 10.1.9.9000


    Attached is the Error message from the SSC.

    Thanks,
    Partha Sarathy K

    Attachment(s)

    doc
    Symantec Error.doc   60 KB 1 version


  • 2.  RE: Unable to change scan settings or update definitions on Netware server

    Posted Jul 29, 2010 11:06 AM
    follow this document



    Error: "The requested operation will not be performed. . .because their topology information could not be retrieved..." when right-clicking on a client in Symantec System Center


    http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2002111315533548


  • 3.  RE: Unable to change scan settings or update definitions on Netware server

    Posted Jul 29, 2010 11:39 AM

    Thanks for the document link,but the issue is with Netware servers smiley


  • 4.  RE: Unable to change scan settings or update definitions on Netware server

    Posted Jul 29, 2010 11:45 AM
    you need to check the communication between the ssc and the network, even if you modify the regisry for scan settings, if its communicating then it wil take policy from manger and gets modified.



  • 5.  RE: Unable to change scan settings or update definitions on Netware server

    Posted Jul 30, 2010 05:02 AM
    I am able to access other netware servers in SSC.the problem is only with one netware server.


  • 6.  RE: Unable to change scan settings or update definitions on Netware server

    Posted Jul 30, 2010 05:27 AM
    try repalcing the grc.dat file