TCP 25 closed

I have a fresh install of Windows Server 2003 R2 - everything is
working like a champ. However, I can not send email from the server.
It seems like the TCP 25 is closed however this is no AV or firewall
software installed. Any other server works just fine. I've tried
disabling the Windows Firewall as well but that did not help.

If you are sending,..25 is irrelevant. Port 25 is the receiving port.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"AF" <(E-Mail Removed)> wrote in message
news:29e061e5-3684-4166-bfc1-(E-Mail Removed)...
>I have a fresh install of Windows Server 2003 R2 - everything is
> working like a champ. However, I can not send email from the server.
> It seems like the TCP 25 is closed however this is no AV or firewall
> software installed. Any other server works just fine. I've tried
> disabling the Windows Firewall as well but that did not help.

In news:(E-Mail Removed),
Phillip Windell <(E-Mail Removed)> requesting assistance, typed the
following:
> If you are sending,..25 is irrelevant. Port 25 is the receiving port.

Well, I guess it depends on the prespective? Technically to a non-MAPI
client's prespective, 25 would be the send port, and 110 (POP3) or 143
(IMAP4) are the receive ports. But server to server, port 25 is used for
send/receive.

Cheers!

Ace

"Ace Fekay [MVP Direcrtory Services]" <(E-Mail Removed)> wrote
in message news:5F5EEF62-B4F8-4299-A063-(E-Mail Removed)...
> In news:(E-Mail Removed),
> Phillip Windell <(E-Mail Removed)> requesting assistance, typed the
> following:
>> If you are sending,..25 is irrelevant. Port 25 is the receiving port.
>
> Well, I guess it depends on the prespective? Technically to a non-MAPI
> client's prespective, 25 would be the send port, and 110 (POP3) or 143
> (IMAP4) are the receive ports. But server to server, port 25 is used for
> send/receive.

True.

AF, can you telnet from the Mail Server (while sitting at it) to another
mail server using port 25 as the target port?

"Telnet <IP# of target> 25"

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

On Aug 29, 11:44*am, "Phillip Windell" <philwind...@hotmail.com>
wrote:
> "Ace Fekay [MVP Direcrtory Services]" <firstnamelastn...@hotmail.com> wrote
> in messagenews:5F5EEF62-B4F8-4299-A063-(E-Mail Removed)...
>
> > Innews:(E-Mail Removed),
> > Phillip Windell <philwind...@hotmail.com> requesting assistance, typed the
> > following:
> >> If you are sending,..25 is irrelevant. *Port 25 is the receiving port.
>
> > Well, I guess it depends on the prespective? Technically to a non-MAPI
> > client's prespective, 25 would be the send port, and 110 (POP3) or 143
> > (IMAP4) are the receive ports. But server to server, port 25 is used for
> > send/receive.
>
> True.
>
> AF, can you telnet from the Mail Server (while sitting at it) to another
> mail server using port 25 as the target port?
>
> "Telnet <IP# of target> 25"
>
> --
> Phillip Windellwww.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------

From the mail server I can telnet to other mail servers on TCP 25. I
can telnet outside of the network (Hotmail) wihtout issue.

From the problematic server I can't telnet to any server - local or
remote.

Outlook Express throws an "Unable to establish a connection" error.

"AF" <(E-Mail Removed)> wrote in message
news:0b435c0c-4dc8-4188-b242-(E-Mail Removed)...

> From the mail server I can telnet to other mail servers on TCP 25. I
> can telnet outside of the network (Hotmail) wihtout issue.

> From the problematic server I can't telnet to any server - local or
> remote.

That just doesn't sound logical at all.
Is the problem machine on the same subnet as the LAN's mail server?

Try two things:

1. Telnet from the problem server to the internal LAN's mail server
directly,...use the machines actual IP# on the LAN,..not any names.

2. Temporarily load IIS with SMTP on the problem server itself. Open a
command prompt and telent to itself on Port 25. Use the machine's own
IP#,..not names, not 127.0.0.1

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

On Aug 29, 5:24*pm, "Phillip Windell" <philwind...@hotmail.com> wrote:
> "AF" <af.at.w...@gmail.com> wrote in message
>
> news:0b435c0c-4dc8-4188-b242-(E-Mail Removed)...
>
> > From the mail server I can telnet to other mail servers on TCP 25. I
> > can telnet outside of the network (Hotmail) wihtout issue.
> > From the problematic server I can't telnet to any server - local or
> > remote.
>
> That just doesn't sound logical at all.
> Is the problem machine on the same subnet as the LAN's mail server?
>
> Try two things:
>
> 1. Telnet from the problem server to the internal LAN's mail server
> directly,...use the machines actual IP# on the LAN,..not any names.
>
> 2. Temporarily load IIS with SMTP on the problem server itself. *Open a
> command prompt and telent to itself on Port 25. *Use the machine's own
> IP#,..not names, not 127.0.0.1
>
> --
> Phillip Windellwww.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------

Both return:
"Could not open connection to the host, on port 25: connect failed."

"AF" <(E-Mail Removed)> wrote in message
news:cb142349-b2cc-425d-abde-(E-Mail Removed)...
On Aug 29, 5:24 pm, "Phillip Windell" <philwind...@hotmail.com> wrote:
> "AF" <af.at.w...@gmail.com> wrote in message
>
> news:0b435c0c-4dc8-4188-b242-(E-Mail Removed)...
>
> > From the mail server I can telnet to other mail servers on TCP 25. I
> > can telnet outside of the network (Hotmail) wihtout issue.
> > From the problematic server I can't telnet to any server - local or
> > remote.
>
> That just doesn't sound logical at all.
> Is the problem machine on the same subnet as the LAN's mail server?
>
> Try two things:
>
> 1. Telnet from the problem server to the internal LAN's mail server
> directly,...use the machines actual IP# on the LAN,..not any names.
>
> 2. Temporarily load IIS with SMTP on the problem server itself. Open a
> command prompt and telent to itself on Port 25. Use the machine's own
> IP#,..not names, not 127.0.0.1
>
> --
> Phillip Windellwww.wandtv.com
>
> The views expressed, are my own and not those of my employer, or
> Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------

Both return:
"Could not open connection to the host, on port 25: connect failed."

I have no idea. That is one screwed up machine.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

In news:cb142349-b2cc-425d-abde-(E-Mail Removed),
AF <(E-Mail Removed)> requesting assistance, typed the following:

> Both return:
> "Could not open connection to the host, on port 25: connect failed."

Is Windows Defender, antivirus, or some other third party antispam tool
installed? Disable everything and try again.

Was Zone Alarm ever installed on the problem box?

Ace