Long time Outlook user struggling sending email

[Gregg A]

I've got (5) box's on my wired/wireless network. The machines all use
Outlook 2003 or the load from Office XP Pro. Three days ago none of the
box's would send email but still received fine. I assumed it to be another
failed NetGear wireless router (most machines are hard wired to it). I
replaced it today and no change. I just configured Outlook Express and it
works fine. Comcast is my ISP but my primary mail is from my business domain
e-mail server (startLogic). Both my comcast and domain mail server give me
the same error message "found the mail server but got no response" (or
something to that effect). I could sure use your help!

 

[Roady [MVP]]

If all your machines experience this at the same time in different
configurations, than I wouldn't directly think Outlook is your issue. What
changed since 3 days ago?

The error would indicate a firewall issue, another form of malware
protection failing, or a change at your ISP.

 

[N. Miller]

I've got (5) box's on my wired/wireless network. The machines all use
Outlook 2003 or the load from Office XP Pro. Three days ago none of the
box's would send email but still received fine. I assumed it to be another
failed NetGear wireless router (most machines are hard wired to it). I
replaced it today and no change. I just configured Outlook Express and it
works fine. Comcast is my ISP but my primary mail is from my business domain
e-mail server (startLogic). Both my comcast and domain mail server give me
the same error message "found the mail server but got no response" (or
something to that effect). I could sure use your help!

The exact, verbose error message is much better than a paraphrased guess.

Comcast has a habit of pushing port 25 blocks on customer modems when SMTP
activity exceeds a certain threshold. Try changing to use port 587, instead.