On Aug 21, 2007, at 9:50 AM, Wanda Prather wrote:

The client's IP address is saved as part of the node definition (do
a q
node f=d and you'll see it.), so that isn't a problem.

However, test the move on ONE client before you flop the IP addresses.
All the client data will move fine with an EXPORT, but it used to
be that
if your server platform changed, the client password wouldn't work
anymore.

Never got a real explanation of why, something about the way the
password
gets encrypted.  Don't know if it's still an issue, but I ran into
it a
couple of versions ago going from an AIX to a Windows TSM server.

This may relate to the server name, as per the 'Set SERVername' command.
It's vital that this stay the same in your server transition, to avoid
having to update the "PASSWORDAccess Generate" saved password in every
client.  Do 'Query STatus' to check the name.

Beyond that, there may be something we aren't aware of in the encrypted
value, as Wanda suggests.

  Richard Sims