Cannot send outgoing mail in Outlook 2003, XP

I am having this same problem as Kevotron:
to reiterate: All Outlook users functioning fine except one.
This user cannot SEND mail but can RECEIVE mail.
Outlook settings are correct (incoming/outgoing POP3, account name/password, authentication, etc.)
When I try to TEST ACCOUNT SETTINGS the error states a network error/cannot connect to the Internet - however, the user can browse, ping known sites (i.e, et. al.)  This machine can ping the servers and other workstations.
TCP/IP is the only protocol and it uses DHCP for IP and DNS.

It suddenly happened - I didn't do anything or change anything.

I have tried everything...all of the suggestions above. I can receive mail just fine but cannot send mail. My server requires authentication and I have that box checked. I've tried "use same setting as incoming" and putting in the user password.

Also, when I send an email and it's waiting in my outbox, a constant popup appears that asks me to "enter network password". Everything is filled in except the box to check to save the password. If I click OK or cancel, it keep coming back.

Any suggestions?
Who is Participating?
If you have Norton Internet Security or McAfee Security Center you may have to disable the Anti-spam or Spam killer respectively. To determine if the problem has anything to do with the Norton Internet Security or McAfee Security, locate the little icon at the bottom right near your time; right click on it and click disable.

Make sure you have Outlook closed while performing the above.

Open Microsoft Outlook, move any email in the Outbox to the Drafts folder. To do this, right click each email in the Outbox. A context menu will appear over it, click Move to Folder. Select the Drafts folder and click OK.

Create a simple email to send, with somthing like "test01" in the subject and "test" in the body. Click send.

Please relate the exact error message you recieve, even if it is the same as before; so I can properly help you.
Ron MalmsteadInformation Services ManagerCommented:
Try re-joining the computer to the domain.  Or uninstall outlook and re-install or detect and repair.

Sounds like an authentication or dns problem though.
I’m a web application developer of a small company. My company is going to host our own web application in recent months (which we’ve never done before), we are concerning about the security issues that might arise when we have our own website up and running. We do have a network administrator; since his previous title was CEO he has little knowledge in networking. (No offense to CEOs, but he outsource basic tasks like setting up VPN, configuring firewall, and installing exchange server to an outside helper for $75/hr -- on company’s bills.)

So, instead of relying on our network admin, I have to start learning about network security. Here’s some basic info:

What we currently have:
1. T1 line -> router -> pix firewall -> 1 PDC, 6 servers, 50 user desktops
2. No segmentation or DMZ to separate the web server from the current network.
3. The web server is a Windows 2003 Server w/ IIS 6 and SQL Server 2000
1. Since we’re a small company, price does matter. We are talking about a budget around $2,500.
2. No skillful network person who can implement anything that is complicated or difficult.

What we have done to protect web server:
1. Secured the web application to prevent SQL injection and XSS attack
2. Encrypted passwords and cookies
3. Run Microsoft Baseline Security Analyzer and fixed all critical problems.
4. Installed latest security updates and service packs for Window Server and SQL Server.

I would like to get suggestions on the following issues for the web server:
1. Sources to find basic network solutions: books, websites, etc.
2. Simple ways to separate web server from the rest of the network
3. Intrusion detection and prevention
4. Antivirus
5. Any other security issues that I’m not aware of

On-Demand: Securing Your Wi-Fi for Summer Travel

Traveling this summer?Check out our on-demand webinar to learn about the importance of Wi-Fi security and 3 easy measures you can start taking immediately to protect your private data while using public Wi-Fi. Follow us today to learn more!

sorry, previous comment posted at mistake.
Check any firewall settings (ports 110 and 25 should be open for outlook). 445 might also need opening.
we should first try to find out if its a user-based or a computer-based problem. try the following:

on that computer do

telnet <smtpservername_as_configured_in_outlook> 25

do you get a connection or just an error message ?

if you create a new user on that computer, or login as another user if you are in a domain and configure outlook for that user, does it work ?
A word about sending mail.

First, you must use the proper Auth Dialect.  Usually CHAP works.  This will show up in an Ethereal capture if you have Ethereal.

There are other issues.  Do you have a FQDN using your own smtp server?  If so, and outgoing requires Auth, Exchange must auth to that smtp server correctly.

Please provide more information on your network and domain setup.
larenjansenAuthor Commented:
thanks - i think this worked...Laren
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.