Discussion Locked

LAN Users, ISP mail accounts, and NAT

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We are behind a firewall which performs NAT. Some of our Users are trying to access email accounts hosted by other ISP's (using Outlook, not a Browser) and are unable to receive their mail. The suggestion was to add every possible IP# that they could go out to the Internet on into our DNS table as "A" records. Is this for real? Any other solutions? Thanks.

5 replies

by ewing bettles

DNS and NAT are not likely your problems. One possible cause of failure would be the Firewall blocking outbound POP3, IMAP4, or SMTP port requests (normally ports 110, 143, and 25, respectively). Another, more likely cause would actually exist with the external network. Many ISP's will only allow logons to their mail servers if the logon request originates from an IP Address that is "internal" to their operation - any external requests are refused.

Good luck, -Ewing

by stillatit

The reason for adding A records would be that the ISP does a DNS lookup on the mail client workstation. This is conceivable, but not likely. It is worth doing, however, because some anonymous FTP sites definately do this.

You need to have these users log on to their own ISP account and check the ISP home page for information about email setup:

Some ISP's restrict access to their incoming email (POP) servers to their own IP addresses.

Almost all ISP's restrict access to their outgoing email (SMTP) servers to avoid spammers using their servers to send out bulk mail.

Some ISP's require the use of secure logins.

If the information pages do not tell you, a call to the ISP's help desk should answer the question.

The reason for logging into the ISP is that some ISP's restrict access to members' information pages to their own IP addresses. (Roadrunner does this, for example.)

Good luck.

This discussion is closed to new replies.