IT_Service
asked on
Trouble connecting Exchang 2003 using POP3
I am having trouble connecting external clients to use POP3 on an Exchange 2003 server.
If I am internal, or connected over VPN, I can type the name of the incoming mail server as the internal name (ie mailsrvr.domain.local) and everything works with no problems. In this scenario, I am using mail.domain.com as the SMTP server.
If I try to connect an external client however, using this info:
POP3 server: mail.domain.com
SMTP Server: mail.domain.com
I get the following error from Outlook:
"Task 'mail.domain.com - Receiving' reported error (0x80042108) : 'Outlook is unable to connect to your incoming (POP3) email server. If you continue to receive this message, contact your server administrator or Internet service provider.'
We are using a hardware firewall (Linksys R0V42) and I have the following Access Rules configured:
Priority: 1
Policy Name: POP3
Enabled: Checked
Action: Allow
Service: POP3[110]
Interface: WAN1
Source: Any
Destination: Any
Time: Always
and
Priority: 2
Policy Name: SSL
Enabled: Checked
Action: Allow
Service: HTTPS[443]
Interface: WAN1
Source: Any
Destination: Any
Time: Always
The POP3 service is started and the default virtual server is configured for port 110.
I only have Basic authentication and Simple Authentication and Security Layer checked. Requires SSL is NOT checked - though I am using SSL for OWA and Active Sync.
Why else could I not be able to connect to the POP3 connector?
Thanks you!!
If I am internal, or connected over VPN, I can type the name of the incoming mail server as the internal name (ie mailsrvr.domain.local) and everything works with no problems. In this scenario, I am using mail.domain.com as the SMTP server.
If I try to connect an external client however, using this info:
POP3 server: mail.domain.com
SMTP Server: mail.domain.com
I get the following error from Outlook:
"Task 'mail.domain.com - Receiving' reported error (0x80042108) : 'Outlook is unable to connect to your incoming (POP3) email server. If you continue to receive this message, contact your server administrator or Internet service provider.'
We are using a hardware firewall (Linksys R0V42) and I have the following Access Rules configured:
Priority: 1
Policy Name: POP3
Enabled: Checked
Action: Allow
Service: POP3[110]
Interface: WAN1
Source: Any
Destination: Any
Time: Always
and
Priority: 2
Policy Name: SSL
Enabled: Checked
Action: Allow
Service: HTTPS[443]
Interface: WAN1
Source: Any
Destination: Any
Time: Always
The POP3 service is started and the default virtual server is configured for port 110.
I only have Basic authentication and Simple Authentication and Security Layer checked. Requires SSL is NOT checked - though I am using SSL for OWA and Active Sync.
Why else could I not be able to connect to the POP3 connector?
Thanks you!!
ASKER
Hello, thanks for the response.
These clients already have POP3 email configured on their remote systems for other account; their preferred connection method is to use POP3. Also, there is not a desire to keep their mail on the mail server. I use HTTP/RPC on other servers, but don't want to do so here.
Just noticed that using http://canyouseeme.org/ I cannot get to Port 110.
I can get a response from port 110 internally.
Not sure where my firewall config could be wrong here.
Any ideas?
thanks!
These clients already have POP3 email configured on their remote systems for other account; their preferred connection method is to use POP3. Also, there is not a desire to keep their mail on the mail server. I use HTTP/RPC on other servers, but don't want to do so here.
Just noticed that using http://canyouseeme.org/ I cannot get to Port 110.
I can get a response from port 110 internally.
Not sure where my firewall config could be wrong here.
Any ideas?
thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I could not connect over telnet either.
I did find the issue ... it was the firewall - port forwarding was missing.
thanks for the responses; i will divide up the points.
I did find the issue ... it was the firewall - port forwarding was missing.
thanks for the responses; i will divide up the points.
ASKER
Thanks for the advice and troubleshooting help!
http://www.lan-2-wan.com/SBS.htm#q5