Remote Access Email

[buena]

I am running a Windows NT server with Microsoft Exchange and RAS.
I have a handful of users that dial into the network remotely.

Users are able to dial in with no problem, but some have trouble accessing email.
Others have no problem at all.

The remote user’s accounts are POP3.

Has anyone experienced this problem?

 

[SjrH]

I've come across this numerous times and it's nearly always been a name resolution issue. If your using WINS, make sure the 046 WINS/NBT Node Type value is set to 0x8 in your DHCP scope. You could also add the Exchange servers IP address and name to both the HOSTS and LMHOSTS files on the clients.

SjrH - Data Security Storage & Availability Specialist

http://www.sjrh.co.uk

 

[buena]

What does adding the Exchange servers IP address and name to HOSTS and LMHOSTS files do?

Do they need this setup in order to access email and our network?

Will I need to also change the account type from POP3 to exchange?

 

[thelaffster]

buena,

What I see most often is that the POP3 accounts are trying to access the Exchange server from the external address of your MX record (ex: mail.myexchange.com = 209.94.220.31). I'm assuming that your exchange server is not in a DMZ but behind a firewall and has a private address. To make it so that they can use a POP3 account when connected locally, as they are when they are dialed-in, you need to setup a DNS entry on your local server that will resolve the IP address to the private address and NOT the external address (ex: mail.myexchange.com = 192.168.3.31). That way, when connecting externally, via the internet, the MX record provides the appropriate external IP address...but when internally connected your DNS will resolve the address to your local private network address.