Etrust not discovering machines on same subnet

  • Thread starter Thread starter melampki
  • Start date Start date
M

melampki

I looked EVERYWHERE for this info, so I thought I'd post it to help
others out.

We have one subnet, and no ports blocked. We are not routed. I could
not figure out why the admin console would not see the clients.

We clone our machines - you need a registry hack to fix it - and
TA-DA!

Hope this helps someone - it only took me 2 weeks to find it!
grrrrrrrr!!!


http://support.ca.com/techbases/ilnt_7/QI48726.html


PRODUCT: eTrust Antivirus EE RELEASE: 7.0

PDC #: QI48726 DATE: 16 DEC 2003

***** Product Documentation Change *****

PROBLEM DESCRIPTION: NT-MACHINE HAS NOT GIVEN A FULL RESPONSE TO POLL
----------------------------------------------------
The client machine may receive the following
error message in the Exchange mailbox:

"The machine [machine name] has not given a full
response to the poll. Some information may not
be up to date."

The error code for the above message is 75.

This error occurs because on this client
machine, the ID value in the registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates
\eTrustAntivirus\CurrentVersion\ID

is the same as the one on other eTrust client
machines. This type of situation may occur when
the eTrust client machines are ghosted from a
common image.

HYPER: NO

DISTRIBUTION CODE: I (A=Available, I=Internal)

DOWNLOAD INFORMATION:

NODE: ftp.ca.com

PATH: /CAproducts/unicenter/eTrust/AntiVirus/7.0/nt/qi48726

FILES: QI48726.C5D________ ___________________ ___________________
___________________ ___________________ ___________________

PROBLEM RESOLUTION: Follow the instructions below:
This problem can be solved using one of the following two methods:

A. Delete the ID value in the registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\eTrustAntivirus
\CurrentVersion\ID

-- OR --

B. Run the InoID utility. Please contact Computer Associates
technical support for this utility.

Thank you for your continued support of Computer Associates and its
products. If you have any questions about this Product Documentation
Change or any other questions about this product, please contact your
local Computer Associates Technical Support organization.

PRODUCT(S) AFFECTED: ETRUST ANTIVIRUS 10-99 USERS RELEASE 7.0
ETRUST ANTIVIRUS 100-249 USERS RELEASE 7.0
ETRUST ANTIVIRUS 250-749 USERS RELEASE 7.0
ETRUST ANTIVIRUS 750+ USERS RELEASE 7.0

For site comments, visit our Feedback page

This page was last modified on 02/02/2004 15:18:24
(c) Copyright 1995-2004 Computer Associates International, Inc. All
rights reserved.
All materials on this site subject to Legal Notice, including CA
Trademarks
 
melampki said:
I looked EVERYWHERE for this info, so I thought I'd post it to help
others out.

We have one subnet, and no ports blocked. We are not routed. I could
not figure out why the admin console would not see the clients.

We clone our machines - you need a registry hack to fix it - and
TA-DA!

Hope this helps someone - it only took me 2 weeks to find it!
grrrrrrrr!!!
Click to expand...

You clearly do not use cloning very well then.

If you use cloning as an installation method you still have to do in-depth
configuration testing. Why was this "failure" of the cloned machines not
found during testing of the cloning and replication procedures? If it was
found during that phase, it should not take longer to find than how long
it takes to run a standard build (or replication) of your "bare" OS base
image (you do have such a thing right?), installation of the software in
question and a quick analysis of a system configuration diff between the
two machines.

If you're not set up to do that, cloning is clearly not the right technology
for you...
 
Dear Nick,

Thank you for your oh-so-helpful commentary. It must be terribly
wonderful to live in Utopia. Could I stop by to visit sometime?

What you have failed to consider is that sometimes network
administrators are brought in to clean up after other incompetent
administrators.

Had *I* have done the cloning here, *I* would have tested it.
However, that was not the case. I inherited a network in a terrible
state of disrepair and I am slowly untangling 4-5 years of unplanned
growth and mismanagement.

Just for kicks and giggles, try walking into a network that has no
documentation, no license keys, no passwords recorded, no ANYTHING, go
straighten it out and make sure everything is in compliance - it is
not a necessarily easy task. You don't just sit down and tackle one
thing at a time in a straightforward and logical fashion when you have
over 400 users and you are the ONLY person doing EVERYTHING.

My posting was intended to help others who might be in a similar
situation as me or for those people who are not as bright as yourself.
 
Back
Top