Activator conflict on system with multiple IPs on single port

[Don Lee]

I saw this as well on every instances where I updated the 6.1.<mumble> (old)
client to the new 6.2.<mumble> client.  I saw it when updating from beta
(unicorn) and then again with the released client.  Not sure what it
is, but it seems unaffected by how I do the upgrade.  It seems you have
to forget the client and re-add it or it won't work.

I didn't try more than about 3 times with this because I ran out of machines.
to upgrade.  ;->

-dgl-

>Mac setup, Retro Client 6.2.234, Retro Server 6.1.230.
>
>An existing user hadn't been backed up for a while, turned out that Retrospect was remembering him with an old IP.  Forgot the user, used the Network search, found him listed, tried to add him back in.   
>Instead of being prompted for a backup password, received an error that he couldn't be found on the network.  Used the Test to check his IP, this was successful.  Tried to add him by his IP, received an activator code conflict.  Logs reported his normal IP, as well as a 10.x.x.x address.
>
>Checked his system, he's running Parallels, network setup for this has a two additional IP address configured on his ethernet port, and this is apparently the issue, the first one I checked was the problem 10.x address.  I'm sure that if I disable the extra IPs, I'll be able to add him back in, but I would worry that as soon as the other IP was turned back on (he unfortunately has to use Parallels extensively during the day) that the Retrospect server would promptly find an activator conflict again and stop backing him up.
>
>I didn't see anything in the knowledge base regarding this issue.
>_______________________________________________
>Retro-Talk mailing list
>List Address: Retro-Talk at list.dantz.com
>Retro-Talk settings and archive: http://list.dantz.com/mailman/listinfo/retro-talk
>Retrospect Support: http://www.emcinsignia.com/support
>Retrospect KB: http://kb.dantz.com