Turnpike POP3 server and port 110

[Jim Smith]

I am not sure this is a Turnpike problem, may be NT related.

I am trying to set up the turnpike pop3 server so the family can collect
their mail without disturbing me. As far as I can see I have done
everything necessary in Turnpike, but no joy.

Outlook Excess reports some mumbo-jumbo which implies that port 110 is
not accessible.

telnet host 110 gives the following

Connecting To 10.1.1.4...Could not open connection to the host, on port
110.
No connection could be made because the target machine actively refused
it.

telnet 127.0.0.1 110 produces a pop3 server ready message, but I can't
get any response out of it.

AKAIK, I have not blocked any ports.

Are there any default settings in Windows XP which would block port 110?
Any other clues?

I'm using XP Professional with most of the updates, but not SP1.
Turnpike Connect is running in no dial-up mode.

TIA
--
Jim Smith
Because of their persistent net abuse, I ignore mail from
these domains (among others) .yahoo.com .hotmail.com .kr .cn .tw
For an explanation see <http://www.jimsmith.demon.co.uk/spam>

[John Underwood]

On Sat, 21 Dec 2002 at 11:42:11, Jim Smith wrote in
demon.ip.support.turnpike
(Reference: <uAFjkpGT...@jimsmith.demon.co.uk>)

>Connecting To 10.1.1.4...Could not open connection to the host, on port
>110.
>No connection could be made because the target machine actively refused
it.

Is Connect running and connected on the target machine? (Pay particular
attention to the second half of that condition).

If not, there isn't a port 110 open.
--
John Underwood
The Reply-To: address will remain in use for at least 30 days, you may write to
me using jo...@theunderwoods.org.uk. Mail to the From: address may be
rejected or a complaint raised about it as UCE/Spam.

[Jim Smith]

In message <cIDPhHIs...@theunderwoods.org.uk>, John Underwood
<newsab...@theunderwoods.org.uk> writes

>On Sat, 21 Dec 2002 at 11:42:11, Jim Smith wrote in
>demon.ip.support.turnpike
>(Reference: <uAFjkpGT...@jimsmith.demon.co.uk>)
>
>
>>Connecting To 10.1.1.4...Could not open connection to the host, on
>>port 110.
>>No connection could be made because the target machine actively
>>refused
>it.
>
>Is Connect running and connected on the target machine? (Pay particular
>attention to the second half of that condition).
>

It is running and connected, and it says "POP3/IMAP servers idle" at the
bottom if that has any significance.

Running netstat shows no difference in open ports between connect not
connected, connect connected, and connect connected but with the pop3
server disabled.

[Andrew Coates]

In article <GcApzMHH$ZB+...@jimsmith.demon.co.uk>, Jim Smith
<j...@jimsmith.demon.co.uk> writes

>Running netstat shows no difference in open ports between connect not
>connected, connect connected, and connect connected but with the pop3
>server disabled.

what about "netstat -a"?

I can see POP3 in listening state here, but better for this kind of
thing is TCPView: http://www.sysinternals.com/ntw2k/source/tcpview.shtml

if you're getting a reply from Turnpike's POP3 server from the machine
it's running on then none of this matters really - something is blocking
access from the other machine(s)

do you have other TCP traffic working between the two machines?

I don't know of any default setting that would block POP3 - I have a
more or less default installation of XP Pro here with Connect's POP3
server running, and I can access it from remote machines

--
Andrew Coates

[Jim Smith]

In message <cvNCt2Nb...@pligplob.com>, Andrew Coates
<ne...@pligplob.com> writes

>In article <GcApzMHH$ZB+...@jimsmith.demon.co.uk>, Jim Smith
><j...@jimsmith.demon.co.uk> writes
>
>>Running netstat shows no difference in open ports between connect not
>>connected, connect connected, and connect connected but with the pop3
>>server disabled.
>
>what about "netstat -a"?
>
>I can see POP3 in listening state here, but better for this kind of
>thing is TCPView: http://www.sysinternals.com/ntw2k/source/tcpview.shtml
>

TCPView showed that one of the components of my virus scanner was
listening on 110 127.0.0.1. Killing that and restarting connect sorted
the problem. I now have to work out how to disable that part of the
virus scanner without breaking it.

Thanks a lot.

[John Underwood]

On Sun, 22 Dec 2002 at 21:10:19, Jim Smith wrote in
demon.ip.support.turnpike
(Reference: <qkPiNjI7...@jimsmith.demon.co.uk>)

>I now have to work out how to disable that part of the virus scanner
>without breaking it.

I would ask what is doing and probably suspect that scanning mail is the
most likely. Two options:

Do without the mail scan - if you are using TP it has very little
benefit and, in this case, an even more obvious disadvantage than usual.

See if you can run either of the applications on another IP such as
127.0.0.2