All,

  Well, we finally resolved this after looking at some notes from the 465
patch to NBU 3.4. (Which by the way turns 3.4 into 3.4.1)

  To allow our NT 3.4 administration clients to administer both 3.4 servers
and 3.2 servers we changed the line in methods.allow to read:
noauth : 3.4ServerName

 with no entries for 3.2 servers. That seems to be working now. So every 3.4
server would need a "noauth" entry in the methods.allow file on your
administrative clients.

    Bryan


>   We have set up a new NBU 3.4 master running on an HP N4000 
> with HP/UX
> 11.00. Normally we run without authentication on our internal 
> networks. To
> get things working with 3.4 however, we have had to muck with the
> authentication files in /usr/openv/var/auth. We have added an entry to
> methods.txt -
> 0 noauth /usr/openv/lib/libnoauth.sl
>  And we also had to modify methods.allow by adding -
> noauth : ALL
> 
>   To make a 3.4 NT Administrative client work, we had to modify the
> corresponding NT files also. Once we did this, we were unable 
> to connect to
> our 3.2 master servers. 
> 
>   Is there a way to make the 3.4 admin clients work with our 
> 3.2 masters,
> preferably without using authentication? And without 
> re-configuring our
> dozen or so 3.2 masters and their clients?