• RSS
  • Twitter
  • FaceBook

Exchange Server Forums

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | My Subscription | My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out

Newb-2k3-Can Not Send

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2003] >> Installation >> Newb-2k3-Can Not Send Page: [1]
Login
Message << Older Topic   Newer Topic >>
Newb-2k3-Can Not Send - 3.May2007 2:54:58 AM   
dassey

 

Posts: 8
Joined: 3.May2007
Status: offline
Hello. I am really just trying to learn exchange, but apparently not doing a good job of it. I have a Windows 2003 Enterprise Server on the net. I installed AD and let it install DNS, the DNS was setup to point to my dedicated server providers DNS, they also have an MX record pointing to me. I installed Exchange 2003, installed all security updates, SP1 and SP2 and all other security updates. So on one server I have AD, DNS and exchange. I can browse to the OWA site and can connect to the pop3 using outlook. I can recieve mail from anywhere on the net and I can route mail internally from pop3 and OWA and can telnet to 25 and route to myself. But I can not send mail to anyone outside my setup! I have several books on the topic that I have been scanning through, but no clean cut: this is how you enable sending email. I imagine it is something basic I am missing, but if anyone has any pointers on where to look, let me know. In the mail tracking center all outgoing messages are stuck at: SMTP: Message Router and Queued for Remote Delievery. If i do an nslookup, i can see other MX servers on the net.

Any and all help is appreciated!

I do not get any error messages in inbox from pop or from owa when i send messages, appears to be fine, but look in queues and its stuck in the queue. I imagine its something to do with DNS or the remote server will not take my messages perhaps, still reading the forums and books to see if i can find a solution...just wish the field was narrowed down a bit.

I hate to tell yall this, but no firewall on the server or protecting the server...like i said, its just a testing thing, a see if i can do it thing. And I do not use a smarthost

< Message edited by dassey -- 3.May2007 6:37:29 AM >
Post #: 1
RE: Newb-2k3-Can Not Send - 3.May2007 8:05:25 AM   
sergebsn

 

Posts: 106
Joined: 10.Jan.2007
From: Russia
Status: offline
What is about telnet from server where is Exchange on external servers?
What's about logs, if they are off - to do they on.

(in reply to dassey)
Post #: 2
RE: Newb-2k3-Can Not Send - 3.May2007 11:28:31 AM   
dassey

 

Posts: 8
Joined: 3.May2007
Status: offline
quote:

ORIGINAL: sergebsn

What is about telnet from server where is Exchange on external servers?
What's about logs, if they are off - to do they on.


Sorry, I am not sure that I understand you 100%. I can telnet from outside my organization to my 25 port and send internally, but not externally. I do have message tracking on, for the relevant message I get the end status message of 1034. I will post a partial from my C:\Program Files\Exchsrvr\KNIGHT.log.

One thing I noticed. My server name is knight.mydomain.com, my MX record is pointing to mail.mydomain.com, in my Default SMTP Virtual Server Properties/Delievery/Advanced my FQDN was set to knight.mydomain.com, i just changed it to mydomain.com. The below ugly snippet is from when i try to send from OWA to a gmail account. I tried to send from my support account.

2007-5-3    11:6:35 GMT    -    -    -    KNIGHT    -    mygmail@gmail.com    1019    46B1D7FCB71E5949B45F97207DB468C63660@Knight.myrealdomain.com    0    0    228    1    2007-5-2 21:29:3 GMT    0    -    -    -    support@myrealdomain.com    -
2007-5-3    11:6:35 GMT    -    -    -    KNIGHT    -    mygmail@GMAIL.COM    1025    46B1D7FCB71E5949B45F97207DB468C63661@Knight.myrealdomain.com    0    0    454    1    2007-5-2 22:31:38 GMT    0    -    -    -    support@myrealdomain.com    -
2007-5-3    11:6:35 GMT    -    -    -    KNIGHT    -    mygmail@GMAIL.COM    1024    46B1D7FCB71E5949B45F97207DB468C63661@Knight.myrealdomain.com    0    0    454    1    2007-5-2 22:31:38 GMT    0    -    -    -    support@myrealdomain.com    -
2007-5-3    11:6:35 GMT    -    -    -    KNIGHT    -    mygmail@GMAIL.COM    1033    46B1D7FCB71E5949B45F97207DB468C63661@Knight.myrealdomain.com    0    0    454    1    2007-5-2 22:31:38 GMT    0    -    -    -    support@myrealdomain.com    -
2007-5-3    11:6:35 GMT    -    -    -    KNIGHT    -    mygmail@GMAIL.COM    1034    46B1D7FCB71E5949B45F97207DB468C63661@Knight.myrealdomain.com    0    0    454    1    2007-5-2 22:31:38 GMT    0    -    -    -    support@myrealdomain.com    -

(in reply to sergebsn)
Post #: 3
RE: Newb-2k3-Can Not Send - 3.May2007 5:05:28 PM   
dassey

 

Posts: 8
Joined: 3.May2007
Status: offline
results of smtpdiag (IP and HostName have been changed to protect the innocent)

C:\SmtpDiag>SmtpDiag.exe support@mydomain.com mygmail@gmail.com /v

Searching for Exchange external DNS settings.
Computer name is KNIGHT.
VSI 1 has the following external DNS servers:
There are no external DNS servers configured.

Checking SOA for gmail.com.
Checking external DNS servers.
Checking internal DNS servers.

Checking TCP/UDP SOA serial number using DNS server [127.0.0.1].
TCP test succeeded.
UDP test succeeded.
Serial number: 2007041201
SOA serial number match: Passed.

Checking local domain records.
Starting TCP and UDP DNS queries for the local domain. This test will try to
validate that DNS is set up correctly for inbound mail. This test can fail for
3 reasons.
   1) Local domain is not set up in DNS. Inbound mail cannot be routed to
local mailboxes.
   2) Firewall blocks TCP/UDP DNS queries. This will not affect inbound mail,
but will affect outbound mail.
   3) Internal DNS is unaware of external DNS settings. This is a valid
configuration for certain topologies.
Checking MX records using TCP: mydomain.com.
A:     mydomain.com [205.129.16.11]
Checking MX records using UDP: mydomain.com.
A:     mydomain.com [205.129.16.11]
Both TCP and UDP queries succeeded. Local DNS test passed.

Checking remote domain records.
Starting TCP and UDP DNS queries for the remote domain. This test will try to
validate that DNS is set up correctly for outbound mail. This test can fail for
3 reasons.
   1) Firewall blocks TCP/UDP queries which will block outbound mail. Windows
2000/NT Server requires TCP DNS queries. Windows Server 2003 will use UDP
queries first, then fall back to TCP queries.
   2) Internal DNS does not know how to query external domains. You must
either use an external DNS server or configure DNS server to query external
domains.
   3) Remote domain does not exist. Failure is expected.
Checking MX records using TCP: gmail.com.
MX:    gsmtp163.google.com (50)
MX:    gsmtp183.google.com (50)
MX:    gmail-smtp-in.l.google.com (5)
MX:    alt1.gmail-smtp-in.l.google.com (10)
MX:    alt2.gmail-smtp-in.l.google.com (10)
A:     gsmtp163.google.com [64.233.163.27]
A:     gsmtp183.google.com [64.233.183.27]
A:     alt1.gmail-smtp-in.l.google.com [66.249.91.27]
Checking MX records using UDP: gmail.com.
MX:    gsmtp183.google.com (50)
MX:    gmail-smtp-in.l.google.com (5)
MX:    alt1.gmail-smtp-in.l.google.com (10)
MX:    alt2.gmail-smtp-in.l.google.com (10)
MX:    gsmtp163.google.com (50)
Both TCP and UDP queries succeeded. Remote DNS test passed.
A:     gmail-smtp-in.l.google.com [64.233.185.27]
A:     gmail-smtp-in.l.google.com [64.233.185.114]
A:     alt2.gmail-smtp-in.l.google.com [209.85.135.27]

Checking MX servers listed for mygmail@gmail.com.
Connecting to gmail-smtp-in.l.google.com [64.233.185.114] on port 25.
Connecting to the server failed. Error: 10051
Failed to submit mail to gmail-smtp-in.l.google.com.
Connecting to gmail-smtp-in.l.google.com [64.233.185.27] on port 25.
Connecting to the server failed. Error: 10060
Failed to submit mail to gmail-smtp-in.l.google.com.
Connecting to alt2.gmail-smtp-in.l.google.com [209.85.135.27] on port 25.
Connecting to the server failed. Error: 10060
Failed to submit mail to alt2.gmail-smtp-in.l.google.com.
Connecting to alt1.gmail-smtp-in.l.google.com [66.249.91.27] on port 25.
Connecting to the server failed. Error: 10060
Failed to submit mail to alt1.gmail-smtp-in.l.google.com.
Connecting to gsmtp183.google.com [64.233.183.27] on port 25.
Connecting to the server failed. Error: 10060
Failed to submit mail to gsmtp183.google.com.
Connecting to gsmtp163.google.com [64.233.163.27] on port 25.
Connecting to the server failed. Error: 10060
Failed to submit mail to gsmtp163.google.com.

C:\SmtpDiag>

(in reply to dassey)
Post #: 4
RE: Newb-2k3-Can Not Send - 3.May2007 11:00:37 PM   
dassey

 

Posts: 8
Joined: 3.May2007
Status: offline
Well, it is either a very difficult question or a very easy question. I am going to assume it has something to do with DNS.

from the Mail Wizard Howto on this site:
///To send E-Mail through DNS you have to configure your internal DNS Server to forward E-Mail to the internet (for example with the help of Root hints, Forwarder (conditional forwarding)).///

So I will assume this means me...if anyone knows of a howto for setting up these types of DNS entries, let me know.

(in reply to dassey)
Post #: 5
RE: Newb-2k3-Can Not Send - 4.May2007 1:54:44 AM   
uemurad

 

Posts: 8232
Joined: 7.Jan.2004
From: California, USA
Status: offline
Check your firewall.  Are you allowing outbound TCP port 53 (DNS) and TCP port 25 (SMTP) from your Exchange server?

_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange (2007-2011)
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to dassey)
Post #: 6
RE: Newb-2k3-Can Not Send - 4.May2007 2:07:33 AM   
sergebsn

 

Posts: 106
Joined: 10.Jan.2007
From: Russia
Status: offline
Hi, dassey
I mean, can you make telnet from your Exchange server to the external servers in internet, for example,"telnet gmail.com 25"?

(in reply to uemurad)
Post #: 7
RE: Newb-2k3-Can Not Send - 4.May2007 2:28:09 AM   
dassey

 

Posts: 8
Joined: 3.May2007
Status: offline
If I had yall's smarts I would throw mine away. I have no firewall on my dedicated server, but apparently something is blocking outbound port 25, either something on the server or something with the provider, GoDaddy. I will check this out and let yall know. If someone already knows something about godaddy dedicated hosting, let me know.

I can not telnet to gmail.com from my computer or the server, but from my computer I can telnet to gmail-smtp-in.l.google.com 25, but from my server I can not.

Thanks for the help, I most likely will be back once i got the basics solved.
Dassey

(in reply to sergebsn)
Post #: 8
RE: Newb-2k3-Can Not Send - 4.May2007 2:54:51 AM   
sergebsn

 

Posts: 106
Joined: 10.Jan.2007
From: Russia
Status: offline
quote:

I can not telnet to gmail.com from my computer or the server, but from my computer I can telnet to gmail-smtp-in.l.google.com 25, but from my server I can not.


The problem from you Exchange server...

Do you have firewall on your organization?? If yes, problem in it.

(in reply to dassey)
Post #: 9
RE: Newb-2k3-Can Not Send - 4.May2007 5:31:28 AM   
dassey

 

Posts: 8
Joined: 3.May2007
Status: offline
I guess I found the issue:
http://help.godaddy.com/article.php?article_id=122&topic_id=120

All outbound email from a dedicated server must use this relay server:
k2smtpout.secureserver.net

So i guess I need to hook up a smart host or reconfigure the outgoing port to be something other than 25

(in reply to dassey)
Post #: 10
RE: Newb-2k3-Can Not Send - 4.May2007 5:38:24 AM   
sergebsn

 

Posts: 106
Joined: 10.Jan.2007
From: Russia
Status: offline
At first hear about "GoDaddy".
Will learn it.

(in reply to dassey)
Post #: 11

Page:   [1] << Older Topic    Newer Topic >>
All Forums >> [Microsoft Exchange 2003] >> Installation >> Newb-2k3-Can Not Send Page: [1]
Jump to:

New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Follow TechGenix on Twitter