FE to BE emails are Queued

Dan · Joined: 05 Aug 2007 Posts: 54

Hello all,

I experienced a problem on the 1st of the year in which I spent 20 hours
trying to resolve. Long story short I restarted my 2 DCs and email started
flowing again.

The problem returns today. I have 1 FE 2003 exchange server and 1 BE 2003
exchange server. I have an SMTP connector set up for all mail to flow through
it. The FE server is listed as the bridgehead server.

my internal domain is intdomain.local and my external domain is
extdomain.com. on the FE and BE smtp virt servers i have set the FQDN to
fe01.extdomain.com and be01.extdomain.com respectively. On the BE server I
can telnet, over port 25, to the FE server using fe01.INTdomain.local but I
can not telnet to the FE server using fe01.EXTdomain.com. I do have all DNS
records created.

I ran WinRoute and everything checks out ok.

The queue information for the connector states: the remote server did not
respond to a connection attempt. That leads me to believe that my BE server
is trying to communicate to my FE server using our EXTdomain instead of our
INTdomain. Does anyone know why that is?

Thanks for any information you can provide to help me figure out why email
works and then, after no changes at all, suddenly stops.

Thanks in Advance,
Dan

Archived from group: microsoft>public>exchange>connectivity

Dan · Joined: 05 Aug 2007 Posts: 54

Sorry all.. the subject should actually be BE to FE emails are queued.

"Dan" wrote:

> Hello all,
>
> I experienced a problem on the 1st of the year in which I spent 20 hours
> trying to resolve. Long story short I restarted my 2 DCs and email started
> flowing again.
>
> The problem returns today. I have 1 FE 2003 exchange server and 1 BE 2003
> exchange server. I have an SMTP connector set up for all mail to flow through
> it. The FE server is listed as the bridgehead server.
>
> my internal domain is intdomain.local and my external domain is
> extdomain.com. on the FE and BE smtp virt servers i have set the FQDN to
> fe01.extdomain.com and be01.extdomain.com respectively. On the BE server I
> can telnet, over port 25, to the FE server using fe01.INTdomain.local but I
> can not telnet to the FE server using fe01.EXTdomain.com. I do have all DNS
> records created.
>
> I ran WinRoute and everything checks out ok.
>
> The queue information for the connector states: the remote server did not
> respond to a connection attempt. That leads me to believe that my BE server
> is trying to communicate to my FE server using our EXTdomain instead of our
> INTdomain. Does anyone know why that is?
>
> Thanks for any information you can provide to help me figure out why email
> works and then, after no changes at all, suddenly stops.
>
> Thanks in Advance,
> Dan

Dan · Joined: 05 Aug 2007 Posts: 54

i have confirmed that my BE server is sending mail to my FE server via the
external DNS record bc when I add a record to the local host file on the BE
server (frontend public FQDN ) the mail flows without a problem.

can anyone shed some light as to what might be causing my BE server to send
mail to my FE server via the public DNS and not the internal DNS?

Thanks in advance.

"Dan" wrote:

> Hello all,
>
> I experienced a problem on the 1st of the year in which I spent 20 hours
> trying to resolve. Long story short I restarted my 2 DCs and email started
> flowing again.
>
> The problem returns today. I have 1 FE 2003 exchange server and 1 BE 2003
> exchange server. I have an SMTP connector set up for all mail to flow through
> it. The FE server is listed as the bridgehead server.
>
> my internal domain is intdomain.local and my external domain is
> extdomain.com. on the FE and BE smtp virt servers i have set the FQDN to
> fe01.extdomain.com and be01.extdomain.com respectively. On the BE server I
> can telnet, over port 25, to the FE server using fe01.INTdomain.local but I
> can not telnet to the FE server using fe01.EXTdomain.com. I do have all DNS
> records created.
>
> I ran WinRoute and everything checks out ok.
>
> The queue information for the connector states: the remote server did not
> respond to a connection attempt. That leads me to believe that my BE server
> is trying to communicate to my FE server using our EXTdomain instead of our
> INTdomain. Does anyone know why that is?
>
> Thanks for any information you can provide to help me figure out why email
> works and then, after no changes at all, suddenly stops.
>
> Thanks in Advance,
> Dan

baruch Ortiz · Joined: 19 Feb 2008 Posts: 2

Put that host (A) into your Internal DNS replacing your Hosts file with
internal IP, that have to fix it without touching your hosts file that some
antivirus could detect as virus/worm attack and could be really painful
fighting with your AV and Exchange.

if your External FQDN of your FE is different from your internal FQDN,
create a new primary zone to match the external name, it won't affect you if
you do it good...

Have fun

Baruch Ortiz

"Dan" escribió en el mensaje de noticias @microsoft.com...
>i have confirmed that my BE server is sending mail to my FE server via the
> external DNS record bc when I add a record to the local host file on the
> BE
> server (frontend public FQDN ) the mail flows without a
> problem.
>
> can anyone shed some light as to what might be causing my BE server to
> send
> mail to my FE server via the public DNS and not the internal DNS?
>
> Thanks in advance.
>
> "Dan" wrote:
>
>> Hello all,
>>
>> I experienced a problem on the 1st of the year in which I spent 20 hours
>> trying to resolve. Long story short I restarted my 2 DCs and email
>> started
>> flowing again.
>>
>> The problem returns today. I have 1 FE 2003 exchange server and 1 BE 2003
>> exchange server. I have an SMTP connector set up for all mail to flow
>> through
>> it. The FE server is listed as the bridgehead server.
>>
>> my internal domain is intdomain.local and my external domain is
>> extdomain.com. on the FE and BE smtp virt servers i have set the FQDN to
>> fe01.extdomain.com and be01.extdomain.com respectively. On the BE server
>> I
>> can telnet, over port 25, to the FE server using fe01.INTdomain.local but
>> I
>> can not telnet to the FE server using fe01.EXTdomain.com. I do have all
>> DNS
>> records created.
>>
>> I ran WinRoute and everything checks out ok.
>>
>> The queue information for the connector states: the remote server did not
>> respond to a connection attempt. That leads me to believe that my BE
>> server
>> is trying to communicate to my FE server using our EXTdomain instead of
>> our
>> INTdomain. Does anyone know why that is?
>>
>> Thanks for any information you can provide to help me figure out why
>> email
>> works and then, after no changes at all, suddenly stops.
>>
>> Thanks in Advance,
>> Dan

emails from hotmail Hi, I have exhcange server 2007 ent. They are installed as an edge server and a mailbox server role. it is a defualt installation. everything was working fine and then I stopped recivening emails from hotmail.com but still I can from yahoo.com and google.

Exchange can't send any emails with attachments Hi We are currently having an issue were exchange will not send any emails with any attachments. It does send emails that have now but emails with attachments come back with an issue saying "Connection was dropped by remote server". Has anyone ever experi

MS Exchange 2003 not receiving emails Hi, I am running MS Win SBS 2003 with Exchange 2003. ( new installation ) behind a netopia 3000 router. Users are able to send emails but not to receive. I have the mx record and reverse dns setup and in place. Trying to telnet the server to port 25 fails

Some incoming emails are bouncing back to the sender Hi - We're using Exchange 2003 on Server 2003 SBS. Recently we've been finding that an increasing number of incoming emails are not reaching us and bouncing back to the senders. This is with emails that have previously got through. My personal gmail email

Emails not leaving SMTP Queue I just moved my exchange SBS server from one ISP to another. It is now sitting behind a Cisco ASA firewall which is connected to a T1 line. Most of my emails make it to their recipient. Emails to aol.com and Comcast.net sit in the mail queue and never mak