Outlook 2003 cannot access Fully Qualified mail server names when behind Netgear router
We have an SBS 2003 system behind a Netgear DG834GT firewall. The SBS 2003 server, slightly unusually, runs a Microsoft POP server so that a certain user can collect his Exchange email via POP on his laptop using Outlook 2003 from both within the network (wirelessly via the Netgear) and outside the internal network, from home. The SBS server runs the local DHCP server, not the Netgear.
At home, the user connects to the POP server over the net, no problem.
At the office however, the connection from Outlook to the POP server (assume its called pop.company.com ) from his laptop fails. DNS resolves the name to the external public address for pop.company.com and when Outlook tries to connect it fails with a 0x800CCC0F error, connection to server interrupted . However if I replace the FQDN with the local IP of the SBS server, it works fine.
I tried setting up a static route inside the Netgear to point requests for the public IP back inside the LAN, but that didnt work.
What is the best way to fix this problem, to get the laptop to always look at the internal server IP when it resolves pop.company.com from inside the office?
At home, the user connects to the POP server over the net, no problem.
At the office however, the connection from Outlook to the POP server (assume its called pop.company.com ) from his laptop fails. DNS resolves the name to the external public address for pop.company.com and when Outlook tries to connect it fails with a 0x800CCC0F error, connection to server interrupted . However if I replace the FQDN with the local IP of the SBS server, it works fine.
I tried setting up a static route inside the Netgear to point requests for the public IP back inside the LAN, but that didnt work.
What is the best way to fix this problem, to get the laptop to always look at the internal server IP when it resolves pop.company.com from inside the office?
Forgot one thing...
As the server propably already is registered in DNS as server.company.com, you should create an alias (CNAME) instead of an extra host (A) record, and point the CNAME-record to the FQDN for the server. If creating extra A-records, you can get some confusing resolving errors when reverse lookup doesn't match (pop->IP->server).
As the server propably already is registered in DNS as server.company.com, you should create an alias (CNAME) instead of an extra host (A) record, and point the CNAME-record to the FQDN for the server. If creating extra A-records, you can get some confusing resolving errors when reverse lookup doesn't match (pop->IP->server).
ASKER
Thanks, I shall do that and let you know the result.
ASKER
Ok, I've had a look at DNS on the server and I am afraid I didn't get anywhere. I must be doing something wrong but I can't figure out what.
I put in "pop.company.com" as the alias name, I point that to the FQDN (which is our SBS server) e.g. server.company.local but when I ping "pop.company.com" I still get a reply from the external IP, not the internal IP
What am I doing wrong?
I put in "pop.company.com" as the alias name, I point that to the FQDN (which is our SBS server) e.g. server.company.local but when I ping "pop.company.com" I still get a reply from the external IP, not the internal IP
What am I doing wrong?
Hello actionco,
how are you configuring the pop3, via the pop3 connection manager on the sbs management console, or straight into the user's outlook?
the FQDN of your server (externally) is for example sbs.yourdomain.com or mail.yourdomain.com. the internal FQDN is server.yourcompany.local.
Here is a tutoruial on how to configure pop3 on sbs:
http://www.msexchange.org/tutorials/Configuring-Incoming-Outgoing-Email-Windows-Small-Business-Server-2003.html
but actually, you shouldn't use pop3 at all, you'd better switch to SMTP:
http://sbs.editme.com/Exchange > switching pop3 to SMTP.
Regards,
suppsaws
how are you configuring the pop3, via the pop3 connection manager on the sbs management console, or straight into the user's outlook?
the FQDN of your server (externally) is for example sbs.yourdomain.com or mail.yourdomain.com. the internal FQDN is server.yourcompany.local.
Here is a tutoruial on how to configure pop3 on sbs:
http://www.msexchange.org/tutorials/Configuring-Incoming-Outgoing-Email-Windows-Small-Business-Server-2003.html
but actually, you shouldn't use pop3 at all, you'd better switch to SMTP:
http://sbs.editme.com/Exchange > switching pop3 to SMTP.
Regards,
suppsaws
ASKER
Hi - I am not using the POP connection manager, because it isn't the server that is collecting POP email, it is the users laptop collecting it from the pop server running on the SBS box.
ok, that is really NOT the way to go.
If you want to use pop3 for your domain use the sbs pop3 connection manager or (and you better should) use full SMTP or you will get all sorts of trouble.
Don't forget this is SBS, not w2k3 server ... use the WIZARDS ... :p
why are you using a separate pop server on the sbs when the pop3 connection manager is there?
If you want to use pop3 for your domain use the sbs pop3 connection manager or (and you better should) use full SMTP or you will get all sorts of trouble.
Don't forget this is SBS, not w2k3 server ... use the WIZARDS ... :p
why are you using a separate pop server on the sbs when the pop3 connection manager is there?
ASKER
I know it is not the way to go but this is the way the owner of the company wants it configured . His laptop, his company :-)
The POP3 connection manager is for the SBS server to download email but this SBS server doesn't use POP3, it uses SMTP to receive email. We're using the POP server on the SBS box so that the laptop can connect using POP, we're not using the POP connector to get email to the server.
The POP3 connection manager is for the SBS server to download email but this SBS server doesn't use POP3, it uses SMTP to receive email. We're using the POP server on the SBS box so that the laptop can connect using POP, we're not using the POP connector to get email to the server.
Huh?
so you mean you are using full SMTP to receive mail, why are you trying to configure pop3 on the laptop then?
just use rpc over http to get his email if he is outside the company, not pop3 .... .
I really don't see the point using pop3 when you can use full smtp, please explain.
so you mean you are using full SMTP to receive mail, why are you trying to configure pop3 on the laptop then?
just use rpc over http to get his email if he is outside the company, not pop3 .... .
I really don't see the point using pop3 when you can use full smtp, please explain.
ASKER
We're using POP because that's what the owner wants on his laptop.
RPC over HTTP on his laptop won't work either, because when he inside the internal LAN he won't be able to reach the server - it's getting the external domain name to point to the server that is the issue you see.
RPC over HTTP on his laptop won't work either, because when he inside the internal LAN he won't be able to reach the server - it's getting the external domain name to point to the server that is the issue you see.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
ok, I can see the advantages in what you say. I will have a go when the laptop arrives at the office.
It's your job to persuade him to choose rpc over http instead of pop3 :-)
show him the advantages of both solutions, he should be easilly conviced but it stays a ... manager :p
they mostly don't care about the technical stuff , they don't have time to listen, things must only WORK :)
show him the advantages of both solutions, he should be easilly conviced but it stays a ... manager :p
they mostly don't care about the technical stuff , they don't have time to listen, things must only WORK :)
> I put in "pop.company.com" as the alias name, I point that to the FQDN (which is our SBS server) e.g. server.company.local but when I ping "pop.company.com" I still get a reply from the external IP, not the internal IP
Did you enter pop.company.com as the alias name and got pop.company.com.company.co
If having separated namespace for internal and external DNS and this is the only one single machine that shall be handled this way to have its external DNS-suffix accesible on the intranet, you can create a zone and name it as the FQDN for the machine (pop.company.com). Creae an alias without name and point it on the internal server-FQDN.
Did you enter pop.company.com as the alias name and got pop.company.com.company.co
If having separated namespace for internal and external DNS and this is the only one single machine that shall be handled this way to have its external DNS-suffix accesible on the intranet, you can create a zone and name it as the FQDN for the machine (pop.company.com). Creae an alias without name and point it on the internal server-FQDN.
ASKER
The owner hasn't been in the office with his laptop since last week so I have been unable to make any progress. I will post an update here as soon as I can.
henjoh09 is correct your issue is defintaly with dns.
On your DNS if your local domain is company.com you can create a new alias called pop and point it to the local IP of your pop server or a new host A record and point it to the servers IP Address.
If you domain is not company.com you will need to create a new forward dns zone called company.com and create a new host A record called pop and point it to the servers IP Address.
Ensure your open a command prompt and do a ipconfig /flushdns to remove just incase its still picking up the external IP Address. Also ensure the laptop is configure to point to your internal dns server.
On your DNS if your local domain is company.com you can create a new alias called pop and point it to the local IP of your pop server or a new host A record and point it to the servers IP Address.
If you domain is not company.com you will need to create a new forward dns zone called company.com and create a new host A record called pop and point it to the servers IP Address.
Ensure your open a command prompt and do a ipconfig /flushdns to remove just incase its still picking up the external IP Address. Also ensure the laptop is configure to point to your internal dns server.
If creating company.com on the internal server, you will hijack the external zone and nead to add all records into the zone instead of when creating the zone to be the whole FQDN for the server address.
ASKER
Thanks!
ASKER
Got the laptop connected using suppsaws suggestions....thanks to everyone else for their input as well.
Have the client to use DHCP to always get the correct DNS-settings independent if he connects internal or external.