I have a case open with my Veritas support for 3 weeks, same problem.

Are you using DNS for name service resolution?  My back network is private,
and I am only using hosts files.  I was able to get around the problem by
using the Client's IP, instead of clinet name for the Client Name in my
policy.  No reason why this should work, but it works for me.

Steve

On 1/19/07, Lee, Kenneth (SBS US) <kenneth.lee at siemens.com> wrote:
>
>
> Hi,
>
> I am running NetBackup 5.1 MP6 on Solaris 9.  Our Windows administrator
> just installed Windows 2003 server with R2.  When I tried to start a
> backup from the Windows client, I am getting a status code of 23.  I
> have looked at network and everything looks good.  There is a case
> opened with Veritas and they have looked at it for the last 3 days but
> no solution at this time.  I know that in order for NetBackup to support
> R2, I need to be on NetBackup 5.1 MP4 or higher.  I have uninstalled and
> reinstalled NetBackup client, rebooted the server and the problem is
> still there.  Has anyone seen this problem?  Is anyone backing up
> Windows 2003 R2 with NetBackup 5.1 using a Solaris 9 Master Server?
>
> Thanks!
>
> Ken
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20070119/9cbf5413/attachment.html