We've seen the same thing for some time now.  It appears to have gotten
worse since we upgraded our Server from Ver 1 to Ver 2 (we're on VM)
Our users are a mix of old and new clients , Unix, netware, Win95 & WinNT.
It appears to occur more often with Win95/NT users.
Since I'm on VM ( :-) ) I trap the error message with PROPLOG and do
a PING of the IP address and if it comes back negative I do the router
(assuming router is a .1).   and I get a variety of responses:
sometimes the workstation doesn't ping back, sometimes it does.
If it doesn't I still get a ping back from the router.  etc.
Users that we see with this problem frequently swear their workstation is
up and running the scheduler when it suppose to be doing so.

One user swears she can control when it fails or succeeds by leaving her
monitor on or off each night.   Sigh.

Any suggestions would be much appreciated.

                     cheers ... joe.f.

On Wed, 10 Jun 1998 09:14:12 -0800 Robbin Smith said:
>I am getting  ANR2716E (Schedule prompter was not able to contact client ....
>using type 1 ). This just started occuring about 3 wks ago. My server is AIX
>V4.2 using ADSM 2.1; the client causing the trouble is an HP Unix also using
>ADSM 2.1. The dsmc scheduler daemon is running; netstat shows port 1501 is
>listening.
>
>If I kill the process and restart it and immediately schedule a backup it will
>usually work. But if the backup is scheduled for later, it generally will not
>work.
>
>I have two other HPUX clients - same network - working just fine.
>
>Anybody have any suggestions or ideas?