[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference forty2::mailbus_400

Title:MAILBUS 400 User Forum
Notice:kits 100-109 - Infocenter //www.digital.com/info/messaging
Moderator:IOSG::MARSHALL
Created:Thu Jun 11 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3210
Total number of notes:9174

3146.0. "Changing the node name" by VAXRIO::ABREU () Wed Mar 05 1997 19:09

    Hi,
    
        I have a customer running Mailbus 400 MTA 2.0 and X.500 1.2 and
    they want to change the node name of their machine. 
    
        What need to be done to have these products working fine after this
    change ? 
    
        Thanks .. Marcia
    
    PS: I don not know both of these products.
T.RTitleUserPersonal
Name		DateLines
3146.1No simple answerZUR01::ASHGGrahame Ash @RLEThu Mar 06 1997 08:2027
Hi Marcia,

>        I have a customer running Mailbus 400 MTA 2.0 and X.500 1.2 and
>    they want to change the node name of their machine. 
    
Er, they're probably not running X.500 V1.2 - it should be V2.0 at least.

What Operating System are they using?

It's possible that you won't have to change anything, as these applications 
rely on address information rather than nodenames. BUT, as always, it depends.

What MTA agents do you have? (ncl show mta agent *)

I notice on our system that we have the nodename defined in several foreign 
address translations. 

The output of the following commands might also be useful to get you a better 
answer:

ncl> show mta all char

ncl> show dsa all char

And tell us what is the node name at the moment.

grahame
3146.2And DUMPFORTY2::KNOWLESPer ardua ad nauseamThu Mar 06 1997 08:274
    I'd add to those commands the DUMP MTS command - to help you check that
    there are no old node names hidden in the directory.
    
    b
3146.3It is working VAXRIO::63230::abreuThu Mar 06 1997 20:2713
Hi,

    I logged on the customer machine this morning and I realized that they had 
already changed the nodename and that Mailbus wasn't working because they 
didn't start it. They removed the command from systartup_vms.com. 

     After starting the product, everything was working fine. I didn't have to 
change anything on Mailbus and X.500 , I just had problems with ALL-IN-1 but 
right now is everything working.

     X.500 wasn't 1.2 , it was 3.0.  

     Thanks ... M�rcia