Hmmm...you set the same passwords for server communication on both servers involved, crossdefined the servers during definition, updated the type=server "node" for the source server on the destination server using the password you set, updated and forcesynced the "server" passwords on both the source and destination. Those steps should have taken care of your issue.
Matthew, are you at least able to route commands between the two servers? BERTAUT TCHUISE Storage Support Administrator Legg Mason Technology Services *410-580-7032 [email protected] -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Matthew Large Sent: Friday, July 31, 2009 11:04 AM To: [email protected] Subject: Re: [ADSM-L] server to server authentication I just tried, and it did not help - they are still experiencing authentication problems. Thanks though On Fri, Jul 31, 2009 at 2:19 PM, Tchuise, Bertaut < [email protected]> wrote: > Hello Matthew, > > Have you tried using the forcesync=yes parameter with the upd server > command? > > Thanks. > > BERTAUT TCHUISE > Storage Support Administrator > Legg Mason Technology Services > *410-580-7032 > [email protected] > > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf > Of Matthew Large > Sent: Friday, July 31, 2009 7:30 AM > To: [email protected] > Subject: [ADSM-L] server to server authentication > > Hi, > > W2k3 TSM 5.5.0.0 server * 2 > > Copy storage pools of FILE deviceclasses with a devtype of SERVER, on > each server, using each other as a copy destination > > When I run space reclaim on one of these pools, hundreds of > > ANR4373E Session rejected by target server <target server> reason: > Authentication Failure > > I have already reset the server password with SET SERVERPASSWORD and > updated the servers with the UPD SERVER SERVERPASSWORD command, but > still these messages appear? > > What else is there which might need authenticating? > > Cheers, > Matthew > > IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason > therefore recommends that you do not send any confidential or > sensitive information to us via electronic mail, including social > security numbers, account numbers, or personal identification numbers. > Delivery, and or timely delivery of Internet mail is not guaranteed. > Legg Mason therefore recommends that you do not send time sensitive or > action-oriented messages to us via electronic mail. > > This message is intended for the addressee only and may contain > privileged or confidential information. Unless you are the intended > recipient, you may not use, copy or disclose to anyone any information > contained in this message. If you have received this message in error, > please notify the author by replying to this message and then kindly > delete the message. Thank you. > IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
