Conference forty2::mailbus_400

3165.0. "NSAP address of Peer-MTA to ExchangeServer on multihome WNT" by ATZIS2::EHRLICH_K (Never met a Lady like her before!) Wed Apr 09 1997 13:12

Hi,

	at Cov we run into the following problem with a connection
MS-ExchangeServer <> MAILbus 400 MTA.

The MS-ExchangeServer is running on a mulithome WNT-Server with
6 Ethernetadapters in it.

The IP-name is sesl06.pc.advge. and has 6 different IP-addresses
(e.g. 10.128.16.32,10.128.17.32,...)

With nslookup or ping we can easily see this server having 1 name and
6 IP-addresses.

Now, within the MAILbus 400 MTA, building a peer-MTA to the MS-ExchangeServer
specifying the IP-name (RFC1006+sesl06.pc.advge.magwien.gv.at) and 
starting the peer-MTA we found that the NSAP-address changed.
It changed to RFC1006+sesq00.advge.magwien.gv.at. The funny thing is,
that THIS (sesq00.advge) name doesn't exist in the whole magwien.gv.at domain.
It seems that this name is random??? Really? Today I spoke with the
network-folks at both departments and they never had such a node in their
network.

By specifying only the IP-address 10.128.16.32 it works pretty fine.
But this means we have to enter all 6 IP-addresses in the presentation-
address of the peer-MTA, because we don't know which adapter the server
will use.

Question now is, why can't we specify only the IP-name, Why is the IP-name
changed to something complete different ??? Is this supported ???

MTIA for your ideas!

Cheers
Charly

PS: This is posted in both, MS-Exchange and MAILbus_400 conference.
    

Which version of the MTA are you running ?

Karen
-----

    Hi Karen,
    
    	many thanks! We'Re using MAILbus 400 MTA V2.0, of course!
    
    Cheers
    Charly
    

There was a problem with RFC1006 addresses but that was fixed in V2.0 so
obviously nothing to do with the problem you've got.

Sorry.

Karen
-----