Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[arose10]

Hi.  I've been having occassional but frustrating issues sending messages from my e-mail accounts set up in Outlook 2003.  Both accounts are POP/SMTP.  The first account has incoming server port number 995 and outgoing server port number 465.  The second account has incoming server port number 110 and outgoing server port number 465.

I was told by someone that a potential solution to this problem could be setting up my DIR-655 router to allow e-mail client access through these ports.  Has anyone had success before using this method?  Where can I find instructions for doing this?  Are there any other potential causes and solutions?  Thanks in advance!


Alex

[Fatman]

This is all outbound traffic, I would look for SPI/Endpoint filtering drops or maybe ALG drops in your logs that correspond.  Failing that I would look at your WAN MTU.

[Clancy]

This is all outbound traffic, I would look for SPI/Endpoint filtering drops or maybe ALG drops in your logs that correspond.  Failing that I would look at your WAN MTU.

Since you have pinpointed this as being outbound traffic (how did you arrive at that conclusion? seriously, I want to know), then I would assume that a software Firewall would not need to be modified to allow outbound traffic, would it? McAfee Firewall controls just about every port and you have to manually open them if you think McAfee is resticting them. Would this be worth a look?

Finally: Fatman, you hypocrite. I think you are trying to solve a problem here. I'm so ashamed to know you.

[arose10]

I'm a little confused with some of the technical language being used.  Sorry.  But in case it helps, I have Norton Internet Security installed on my computer.  Let me know if I can provide any other information that will help derive solutions to my problem.

Thanks,
Alex

[Fatman]

 

how did you arrive at that conclusion? seriously, I want to know

Because POP and SMTP are both client/server architecture programs.  As he did not call it his server but his account I know the traffic is outbound from him.  Another big clue is the fact that he is trying to pull his mail, that implies outbound traffic.

I would assume that a software Firewall would not need to be modified to allow outbound traffic, would it? McAfee Firewall controls just about every port and you have to manually open them if you think McAfee is resticting them. Would this be worth a look?

That depends upon the firewall, they often seem the product of a million monkies on a million typewriters, and I haven't seen a copy of Hamlet come forth yet.

I'm a little confused with some of the technical language being used.  Sorry.  But in case it helps, I have Norton Internet Security installed on my computer.

Does your mail work with all security software disabled?  Do you have log entries corresponding to the failed traffic on your router?

help derive solutions to my problem.

And remember kids, never drink and derive, it isn't a calculus risk, it will put you inside the area of the earths curvature!

Finally: Fatman, you hypocrite. I think you are trying to solve a problem here. I'm so ashamed to know you.

Thats it, no Christmas card for you!

[arose10]

Based on a recommendation, I turned off both incoming and outgoing e-mail scanning, yet have still experienced this problem.  Should I change any of the other settings in Norton Internet Security?

I'm not sure how to pull log entries corresponding to the failed traffic on my router, but if you let me know how, I will do this and post.


Thanks,
Alex

[davevt31]

The email scanning won't effect the delivery of the mail, you need to check the firewall settings in NIS as it may be the one blocking.

[Clancy]

And remember kids, never drink and derive, it isn't a calculus risk, it will put you inside the area of the earths curvature!

fade in to crowd noise...........

Ladies and gentlemen I think I see....yes, yes I'm certain now, The Umpire just threw Fatman out of the game for that lame joke!!!!!

Well Fred, you could see it coming. The Ump can only take so much before he's going to ring you up.

And Fatman is furious. He's kicking dirt on the Umpire's shoes.

Fred, he might draw a suspension for that move.

fade out crowd noise...........

[Fatman]

If you log on to your router it should be under status->logs

[Fatman]

Talk about lame, I sense another 5 minute major coming from you Clancy, I just haven't figured out what penalties exist in fishing/beer curls.

[Fatman]

I received a PM from arose10 with his logs (due to security concerns).  Looking through the logs the only message I see relating to the traffic in question is a single drop of a packet with a destination port of 110 that was dropped as out of sequence.

Could you clear your logs and create a log that only encompasses 10 minutes of time and includes as many attempts to pull mail as you can make happen in that time?  So far I am not leaning towards the thought that our blocked traffic is going to be as simple as logged drops.

In the PM for that log include the IP of DNS name of all your e-mail servers please.

[arose10]

Thanks.  A couple questions...

1) You mention attempts to "pull mail," but the issues I'm having aren't with receiving mail but rather with sending.  Are you referring generically to send/receive attempts?

2) What is a log's PM?  How do I find and pull the IP of DNS name for my e-mail servers?


Alex

[Fatman]

1) You mention attempts to "pull mail," but the issues I'm having aren't with receiving mail but rather with sending.  Are you referring generically to send/receive attempts?

Yes I am.

2) What is a log's PM?  How do I find and pull the IP of DNS name for my e-mail servers?

I was referring to the P(rivate) M(essage) that includes the next log.  It should be a setting in outlook.

[Lycan]

Log in to the router, disable the SPI and set the NAT End point Filters to endpoint independent.

That should set you straight.

[Fatman]

That was already suggested, besides that is the primary thing his logs are being probed for is SPI errors.