Conference iosg::all-in-1

2506.0. "Remote DDS and Migration from VAX to Alpha" by VAXRIO::63230::abreu () Wed Feb 05 1997 18:52

Hi,

    I have a customer that migrated from a Vax running ALL-IN-1 v3.0 to 
an Alpha running V3.1. They are using Remote DDS. The problem is that the 
users are receiving a message saying that they were not authenticated at the 
mail directory.

    I created a new account and adopted the entry created in DDS and it worked 
fine. The authentication problem happens only with the old users. I tried to 
adopt their old entries in DDS but it didn't solve the problem. 

    The alpha uses the mailbox A1 in the VAX so that the users didn't have 
their address changed. All-IN-1 in the VAX was disabled , I mean it will not 
be used anymore.

    I realized that the user agent of the alpha has the name oa$alpha$allin1 
and the proxy user agent in the old user entries in dds is oa$vax$allin1(the 
old one). Could this be the problem that makes adoption not work ? 

    I guessed that maybe if I changed the alpha useragent to have the name of 
the old useragent , it could solve the problem but I don't know which problems 
this can cause.

    Any ideas ?

    Thks ,

     M�rcia

    

        You can't reuse the old user agent name in ALL-IN-1 v3.1, I'm not
        sure it's different in v3.2.  ALL-IN-1 expects the node name in
        the user agent, for an Alpha, to be something like,
        OA$PRIMARY_NODE.  It won't work if it's not.
        
        Dave Zaniewski

    I can't remember whether I did it through ALL-IN-1 or through an MBMAN
    script (I suspect the latter), but when making the same migration I
    changed the proxy user agentinformation on all the DDS entries, and it
    works fine for me.
    
    Jenny Joyce

Hi Jenny,

     I didn't realize I could change the proxy of the dds entries. I tried 
that and it worked fine.

     Thanks .. Marcia