Hmmm... The tlot pickens.. bash-2.04$ telnet de.durr-usa.com 25 Trying 65.43.129.25... Connected to de.durr-usa.com. Escape character is '^]'. 220 ***************************************************2**0*0 *****
Tell their admins to change their PIX configuration to include: No fixup protocol smtp 25 Their PIX is running MaulGuard (oops, Mailguard), which has known issues with some ESMTP mailers (funny enough, Exchange is one of them). Its all over the CISCO support pages. Alternately, set your IMC to only use SMTP rather than ESMTP for that domain. I'd suggest, since they're being less than nice about it, you tell them their firewall is screwed up. Its more fun that way... I can't find the Cisco article about it, but those *** are indicative, IIRC. ------------------------------------------------------ Roger D. Seielstad - MCSE Sr. Systems Administrator Peregrine Systems Atlanta, GA > -----Original Message----- > From: Joe Pochedley [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, March 13, 2002 12:11 PM > To: Exchange Discussions > Subject: RE: Network Error During Host Resolution > > > I know there's no MX record (I stated that in my original > post). According to the RFC for SMTP (forget the number > right now), if there's no MX record but there is an A record > (which there is) then the SMTP server should use the A record > as an MX record and attempt delivery to the address > referenced in the A record. > > I tried telling the folks at the remote company that they > should haven an MX record for their subdomain, but got the > "Nobody else is having a problem so we're not going to do > anything about it." type response. > > Re: To the person who asked about telnet testing... I tried > Telnet testing and get a 220 connect message from > de.durr-usa.com, but when a send a HELO command, I never get > a 250 response back. Again, according to the folks at the > remote end, "Nobody else is having a problem..." > > Thanks....... Still looking...... > > Joe Pochedley > "I like deadlines," > cartoonist Scott Adams once said. > "I especially like the whooshing > sound they make as they fly by." > > > -----Original Message----- > From: Nick Field [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, March 13, 2002 11:56 AM > To: Exchange Discussions > Subject: RE: Network Error During Host Resolution > > > There does not appear to be a MX record for de.durr-usa.com > Perhaps this is your problem. > > Nick > > > > -----Original Message----- > From: Joe Pochedley [mailto:[EMAIL PROTECTED]] > Sent: 13 March 2002 16:40 > To: Exchange Discussions > Subject: Network Error During Host Resolution > > Kind ladies and gentlemen of the list. I am sending this > message again in hopes that someone will be able to help me. > I'm not intending to spam the list, just looking for some > assistance. I've heard from a few people off list that > they've also experienced similar problems, but none of them > have / had a solution and were hoping that I had found > something with yesterday's inquiry....... > > If anyone out there can help, or at least give me another > direction to explore I would greatly appreciate it. (I know > about MS PSS and it is my final option, but I'd rather not go > there). > > My Exchange Server is v5.5 SP4 > > Problem is as follows: > > -Begin Quoted Error Message- > > Your message did not reach some or all of the intended recipients. > > Subject: RE: Durr Industries > Sent: 3/10/02 1:11 PM > > The following recipient(s) could not be reached: > > '[EMAIL PROTECTED]' on 3/12/02 1:01 PM > The recipient name is not recognized > The MTS-ID of the original message is: c=US;a= > ;p=namfg;l=SEQUOYAH-020310181103Z-71 > MSEXCH:IMS:namfg:cleveland:SEQUOYAH 3499 > (000B09AA) network error during host resolution > > [EMAIL PROTECTED] on 3/12/02 1:01 PM > The recipient name is not recognized > The MTS-ID of the original message is: c=US;a= > ;p=namfg;l=SEQUOYAH-020310181103Z-71 > MSEXCH:IMS:namfg:cleveland:SEQUOYAH 3499 > (000B09AA) network error during host resolution > > -End Quoted Error Message- > > I'm getting this error when trying to send to > de.durr-usa.com, and have in the past had this error on a few > other addresses, but the message has always eventually gone > through in the past. This time though, I can't get anything > to go through to de.durr-usa.com. Supposedly, we have been > able to send to these recipients in the past, but it's only > been in the past two months that there have been any problems > that the end user has complained about... No changes have > been made to our Exchange Server or DNS servers for at least > the past 4-6 months. > > I am able to look up de.durr-usa.com using the same DNS > server that the exchange server is using, so it's not that > the DNS server can't resolve the host name... I looked up > durr-usa.com's DNS records and there is no MX record for the > sub domain 'de' but there is an A record, so theoretically > the Exchange SMTP service should use the A record in place of > the MX record, correct? > > I am at a loss. > > Thanks in advance. > > Joe Pochedley > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
