Blocked POP Port 110

  • Thread starter Thread starter Ignis Fatuus
  • Start date Start date
I

Ignis Fatuus

What: Win2k SP2 desktop. Cable broadband. NAT router. No sw
firewall. Using Network Ice.

Issue: Several months prior the pop server connection to the ISP
stopped working. No idea why. I tried several dift fixes. None of
which worked. Initially I thought the port was blocked. It wasn't.
the pop server should be pop.west.cox.net but I couldnt even telnet
into it. OK fine. So I try pop.east.cox.net and it works. Everything
is fine. Email client works again. Tonight it stops working. try to
telnet into pop.east.cox.net and it fails just like telnet into
pop.west.cox.net failed months ago.

ISP has no idea. It's not on their end. I believe them b/c I can telnet
into the same port on a laptop using the *same* router for the Net
connection.

I've tried disconnecting the router and connecting directly to the pc
with the same results.

I've tried uninstalling/reinstalling networking and rebotting with the
same results.

I've tried stopping the AV service and quitting the app. No go. Same
result.

I've tried stopping the Network Ice service and quitting the app. No
go. Same result.

Port 110 still will not receive.

Now what? Will a system reinstall even work at this point? If I've
unin/rein all networking protocols what can a system reinstall possibly
do. Whatever the problem is the port in question is somehow blocked
since the pop.west/east.cox.net will not work. I can send email just
fine through the clients, but it won't receive.

One other thing. The email client works just fine for newsgroups. Can
send/receive no problem whatsoever.

Any other suggestions/comments?
 
Ignis said:
What: Win2k SP2 desktop. Cable broadband. NAT router. No sw
firewall. Using Network Ice.

Issue: Several months prior the pop server connection to the ISP
stopped working. No idea why. I tried several dift fixes. None of
which worked. Initially I thought the port was blocked. It wasn't.
the pop server should be pop.west.cox.net but I couldnt even telnet
into it. OK fine. So I try pop.east.cox.net and it works.
Everything is fine. Email client works again. Tonight it stops
working. try to telnet into pop.east.cox.net and it fails just like
telnet into pop.west.cox.net failed months ago.

ISP has no idea. It's not on their end. I believe them b/c I can
telnet into the same port on a laptop using the *same* router for the
Net connection.
I've tried disconnecting the router and connecting directly to the pc
with the same results.

I've tried uninstalling/reinstalling networking and rebotting with the
same results.

I've tried stopping the AV service and quitting the app. No go. Same
result.

I've tried stopping the Network Ice service and quitting the app. No
go. Same result.

Port 110 still will not receive.

Now what? Will a system reinstall even work at this point? If I've
unin/rein all networking protocols what can a system reinstall
possibly do. Whatever the problem is the port in question is
somehow blocked since the pop.west/east.cox.net will not work. I can
send email just fine through the clients, but it won't receive.
One other thing. The email client works just fine for newsgroups. Can
send/receive no problem whatsoever.

Any other suggestions/comments?
Click to expand...

New development. So it seems port 110 is not "blocked" after all. It
is working very ssssssssslllllllllllllllooooooowly and timing out in the
process. I configged the same profile in Thunderbird and it
sent/received just fine albeit slowly. Now it's working correctly in
Outlook albeit slowly. Can anyone comment on this? Is this a
Microcrap issue or the ISP's slow email servers? It seems to be on my
end and not being able to telnet into port 110 seems to be the key.
 
Ignis said:
What: Win2k SP2 desktop. Cable broadband. NAT router. No sw
firewall. Using Network Ice.

Issue: Several months prior the pop server connection to the ISP
stopped working. No idea why. I tried several dift fixes. None of
which worked. Initially I thought the port was blocked. It wasn't.
the pop server should be pop.west.cox.net but I couldnt even telnet
into it. OK fine. So I try pop.east.cox.net and it works.
Everything is fine. Email client works again. Tonight it stops
working. try to telnet into pop.east.cox.net and it fails just like
telnet into pop.west.cox.net failed months ago.

ISP has no idea. It's not on their end. I believe them b/c I can
telnet into the same port on a laptop using the *same* router for the
Net connection.
I've tried disconnecting the router and connecting directly to the pc
with the same results.

I've tried uninstalling/reinstalling networking and rebotting with the
same results.

I've tried stopping the AV service and quitting the app. No go. Same
result.

I've tried stopping the Network Ice service and quitting the app. No
go. Same result.

Port 110 still will not receive.

Now what? Will a system reinstall even work at this point? If I've
unin/rein all networking protocols what can a system reinstall
possibly do. Whatever the problem is the port in question is
somehow blocked since the pop.west/east.cox.net will not work. I can
send email just fine through the clients, but it won't receive.
One other thing. The email client works just fine for newsgroups. Can
send/receive no problem whatsoever.

Any other suggestions/comments?
Click to expand...

Is there a way to stop the download feature from timing out? It seems
like for whatever reason is making port 110 download mail so slowly, the
email client is timing out. Is there a way to stop this from occuring?
I'm using Outlook 2000 SP3 on a Win2k desktop.
 
Back
Top