jrjuiliano
MIS
Hi all,
I've got about three or four people running a POP3 account on a LAN with Outlook 2000, and no Exchange server.
DNS points to our regular server as network with forwarders to the outside world, all hinging on a Cisco 1720 router to get out of the local net.
Frequently I'll have one user get time out messages for the SMTP server when trying to send e-mail. Usually it's not everyone, but there are times when it happens to at least two persons.
Here's the deal though - If I run "pathping" from the command line and let it finish out everything, sometimes it connects to the server just fine. OR, if the user shuts down the computer and restarts, it will connect just fine.
I'm at a loss. I can only do connectivity tests so many times and get the same results, but still have Outlook not connect to the ISP's mail server. I've already set the time out to a minute-and-a-half, but that's pretty excessive!
Any ideas?
J.R. Juiliano
Information Systems Specialist
Tri-City Emergency Medical Group
I've got about three or four people running a POP3 account on a LAN with Outlook 2000, and no Exchange server.
DNS points to our regular server as network with forwarders to the outside world, all hinging on a Cisco 1720 router to get out of the local net.
Frequently I'll have one user get time out messages for the SMTP server when trying to send e-mail. Usually it's not everyone, but there are times when it happens to at least two persons.
Here's the deal though - If I run "pathping" from the command line and let it finish out everything, sometimes it connects to the server just fine. OR, if the user shuts down the computer and restarts, it will connect just fine.
I'm at a loss. I can only do connectivity tests so many times and get the same results, but still have Outlook not connect to the ISP's mail server. I've already set the time out to a minute-and-a-half, but that's pretty excessive!
Any ideas?
J.R. Juiliano
Information Systems Specialist
Tri-City Emergency Medical Group