[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | Microsoft Exchange Server |
| Notice: | |
| Moderator: | FLASK2::SYSTEM |
|
| Created: | Fri Feb 17 1995 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Thu Jun 05 1997 |
| Number of topics: | 1099 |
| Total number of notes: | 5174 |
988.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:13
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.