Notices
Computer & Technology Related Post here for help and discussion of computing and related technology. Internet, TVs, phones, consoles, computers, tablets and any other gadgets.

Odd exchange 2003 problem

Thread Tools
 
Search this Thread
 
Old 19 December 2006, 12:35 PM
  #1  
BlkKnight
Scooby Regular
Thread Starter
 
BlkKnight's Avatar
 
Join Date: Feb 2004
Location: High Wycombe
Posts: 3,763
Likes: 0
Received 0 Likes on 0 Posts
Default Odd exchange 2003 problem

I've got a win2000 AD domain, one server has EX2003 installed (and service packed up).

DNS is installed on the exchange server & member servers configured in a round robin.

NSlookups work to external sites & caching is ok.


All is fine except sending to one domain:

spriproducts.com

As far as I can tell the problem is at our end (as yahoo.co.uk sends ok). There is nothing in the event log.

All that happens is we get a bounce (immediately):

Your message did not reach some or all of the intended recipients.

Subject: test
Sent: 19/12/2006 11:55

The following recipient(s) could not be reached:

'herb@spriproducts.com' on 19/12/2006 11:55
You do not have permission to send to this recipient. For assistance, contact your system administrator.
<mail.physicalcompany.co.uk #5.7.1 smtp;550 5.7.1 Message rejected.>


I really don't know why it's failing as we can send to other external domains fine. . .

Any advice would be appreciated
Old 19 December 2006, 01:47 PM
  #2  
David_Wallis
Scooby Regular
 
David_Wallis's Avatar
 
Join Date: Nov 2001
Location: Leeds - It was 562.4bhp@28psi on Optimax, How much closer to 600 with race fuel and a bigger turbo?
Posts: 15,239
Likes: 0
Received 1 Like on 1 Post
Default

do you have this configured as a mail adress internally?


what do you mean you have configured dns in round robin (yes I know what round robin is!!!)
Old 19 December 2006, 01:52 PM
  #3  
Kieran_Burns
Scooby Regular
Support Scoobynet!
iTrader: (1)
 
Kieran_Burns's Avatar
 
Join Date: Jul 2004
Location: There on the stair
Posts: 10,208
Likes: 0
Received 0 Likes on 0 Posts
Default

Microsoft Exchange Server: Administration Tip: Resolving Nondelivery Reports Caused by 5.7.1 or 5.7.3 Errors

is always a good place to start
Old 19 December 2006, 02:02 PM
  #4  
BlkKnight
Scooby Regular
Thread Starter
 
BlkKnight's Avatar
 
Join Date: Feb 2004
Location: High Wycombe
Posts: 3,763
Likes: 0
Received 0 Likes on 0 Posts
Default

just if one dns server is busy they use the secondary.

I've tried the above already - I can send to all other external domains - just not this one ;(

I don't have the e-mail set up internally
Old 19 December 2006, 02:16 PM
  #5  
cottonfoo
Scooby Regular
 
cottonfoo's Avatar
 
Join Date: Jan 2001
Location: still behind twin turbos
Posts: 469
Likes: 0
Received 0 Likes on 0 Posts
Default

Originally Posted by BlkKnight
just if one dns server is busy they use the secondary.
DNS server load has nothing to do with it, there's no failover or load balancing going on, it just gives out the "next nameserver in the list on each request".

Do you get a bounce from the remote MTA or does it not even get out of your network?
Old 19 December 2006, 02:19 PM
  #6  
BlkKnight
Scooby Regular
Thread Starter
 
BlkKnight's Avatar
 
Join Date: Feb 2004
Location: High Wycombe
Posts: 3,763
Likes: 0
Received 0 Likes on 0 Posts
Default

There was an issue where the dns servers had different cached records for the MX record for spriproducts.com - so I cleared both and now they are fine.

It doesn't even get out past our server

Last edited by BlkKnight; 19 December 2006 at 02:21 PM.
Old 19 December 2006, 02:38 PM
  #7  
Nobbie
Scooby Regular
 
Nobbie's Avatar
 
Join Date: Apr 2006
Location: Herts
Posts: 299
Likes: 0
Received 0 Likes on 0 Posts
Default

What if you try and 'frig it' to use an isp'd dns server, does it resolve and get out then or not?

Are you using and spam lookups, etc?.

Are you using correct revers dns lookups?

Trending Topics

Old 19 December 2006, 02:42 PM
  #8  
BlkKnight
Scooby Regular
Thread Starter
 
BlkKnight's Avatar
 
Join Date: Feb 2004
Location: High Wycombe
Posts: 3,763
Likes: 0
Received 0 Likes on 0 Posts
Default

The domain resolves fine. The MX record for the domain is mail.spriproducts.com - which when I telnet to it and helo my domain is fine.

I am not doing any spam lookups.

I would assume the reverse dns is fine.
Old 19 December 2006, 02:54 PM
  #9  
David_Wallis
Scooby Regular
 
David_Wallis's Avatar
 
Join Date: Nov 2001
Location: Leeds - It was 562.4bhp@28psi on Optimax, How much closer to 600 with race fuel and a bigger turbo?
Posts: 15,239
Likes: 0
Received 1 Like on 1 Post
Default

Ahh, you have created a dns entry for all the dns servers and use that for message delivery?

David
Old 19 December 2006, 02:59 PM
  #10  
Nobbie
Scooby Regular
 
Nobbie's Avatar
 
Join Date: Apr 2006
Location: Herts
Posts: 299
Likes: 0
Received 0 Likes on 0 Posts
Default

In that case it maybe the case that the destination is blocking your details.

what does a tracert give?
Old 19 December 2006, 03:15 PM
  #11  
BlkKnight
Scooby Regular
Thread Starter
 
BlkKnight's Avatar
 
Join Date: Feb 2004
Location: High Wycombe
Posts: 3,763
Likes: 0
Received 0 Likes on 0 Posts
Default

Ahh, you have created a dns entry for all the dns servers and use that for message delivery?


- nope the entries are sitting in the "cached lookups" - oddley my two dns servers did not match - so I cleared the cache out - and they now point to the same place.

I don't see how a trecert will help as the end point are probabily fire walled. And that I CAN telnet onto their mail server from the exchange server. But here you go:

Code:
C:\DOCUME~1\PHYSICAL>tracert mail.spriproducts.com

Tracing route to mail.spriproducts.com [68.23.252.210]
over a maximum of 30 hops:

  1     1 ms     1 ms   <10 ms  192.168.2.254
  2    30 ms    49 ms   105 ms  btdhg516-hg1.ealing.broadband.bt.net [217.47.49.
200]
  3    30 ms    55 ms    89 ms  217.47.49.162
  4    81 ms    32 ms    88 ms  217.47.49.238
  5    31 ms    31 ms    31 ms  217.47.219.98
  6    31 ms    39 ms    35 ms  217.41.168.25
  7    33 ms    34 ms    35 ms  217.41.168.66
  8    36 ms    32 ms    32 ms  217.41.168.78
  9    43 ms    47 ms    42 ms  212.140.233.38
 10    41 ms    36 ms    31 ms  217.47.155.90
 11    32 ms    31 ms    32 ms  core1-pos3-2.ealing.ukcore.bt.net [62.6.200.1]
 12    36 ms    39 ms    37 ms  transit1-pos5-0.ealing.ukcore.bt.net [194.72.17.
122]
 13    57 ms    46 ms    41 ms  t2c1-p3-0.uk-eal.eu.bt.net [166.49.168.5]
 14   105 ms   106 ms   105 ms  t2c1-p4-1.us-ash.eu.bt.net [166.49.164.74]
 15   105 ms   105 ms   107 ms  ex2-g1-0-0.eqabva.sbcglobal.net [151.164.250.53]

 16   171 ms   164 ms   160 ms  bb1-p4-1.chcgil.ameritech.net [151.164.42.184]
 17   133 ms   129 ms   136 ms  ded1-g1-3-0.chcgil.ameritech.net [151.164.191.24
7]
 18   133 ms   128 ms   127 ms  spri-products-inc-1129807.cust-rtr.ameritech.net
 [68.251.223.238]
 19   126 ms   128 ms   125 ms  68-23-252-210.nettekinc.com [68.23.252.210]

Trace complete.
and

Code:
C:\DOCUME~1\PHYSICAL>tracert spriproducts.com

Tracing route to spriproducts.com [66.243.178.196]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.2.254
  2    29 ms    29 ms    32 ms  btdhg516-hg1.ealing.broadband.bt.net [217.47.49.
200]
  3    30 ms    29 ms    31 ms  217.47.49.130
  4    42 ms    36 ms    61 ms  217.47.49.238
  5    33 ms    30 ms    31 ms  217.47.219.98
  6    39 ms    43 ms    39 ms  217.41.168.25
  7    44 ms    48 ms    45 ms  217.41.168.66
  8    33 ms    31 ms    31 ms  217.41.168.78
  9    33 ms    38 ms    39 ms  212.140.233.38
 10    32 ms    31 ms    31 ms  217.47.155.83
 11    32 ms    35 ms    31 ms  core2-pos1-7.ealing.ukcore.bt.net [62.6.200.13]

 12    58 ms    57 ms    48 ms  transit1-pos4-0.ealing.ukcore.bt.net [194.72.9.2
38]
 13    45 ms    45 ms    43 ms  t2c1-p1-0.uk-eal.eu.bt.net [166.49.168.13]
 14   108 ms   105 ms   106 ms  t2c1-p4-1.us-ash.eu.bt.net [166.49.164.74]
 15   106 ms   106 ms   107 ms  sp0-4-asbnvaas.broadwing.com [206.223.115.72]
 16   114 ms   118 ms   111 ms  ge-3-1-0.a1.wash.broadwing.net [216.140.8.10]
 17   109 ms   111 ms   109 ms  p4-0.c0.wash.broadwing.net [216.140.8.89]
 18   113 ms   114 ms   115 ms  p6-0.c0.nwyk.broadwing.net [216.140.17.122]
 19   135 ms   132 ms   134 ms  216.140.16.209
 20   136 ms   134 ms   135 ms  s0-0-0.a1.chcg.broadwing.net [216.140.15.142]
 21   139 ms   137 ms   138 ms  g1-2-0-0.core2.chi.foc.broadwing.net [216.140.15
.146]
 22   137 ms   138 ms   140 ms  207-7-239-132.focaldata.net [207.7.239.132]
 23   140 ms   140 ms   141 ms  66.243.176.6
 24   142 ms   143 ms   141 ms  66.243.178.196
 25   141 ms   149 ms   145 ms  66.243.178.196
 26   154 ms   160 ms   157 ms  66.243.178.196

Trace complete.
Old 19 December 2006, 03:21 PM
  #12  
Nobbie
Scooby Regular
 
Nobbie's Avatar
 
Join Date: Apr 2006
Location: Herts
Posts: 299
Likes: 0
Received 0 Likes on 0 Posts
Default

OKay thats cool. If you can happily telnet onto thier dns server, from your mail server/external wan ip, then any ip blocking/filtering/spam lookup, etc, is out the question really.
If you smtp to thier mail server, and actually send an email to a live rcpt, do they get it?
Old 19 December 2006, 03:22 PM
  #13  
Nobbie
Scooby Regular
 
Nobbie's Avatar
 
Join Date: Apr 2006
Location: Herts
Posts: 299
Likes: 0
Received 0 Likes on 0 Posts
Default

PS trace route was just to prove to me that it was actually getting out of your building/environment.
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
Primey
ICE
14
24 February 2017 12:46 AM
Mattybr5@MB Developments
Full Cars Breaking For Spares
28
28 December 2015 11:07 PM
PetrolHeadKid
Driving Dynamics
10
05 October 2015 05:19 PM
Ganz1983
Subaru
5
02 October 2015 09:22 AM
Primey
General Technical
2
30 September 2015 11:28 AM



Quick Reply: Odd exchange 2003 problem



All times are GMT +1. The time now is 10:58 AM.