Re: Newbie question... Exchange 2003 queued messages

Figure out what's blocking the port 25 traffic.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Neon" <Neon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1C25CC42-D9D5-4F1B-9E09-EE6E684AA81E@xxxxxxxxxxxxxxxx
I can do an NSLOOKUP, and get the proper DNS information (set to the
firewall
as mentioned in the original post). When I try to TELNET to the
mail.domain.com through port 25, it times out. If I try to TELNET to just
the domain.com, it gives me an unable to open port error. Is there
anything
else I can try to troubleshoot the problem?

Thanks;

Wayne Roberts


"Ed Crowley [MVP]" wrote:

From the Exchange server use NSLOOKUP to find the mail server name
corresponding to the domain, such as:

NSLOOKUP
SET TYPE=MX
domain.com

Then telnet to port 25 of the mail server servicing this domain's mail as
shown in the results of the NSLOOKUP you just did:

TELNET mail.domain.com 25

Do you get a connection?
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Neon" <Neon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:22B4686A-E62C-4CF4-A63D-27CFD7E749D5@xxxxxxxxxxxxxxxx
I am trying to set up a new Exchange 2003 server on a Windows 2003
server.
I
think I have everything set up, but when I send a message to an
Internet
address, the message goes to an SMTP queue, and remains there with a
'queued'
status. The server is behing a firewall, and uses a private IP
address.
It
is set up to forward smtp mail via DNS, not through a smart host. I
have
set
up the firewall (which has a public IP address) to forward smtp out
from
the
server, and forward POP3 and IMap from the outside world to the server.
The
DNS for the domain is directed to the firewall's public address as is
the
mx
record. Is there a trick to getting exchange to work with a private IP
address, or does it look like I don't have the firewall set up
properly?

Thanks

Wayne Roberts






.