Re: No one will answer
From: Evan Dodds [MSFT] (evand_at_online.microsoft.com)
Date: 07/12/04
- Next message: Scott Harris: "Print Out a Distribution List"
- Previous message: Lanwench [MVP - Exchange]: "Re: a problem in install"
- In reply to: Stu Hamilton: "Re: No one will answer"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 12 Jul 2004 10:55:42 -0400
Stu -
Having an MX record pointing to an IP address isn't a legal configuration, I
don't think. At the very least, I'd suggest that you set up an A record for
your MX host and reconfigure the MX record this way to see if it makes any
difference.
Also, it seems strange to me that you'd be getting an SMTP protocol error if
it's not connecting to SOME host (even if it's not the ISP). If you get a
netmon of these communication attempts, what is your DomainA server trying
to connect to? Is it the ISP?
-- Evan Dodds Microsoft Exchange Support ****** Disclaimer ****** This posting is provided "AS IS" with no warranties, and confers no rights. Note: Please do not reply to this e-mail address. It is used for newsgroup purposes only. "Stu Hamilton" <StuHamilton@discussions.microsoft.com> wrote in message news:4D1A0BDA-8FEB-464E-A6C1-5DD6E659D506@microsoft.com... > Evan, > > I have double checked my virtual SMTP server and there are no > configurations in there for any smart hosts. All the other email is > working correctly. When I do an nslookup -type=mx it resolves the the > correct IP address of the web mail server. When I check the properties on > the outgoing mail to domain B in my exchange box queue, it says there has > been an smtp protocol error? I am using my internal AD DNS servers for my > exchange box. The mx record I created in Domain B is entered as an IP > addrss and not a FQDN. But this should work OK? You said about an A > record .. do I need to create an A record as well as an mx record? > > Thanks again > > Stu > > "Evan Dodds [MSFT]" wrote: > >> Stu - >> >> If there are no connectors set up, then all of the routing configuration >> in >> Exchange will be handled by the SMTP protocol virtual server. You can >> confirm that on the protocol virtual server, nothing is set up >> incorrectly. >> I presume that mail to destinations other than DomainB work properly? Is >> the >> SMTP protocol virtual server for the Exchange server in DomainA >> configured >> to use a smarthost? How about External DNS configuration? >> >> Once you've determined that it's not using a smarthost and what DNS >> servers >> are being used (I believe it'll be the same as the OS unless you define >> external DNS resolvers on the protocol virtual server), you can test the >> results of these DNS servers. Exchange will look up the MX records for >> the >> destination domain through DNS and will then route to the listed A >> records >> for the mail exchanger hosts. If these are incorrect in your DNS, mail >> will >> route incorrectly. >> >> -- >> Evan Dodds >> Microsoft Exchange Support >> >> ****** Disclaimer ****** >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> Note: Please do not reply to this e-mail address. It is used for >> newsgroup >> purposes only. >> >> "Stu Hamilton" <StuHamilton@discussions.microsoft.com> wrote in message >> news:F3256A0E-B8D7-40BE-83FA-45185DEDB8E5@microsoft.com... >> > Hi Evan, >> > >> > Thanks for the reply, I appreciate it. I do not have any Exchange >> > connectors configured inside of Domain A. Before, when the two >> > Exchange >> > boxes were up and running they were completelty indipendent of each >> > other. >> > This is why I suspect DNS but cannot prove it. Is there any way to >> > prove >> > if it is Exchange or DNS? >> > >> > Again, many thanks >> > >> > Stu >> > >> > "Evan Dodds [MSFT]" wrote: >> > >> >> Stu - >> >> >> >> How were DomainA and DomainB configured to exchange email before you >> >> removed >> >> the DomainB Exchange server? It sounds to me like the DomainA Exchange >> >> server believes it needs to route to DomainB in an incorrect way. Is >> >> it >> >> possibly configured to route mail directly to the old DomainB Exchange >> >> server that no longer exists? >> >> >> >> -- >> >> Evan Dodds >> >> Microsoft Exchange Support >> >> >> >> ****** Disclaimer ****** >> >> This posting is provided "AS IS" with no warranties, and confers no >> >> rights. >> >> >> >> Note: Please do not reply to this e-mail address. It is used for >> >> newsgroup >> >> purposes only. >> >> >> >> "Stu Hamilton" <StuHamilton@discussions.microsoft.com> wrote in >> >> message >> >> news:1AF2888E-91A5-485C-A7B2-1061E309D3E1@microsoft.com... >> >> > Hi, >> >> > I have tried to ask this question everywhere and no one will answer. >> >> > Not >> >> > sure why (am i asking it wrong or rudely?) >> >> > Two of my domains (W2K AD Native SP4), Domain A & B. Both trust >> >> > each >> >> > other. Both used to have Exchange. I retired the exchange box in >> >> > domain >> >> > B and moved them over to a web based solution (verio web mail). >> >> > Since then, Domain B can email Domain A fine. But Domain A connot >> >> > email >> >> > Domain B. The emails get stuck in the Exchange Queue, then >> >> > eventually >> >> > NDR >> >> > (4.4.7). I have checked with the Web Mail provicer and they do not >> >> > see >> >> > any connection attempts to their mail server from mine in Domain A? >> >> > What am I missing? This driving me mad. >> >> > Please Help!!! >> >> > >> >> > Thanks >> >> > >> >> > Stu >> >> >> >> >> >> >> >> >>
- Next message: Scott Harris: "Print Out a Distribution List"
- Previous message: Lanwench [MVP - Exchange]: "Re: a problem in install"
- In reply to: Stu Hamilton: "Re: No one will answer"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
