Thanks to everyone who provided input / feedback on this.  In my case, I
was able to figure out what was wrong. When I downloaded the audit
compliance files, a .txt extension was being saved witht the file
(FDCC_Desktops_v90_v2.audit.txt).  When I removed the .txt extension and
left it with the .audit (FDCC_Desktops_v90_v2.audit) extension, it ran
fine. 

Thanks again.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, June 20, 2008 12:00 PM
To: [email protected]
Subject: Nessus Digest, Vol 56, Issue 17

Send Nessus mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://mail.nessus.org/mailman/listinfo/nessus
or, via email, send a message with subject or body 'help' to
        [EMAIL PROTECTED]

You can reach the person managing the list at
        [EMAIL PROTECTED]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Nessus digest..."


Today's Topics:

   1. NESSUSGui  (Kinnear, Mike)
   2. Re: using Nessus 3.2 on a Novell Netware 6.5 network (Ron Gula)
   3. Re: NESSUSGui  (George A. Theall)
   4. Error when running Windows Compliance Check (Richard Puerto)
   5. Re: Error when running Windows Compliance Check (YARICK)
   6. RE: Error when running Windows Compliance Check (Deepak J. Mathew)
   7. Re: Error when running Windows Compliance Check (Nicolas Pouvesle)


----------------------------------------------------------------------

Message: 1
Date: Thu, 19 Jun 2008 11:14:41 -0500
From: "Kinnear, Mike" <[EMAIL PROTECTED]>
Subject: NESSUSGui 
To: <[email protected]>
Message-ID:
        <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"

What happened to the NessusGUI.exe application?  

Securely yours,

Mike Kinnear, CEH
Security Analyst II - SHAZAM Secure
ITS, Inc.
515-288-2828 ext. 4558



Attention: This electronic document and associated attachments (if any)
may contain confidential information of the sender (SHAZAM Network) and
is intended solely for use by the addressee(s). Review by unintended
individuals is prohibited. If you are not the intended recipient: (i) do
not read, transmit, copy, disclose, store, or utilize this communication
in any manner; (ii) please reply to the sender immediately, state that
you received it in error and permanently delete this message and any
attachment(s) from your computer and destroy the material in its
entirety if in hard copy format. If you are the intended recipient,
please use discretion in any email reply to ensure that you do not send
confidential information as we cannot secure it through this medium. By
responding to us through internet e-mail, you agree to hold SHAZAM, Inc.
and all affiliated companies harmless for any unintentional
dissemination of information contained in your message.  Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mail.nessus.org/pipermail/nessus/attachments/20080619/d604102a/at
tachment-0001.html 

------------------------------

Message: 2
Date: Thu, 19 Jun 2008 15:29:10 -0400
From: Ron Gula <[EMAIL PROTECTED]>
Subject: Re: using Nessus 3.2 on a Novell Netware 6.5 network
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Kelly, Jim wrote:
> Are there any caveats using Nessus on a Novell network?

In the past, users with older, unpatched Novell networks suffered a
nasty
denial of service issue that could crash some of their servers. This
resulted
in Tenable adding a 'Do not scan fragile devices' configuration option
that
allowed for early detection of Novell devices in a scan and then stop
scanning
that device. If you specifically want to scan Novell devices, you need
to
enable the option 'Scan Novell Netware hosts'.

> Netware 6.5 uses TCP/IP, I believe in addition to the old IPX/SPX.

Nessus only audits Novell over TCP/IP, not IPX/SPX.

> Has anyone had any experience scanning a Netware 6.5 network? Can you
> share whatever caveats you might have?

Please check the archives of this email list.

> Can Nessus deal with this kind of network?

Yes, unless it is 100% IPX/SPX which we still run into occasionally,
even
in 2008.

Ron Gula
Tenable Network Security






------------------------------

Message: 3
Date: Thu, 19 Jun 2008 16:01:30 -0400
From: "George A. Theall" <[EMAIL PROTECTED]>
Subject: Re: NESSUSGui 
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=US-ASCII; format=flowed

On Jun 19, 2008, at 12:14 PM, Kinnear, Mike wrote:
> What happened to the NessusGUI.exe application?
>
It was replaced by NessusClient 3.2.0 last March:

 
http://list.nessus.org/pipermail/nessus-announce/2008-March/000005.html


George
-- 
[EMAIL PROTECTED]





------------------------------

Message: 4
Date: Thu, 19 Jun 2008 21:26:45 -0400
From: "Richard Puerto" <[EMAIL PROTECTED]>
Subject: Error when running Windows Compliance Check
To: [email protected]
Message-ID:
        <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"

I have been getting this error during many of my scans.

Windows Compliance Checks
Syntax error (line 59) : invalid value_data (value data element '1' is
not a
valid predefined value)

Nessus ID : 21156

The audit file I am using is FDCC_Desktops_v90_v2.audit.txt

Any one else experience this?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mail.nessus.org/pipermail/nessus/attachments/20080619/aadf39fd/at
tachment-0001.html 

------------------------------

Message: 5
Date: Thu, 19 Jun 2008 22:47:09 -0400
From: YARICK <[EMAIL PROTECTED]>
Subject: Re: Error when running Windows Compliance Check
To: "Richard Puerto" <[EMAIL PROTECTED]>
Cc: [email protected]
Message-ID:
        <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"

hi, i have never seen anything like that, please attach the audit file
and
describe the scanner version and OS along with the version and patch
level,
i will try to reproduce.

[EMAIL PROTECTED]

On Thu, Jun 19, 2008 at 9:26 PM, Richard Puerto
<[EMAIL PROTECTED]>
wrote:

> I have been getting this error during many of my scans.
>
> Windows Compliance Checks
> Syntax error (line 59) : invalid value_data (value data element '1' is
not
> a valid predefined value)
>
> Nessus ID : 21156
>
> The audit file I am using is FDCC_Desktops_v90_v2.audit.txt
>
> Any one else experience this?
>
> _______________________________________________
> Nessus mailing list
> [email protected]
> http://mail.nessus.org/mailman/listinfo/nessus
>



-- 
--Yarick Tsagoyko

Advisory Notice: Email is covered by the Electronic Communications
Privacy
Act and is legally privileged, but inherently insecure. Content may be
subject to alteration: email addresses may incorrectly identify the
sender.
This email transmission, and any documents, files, or previous email
messages attached to it may be privileged and confidential, and are
intended
only for the use of the recipient(s) named in the address field. If the
reader of this message is not an intended recipient, or the employee or
agent responsible to deliver it to the recipient, you are hereby
notified
that any dissemination, distribution, or copying of this message or its
contents is strictly prohibited. If you have received this message in
error,
please notify me by telephone or return email and delete it and any
attachments from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mail.nessus.org/pipermail/nessus/attachments/20080619/a458667e/at
tachment-0001.html 

------------------------------

Message: 6
Date: Thu, 19 Jun 2008 22:37:56 -0500
From: "Deepak J. Mathew" <[EMAIL PROTECTED]>
Subject: RE: Error when running Windows Compliance Check
To: "'Richard Puerto'" <[EMAIL PROTECTED]>,
        <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"

We had similar issues and we ended up using the Nessus Client.  are you
using the web console?

 

Deepak J. Mathew

Systems Manager - Administrative Systems

Rice University

 

(t) 713-348-4328

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Richard Puerto
Sent: Thursday, June 19, 2008 8:27 PM
To: [email protected]
Subject: Error when running Windows Compliance Check

 

I have been getting this error during many of my scans. 

 

Windows Compliance Checks 
Syntax error (line 59) : invalid value_data (value data element '1' is
not a
valid predefined value)

 

Nessus ID : 21156  

 

The audit file I am using is FDCC_Desktops_v90_v2.audit.txt

 

Any one else experience this?

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mail.nessus.org/pipermail/nessus/attachments/20080619/14c6e6af/at
tachment-0001.html 

------------------------------

Message: 7
Date: Fri, 20 Jun 2008 13:18:02 +0200
From: Nicolas Pouvesle <[EMAIL PROTECTED]>
Subject: Re: Error when running Windows Compliance Check
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes


On Jun 20, 2008, at 3:26 AM, Richard Puerto wrote:

> I have been getting this error during many of my scans.
>
> Windows Compliance Checks
> Syntax error (line 59) : invalid value_data (value data element '1'  
> is not a valid predefined value)
>
> Nessus ID : 21156
>
> The audit file I am using is FDCC_Desktops_v90_v2.audit.txt
>
> Any one else experience this?


Could you make sure you are using the latest version ?

# $Revision: 1.4 $
#
# $Date: 2008/02/05 18:31:32 $
#

If it is not the case just download it from the customer portail and  
you should no longer see this error.


Nicolas


------------------------------

_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus

End of Nessus Digest, Vol 56, Issue 17
**************************************


_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus

Reply via email to