TCP Flags invalid: 0x00000104

Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.

One of our customers running NIS 2003 (yes, I realize it's old) is reporting this to us.  My first thought is it's a false positive.  TCP flags is a one byte field (hexidecimal 0-FF) so I'm trying to understand what NIS means when it reports "TCP Flags invalid: 0x00000104"?  Is there some document or knowledge base article that explains this value?  Thank you in advance.

Can you add what version of Windows it is being used on including Service Packs (unless it is WIN95 <g>).

 

From a Google on that error message from which apart from your own two messages here the only reference is partly in Russian from a UN person ..... it might be an invasion?

 

I've flagged your message as outstanding ....

Message Edited by huwyngr on 09-04-2008 09:38 PM

I apologize for the delay. I’m a bit confused at what your customers is seeing. Is it a Blue Screen error? A Windows Error message? A Symantec Error message? If you could attach a screenshot to a future post, that would be helpful. without knowing the specifics of the system and of where the error is seen, it’s a bit difficult to find a resolution to this issue. Any additional information you can provide is appreciated. Thanks!

Symantec, a response would be appreciated.