this is a network issue to some degree...
make sure the tcpserveraddress points to the proper (ATM) interface on the
server
AND make sure the routing on the client sends traffic bound for that address
(subnet) out the ATM interface on the client.
usually if these are on the same subnet it is kind'a automatic but I've
still had clients on a dedicated fddi loop for backups and send their adsm
traffic out across about 6 hops of other networks to get to my adsm
servers...(sigh)

Dwight

ps the tcpclientaddress is the interface you want the tsm server scheduler
service to come in to contact the running client scheduler

> ----------
> From:         Rupp Thomas (Illwerke)[SMTP:thomas.rupp AT ILLWERKE DOT AT]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Tuesday, July 11, 2000 2:16 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      New IP Address for TSM Clients
>
> Hi TSM-Gurus,
>
> we just installed a 155Mb ATM backbone just for backup.
> Now most of our servers have two networking cards (one for the
> 16Mb Token Ring and the other for the ATM back bone).
>
> How can I change the IP address so the TSM server uses the
> fast ATM connection and not the (up till now used) slow TR
> connection?
>
> If memory serves me well TSM notes the IP address on first contact.
> Does TCPCLIENTADDRESS in DSM.OPT help to change the
> address?
>
> Thanks in advance!
>
> Kind regards
> Thomas Rupp
> Vorarlberger Illwerke AG
> MAIL:   thomas.rupp AT illwerke DOT at
> TEL:    ++43/5574/4991-251
> FAX:    ++43/5574/4991-820-8251
>