1. Community Tip: Please Give Thanks to Those Sharing Their Knowledge.
    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.
  2. Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)
    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

ANR2716E Schedule prompter was not able to contact client

Discussion in 'TSM Client' started by skeeter66, Mar 23, 2007.

  1. skeeter66

    skeeter66 ADSM.ORG Member

    Joined:
    Sep 18, 2003
    Messages:
    32
    Likes Received:
    0
    I have installed the TSM client on a Windows Server 2003 Standard. I have set up the TSM server for this client the same as any other client I have installed in the last three years. I can preform manual backups from the client but when the scheduled time comes for the automated backup it does not work. The following message is written to the daily log file.
    "ANR2716E Schedule prompter was not able to contact client
    OMH-SERVER using type 1 (omh-server.oconeemed.org 4112)."
    This client is on a different domain than the TSM server and the rest of the clients. the TSM server and clients are on the oconeemed.org domain while this particular client is on another domain. I have added this clients IP address to the TSM servers Host file using omh-server.oconeemed.org as the host name for the clients IP Adress. The clients actual domain is different but I set it as oconeemed.org at the suggestion of the Network Admin. I can ping the client from the TSM server using the IP Address and now using omh-server since writing this information in the host file.
    Any suggestions would be appreciated.
     
  2.  
  3. heada

    heada ADSM.ORG Moderator

    Joined:
    Sep 23, 2002
    Messages:
    2,560
    Likes Received:
    168
    Occupation:
    Storage Administrator
    Location:
    Indiana
    Does the client have HL address and LL address set?

    -Aaron
     
  4. skeeter66

    skeeter66 ADSM.ORG Member

    Joined:
    Sep 18, 2003
    Messages:
    32
    Likes Received:
    0
    Where would I look to determine this?
    Thanks
     
  5. heada

    heada ADSM.ORG Moderator

    Joined:
    Sep 23, 2002
    Messages:
    2,560
    Likes Received:
    168
    Occupation:
    Storage Administrator
    Location:
    Indiana
    q node {node} f=d

    -Aaron
     
  6. skeeter66

    skeeter66 ADSM.ORG Member

    Joined:
    Sep 18, 2003
    Messages:
    32
    Likes Received:
    0
    Both the HL and LL are blank. TheTCP/IP Name and TCP/IP Address are set. The HL and LL are not set on any of the clients.
     
  7. heada

    heada ADSM.ORG Moderator

    Joined:
    Sep 23, 2002
    Messages:
    2,560
    Likes Received:
    168
    Occupation:
    Storage Administrator
    Location:
    Indiana
    It looks like TSM is attempting to start the session (server based vs client based) You might want to fill out the HL address (fully qualified hostname) and LL address (port it connects to) and see if that makes a difference.

    -Aaron
     
  8. blagrange

    blagrange ADSM.ORG Member

    Joined:
    Aug 25, 2004
    Messages:
    148
    Likes Received:
    0
    Occupation:
    Storage Engineer
    Location:
    Denver, Co.
    Is there a firewall between the domains?
     
  9. skeeter66

    skeeter66 ADSM.ORG Member

    Joined:
    Sep 18, 2003
    Messages:
    32
    Likes Received:
    0
    No firewall between them.
    I have set the HL and LL addresses. I'll check it after the next scheduled backup.
     
  10. Asha

    Asha ADSM.ORG Member

    Joined:
    Sep 26, 2006
    Messages:
    126
    Likes Received:
    1
    Occupation:
    Systems Engineer
    Hi...

    I am facing a similar issue...Just wanna know whether adding the HL and LL address resolved the problem???
     
  11. raistlin1981

    raistlin1981 ADSM.ORG Member

    Joined:
    May 8, 2008
    Messages:
    17
    Likes Received:
    1
    It did not work for me. I have about 5 servers with the same problem, 3 servers do not have DNS entries but I setup the HL and LL addresses, and the other 2 boxes reside behind a load balancer with all ports opened but register a separate ip with the TSM server because they're behind the load balancer. 1 box is server 2000 and the other 4 are server 2003.
     
  12. gyuzik

    gyuzik ADSM.ORG Member

    Joined:
    Dec 18, 2003
    Messages:
    193
    Likes Received:
    1
    Occupation:
    Senior Network Analyst
    Location:
    Alberta
    I just recently had this exact same issue and found a solution that worked for me so I thought I would share.

    The solution was in the DNS server. Under reverse resolution, I found entries for some old servers that had the same IP as the new one. I removed those entries and finally had a successful night of scheduled backups.

    Hope this helps.
     
  13. jjescude

    jjescude Newcomer

    Joined:
    Sep 7, 2015
    Messages:
    3
    Likes Received:
    0
    Hola,
    En ocasiones en el DNS se repiten ip porque hay url (aplicaciones) montadas en dicho servidor, en cuyo caso no se pueden borrar las duplicadas en la zona inversa, creo que debes revisar en el archivo .opt o dsm.sys para ver si no tienes otras tareas de backup configuradas que estan en modo listening y usan el mismo puerto... me sucedio que tengo tres politicas de backup, diaria, semanal y mensual, y si usan el mismo puerto la tarea falla en caso de tener la planificación en modo prompted... es necesario en este caso que cada uno suba con un puerto diferente...
     

Share This Page