Networker

Re: [Networker] errrr... licensing problem with 6.2?

2003-08-13 09:21:17
Subject: Re: [Networker] errrr... licensing problem with 6.2?
From: "Er, Murat" <murat.er AT HP DOT COM>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Wed, 13 Aug 2003 16:21:08 +0300
Hi,

This machine is domain controller+global catalog+AD integrated DNS.But I
have another networker zone with 6.1.3 version and that machine is also
AD+DNS+global catalog for another domain.No problem with that machine.
I don't use license manager.


Murat ER
System Specialist
Hewlett Packard

Tel:+90 216-579 78 83
Fax :+90 216-579 78 00
E-mail : murat.er AT hp DOT com 

  


-----Original Message-----
From: Sumash Singh [mailto:ssingh AT STORTECH.CO DOT ZA] 
Sent: Wednesday, August 13, 2003 4:03 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: errrr... licensing problem with 6.2?

Hi

Here is my thoughts on this matter. 

First let me ask if this machine is an Active Directory Domain
Controller?? Is it??

Anyway, it could be that active directory is messing up the SID
(Security Identifier) for this computer. In these cases you can use the
IP address as the hostid generator and ask Legato to use that hostid as
your basis for the auth code. 

It has been seen sometimes that since the SID on AD domain controllers
change they viod the auth code and hence the expiry. What you can do is
identify the primary interface using the Network Binding order in
Windows and then according to the IP address work out the hostid

So if your IP is 192.168.1.10 this converted to HEX would be c0a8010a

Then Legato Licensing will generate you new auth codes based on this
hostid. The algorithm that Networker uses will first test the auth code
against the SID hostid and fail then move on to IP address based hostid.
If this is the case, you will get the auth code working. Then if any
changes on the SID of the AD controller happens there would be no issues
with licensing unless of course you go an change the IP address or the
binding order of the network cards/.

Also, you will have to fill out host transfer affidavits to confirm that
you will not be running the software on another machine.

HTH 

Sumash

-----Original Message-----
From: Er, Murat [mailto:murat.er AT HP DOT COM] 
Sent: 13 August 2003 02:49
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] errrr... licensing problem with 6.2?

I entered authcodes on 30 Dec 2002 and I saw that it shows no expiration
on  license page.On 5 May 2002 I could see no expiration after entering
authcodes and now I still see no expiration on license page since 1 Aug
2003,but I think it will expire again nearly 2 or 3  months later.



Murat ER
System Specialist
Hewlett Packard

Tel:+90 216-579 78 83
Fax :+90 216-579 78 00
E-mail : murat.er AT hp DOT com 

  


-----Original Message-----
From: Davina Treiber [mailto:treiber AT HOTPOP DOT COM] 
Sent: Wednesday, August 13, 2003 3:34 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: errrr... licensing problem with 6.2?

On Wed, 13 Aug 2003 14:35:25 +0300, Er, Murat <murat.er AT HP DOT COM> wrote:

>Hi all,
>
>I have a strange problem about licensing.
>Networker 6.2.
>Although there is no configuration change on machine, networker base
>license expired.First license expired on 4th of May entered
>authorization codes then 30th of July second time expired.no
information
>in logs.Just your license will be expired in 13,12,11 days etc.

Doesn't sound strange to me.

4th May, eval licence expires.
You enter new enabler codes but omit to obtain and enter authorisation
codes.
30th July, enabler code expires.

An enabler code is time limited. Until you enter the auth code it is not
permanent.

--
Note: To sign off this list, send a "signoff networker" command via
email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via
email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.504 / Virus Database: 302 - Release Date: 2003/07/24
 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.504 / Virus Database: 302 - Release Date: 2003/07/24
 

--
Note: To sign off this list, send a "signoff networker" command via
email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

<Prev in Thread] Current Thread [Next in Thread>