I am not that familiar with MS Exchange and the person that helped me setup the network and did the exchange is no longer in contact so, I apologize for my dumbness with this issue. My friends office is using one server for his internet, file share and exchange. Its 2003 small business server, we can recieve all email but sending to some clients fails. It appears to just sit in que and never send out. HELP!!!!!!!!!

Take a look at the target addresses for the messages in the queues and see if you can resolve the domain names to which they're destined using nslookup. Missy

Sorry to ask this but, can you give me an example of the nslookup and , are u able to chat tomorrow morning for questions? Sorry to bug ya but, i need to get this figured out quickly and I am almost about to lose my mind..

This is really basic. To use nslookup, go to a command prompt (preferably ON the hub server so you'll see what it sees) and type nslookup. Then, you want to define the type of DNS record you're looking for - since we're talking email, you'll look for an MX record. Then you want to query for the domain name that your server is having an issue delivering to. See below for an example, with my comments (in parenthesis, italicized) C:\>nslookupDefault Server: ns3.somwhere.com (the Default Server is the name server I am using.)Address: 199.199.199.84 (this is the IP address of my Default Server; note that I've changed these records) > set type=mx (Here's where you define what kind of record you want to be shown)> domain.com (this is the name of the domain that you want to find records for)Server: ns3.somewhere.com (again, the name server that's providing the results)Address: 199.199.199.84 (again, the IP address of the name server that's providing the results) Non-authoritative answer: (the stuff below here is the important stuff)domain.com MX preference = 10, mail exchanger = sentry.domainbank.com (sentry.domainbank.com is the mail exchanger - MX - record for domain.com) domain.com nameserver = ns2.dotsterhost.comdomain.com nameserver = ns3.dotsterhost.comdomain.com nameserver = ns1.dotsterhost.com >Once you've determined the server that you need to talk to (i.e. sentry.domainbank.com above - the server named in the MX record for the domain your server is having issues delivering mail to), you will want to telnet to that server from your hub and see if it responds. Missy

Hopefully this was done right. This is what I did and the response I got. So, any clues on the issue???? Microsoft Windows [Version 5.2.3790](C) Copyright 1985-2003 Microsoft Corp. C:\Documents and Settings\Administrator.GTBFSRV01>nslookupDefault Server: gtbfsrv01.gtbf.localAddress: 192.168.1.5 > set type=mx> roadrunner.comServer: gtbfsrv01.gtbf.localAddress: 192.168.1.5 Non-authoritative answer:roadrunner.com MX preference = 20, mail exchanger = cdptpa-smtpin02.mail.rr.com roadrunner.com MX preference = 10, mail exchanger = cdptpa-smtpin01.mail.rr.com > telnet cdptpa-smtpin02.mail.rr.comServer: cdptpa-smtpin02.mail.rr.comAddress: 75.180.132.244 DNS request timed out. timeout was 2 seconds.*** Request to cdptpa-smtpin02.mail.rr.com timed-out

Just a side note.... I get the same response for yahoo. Microsoft Windows [Version 5.2.3790](C) Copyright 1985-2003 Microsoft Corp. C:\Documents and Settings\Administrator.GTBFSRV01>nslookupDefault Server: gtbfsrv01.gtbf.localAddress: 192.168.1.5 > set type=mx> yahoo.comServer: gtbfsrv01.gtbf.localAddress: 192.168.1.5 Non-authoritative answer:yahoo.com MX preference = 1, mail exchanger = f.mx.mail.yahoo.comyahoo.com MX preference = 1, mail exchanger = g.mx.mail.yahoo.comyahoo.com MX preference = 1, mail exchanger = h.mx.mail.yahoo.comyahoo.com MX preference = 1, mail exchanger = a.mx.mail.yahoo.comyahoo.com MX preference = 1, mail exchanger = b.mx.mail.yahoo.comyahoo.com MX preference = 1, mail exchanger = c.mx.mail.yahoo.comyahoo.com MX preference = 1, mail exchanger = d.mx.mail.yahoo.comyahoo.com MX preference = 1, mail exchanger = e.mx.mail.yahoo.com> telnet f.mx.mail.yahoo.comServer: f.mx.mail.yahoo.comAddress: 98.137.54.237 DNS request timed out. timeout was 2 seconds.*** Request to f.mx.mail.yahoo.com timed-out> telnet e.mx.mail.yahoo.comServer: e.mx.mail.yahoo.comAddress: 67.195.168.230 DNS request timed out. timeout was 2 seconds.*** Request to e.mx.mail.yahoo.com timed-out

Both nslookups returned results. The result you care about is this: Non-authoritative answer:roadrunner.com MX preference = 20, mail exchanger = cdptpa-smtpin02.mail.rr.com roadrunner.com MX preference = 10, mail exchanger = cdptpa-smtpin01.mail.rr.com Now what you need to do is to try to telnet to port 25 by hand to that server and see if you can have a conversation. http://support.microsoft.com/kb/153119 explains how to do this - you'll use: > telnet cdptpa-smtpin02.mail.rr.com 25 to initiate the conversation. The article explains this - ignore the version numbers at the bottom of the article, this is smtp. :) Missy

Oh - and make sure that you put the 25 after the MX name. You have to define the smtp port. Missy

Here is the response: 554 5.7.1 - Connection refused. IP name lookup failed for 12.234.236.100 Connection to host lost. C:\Documents and Settings\Administrator.GTBFSRV01>

Well, that's your problem. They won't accept mail from your server. Do you have PTR records set up in DNS for your servers?

ptr records???? not sure..sorry.

Bing is your friend. http://www.bing.com/search?q=create+PTR+record&src=IE-SearchBox&FORM=IE8SRC This is DNS stuff.

ok.. I will contact my isp and discuss. Thanks. I will update you. I owe ya lunch...

:) Good luck!

ok.... Now I am really gonna go nuts. Called isp(AT&T). they state that because they are not hosting the domain that they cannot setup reverse dns on the ip. We either have to see if godaddy will accept delegation from AT&T for reverse dns or setup a domain on AT&T and then they will do reverse on that one and the other. Does this sound right?

Hello trig, Most ISP's will host your Reverse DNS zones while they allow you to host your own Forward DNS zones using a registrar like Godaddy. What AT&T policy for T-1 & higher bandwidth requires is that they host both your forward and reverse DNS zones or that you host both yourself. They don't want to split apart forward and reverse zones between two delegations. If you are up to the challenge, my suggestion is that you go to Godaddy and look up the A records, CNames and MX records and write them down. Then call AT&T and request for them to host your forward dns. Give them the information so that they can input your A records, Cnames and MX records for you in their DNS forward zones and request a reverse PTR like mail.yourdomain.com (or whatever is your mail server FQDN is) Next, go back to godaddy, and change the Names Servers to point to whatever NameServers AT&T tell you. See: AT&T Reverse DNS for T1 Policy and Contact Info and test your mail parameters with http://www.mxtoolbox.com Also, RR may be refusing your conenction based of packet fragmentation. They are very finicky about MTU sizes. My best advice is that you get an IT person who has experience in this. This may be a bit of a technical stretch that will have you chasing your own tail without proper technical background... Not to mention people aren't happy when their E-mails don't work... Miguel Fra / Falcon ITS Computer & Network Support , Miami, FL Visit our Knowledgebase Sharepoint Site

On Tue, 13 Apr 2010 21:20:59 +0000, trig1100 wrote:>ok.... Now I am really gonna go nuts. Called isp(AT&T). they state that because they are not hosting the domain that they cannot setup reverse dns on the ip. We either have to see if godaddy will accept delegation from AT&T for reverse dns or setup a domain on AT&T and then they will do reverse on that one and the other. Does this sound right? No, it doesn't.If AT&T is providing the IP address then they should create a PTRrecord for the IP address and put whatever name you want in there --assuming that the IP addres isn't a dynamically assigned one.For the vast majority of MTAs it doen't matter what name is returnedby the PTR record query. What's important is that there IS a PTRrecord.If AT&T wants to get snarky, tell them to assign the name12-234-236-100.att.com to the record. That'll get you past almostevery check.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

Rich, I agree 100% with you. It does not sound right. If you are talking about AT&T DSL, they will create a PTR record for you, no problemo. However for T-1 and higher, they want to delegate the reverse zone to you. I can't understand the reasoning behind it. MiguelMiguel Fra / Falcon ITS Computer & Network Support, Miami, FL Visit our Knowledgebase Sharepoint Site

On Wed, 14 Apr 2010 13:23:11 +0000, Falcon ITS wrote:>I agree 100% with you. It does not sound right. >>If you are talking about AT&T DSL, they will create a PTR record for you, no problemo.>>However for T-1 and higher, they want to delegate the reverse zone to you. I can't understand the reasoning behind it.I expect they think you own that portion of the network. Do you? Howmany IP addresses are in your netblock?If you already have an external DNS then setting up the zone is no bigdeal.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP