• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 498
  • Last Modified:

Can't get POP email on internal network using public domain name/ip as POP server

Hi,

I have an Exchange 2003 Server on Windows SBS 2003. Between my server and the internet is a DSL-504 D-Link router.

I have one user that refuses to connect to the network in any way but wants to POP email out of the exchange server. His computer is a laptop. When he is on the road and uses dial up internet, he can POP the mail out of the server (using mail.ourdomainname.com as the POP server. However when he is in the workshop (same network/subnet but not connected to the domain) he cannot receive mail on mail.ourdomainname.com and has to use the computer name or IP Address of the server to be able to get the mail. We are using ourdomainname.local for our internal domain.

We can obviously make it work by changing the POP server depending on whether he is internal/external to the local network, but It would be far better if he could collect his mail on mail.ourdomainname.com no matter where he is.

Thanks!  
0
PeteJH
Asked:
PeteJH
  • 4
  • 2
  • 2
1 Solution
 
ahmedbahgatCommented:
try to add a record to the hosts file, that represent the local server name with the equievlent IP address

cheers
0
 
ahmedbahgatCommented:
the records should be like this

192.x.x.x      mail.ourdomainname.com

cheers
0
 
PeteJHAuthor Commented:
I can see this working, but what happens when he takes his laptop away with him and wants to POP out his email over a dial up internet connection? Will it still try to find 192.168.0.1?
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
sr_millarCommented:
Peteh,

Are you running DNS on your LAN?  I aaume so.  You need to add a forward lookup zone in your DNS for ourdomain.com - you  probably only have your domain listed right now in DNS.

Then, in the new forward zone ourdomain.com, add a record called mail.  Now he will be able to use your local DNS to do the lookup, as will anyone else on your LAN.  

One point to note is if you are corporate website, www.ourdomain.com, is hosted by a 3rd party you will need to add a host to the new zone called www and add the ip address of the webserver so that internal network users can still resolve the domain name.

The above will work because when he is on the road he will use internet DNS to resolve mail.ourdomain.com, and your DNS when he is local.

Hope this helps.
0
 
PeteJHAuthor Commented:
Thanks very much for your help thus far.

I have created the new zone as discussed. It seems to be working a treat for any computer that is joined to the domain.
However this computer is not joined to the domain and is just another pc on the 192.168.0.x network. It connects straight away but gives the following error after a preiod of no activity: "Your server has unexpectedly terminated the connection ..... server problems, network problems, or a long period of inactivity ... etc"

Any ideas what this could be?
0
 
PeteJHAuthor Commented:
hang on....it might be working now....
0
 
PeteJHAuthor Commented:
Yep. Its working fine. Thankyou so much for your help.
0
 
sr_millarCommented:
no problem
0
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.

Join & Write a Comment

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 4
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now