Greetings,
Our mailserver currently works just fine, both internally and externally. If a client wishes to download their messages via POP3 their client simply checks mail.ourdomain.com. Internally, the clients simply check using outlook at mailserver.domain. That's just peachy.
However, now that we have salesmen using tablet PCs both in and out of the office, I thought it would be a good idea for the client to check for mail using the LAN connection when it was available. I (foolishly) assumed that since the client was looking at mail.ourdomain.com, when they were on the LAN and were using our DNS servers, mail.ourdomain.com would resolve to the mailserver as usual and be routed internally.
This is true, it does instantly resolve to our public IP address, but SMTP/POP3 connections are refused. Has anyone ever come across this before, or knows why they might be refused?
Much obliged for any assistance.
Russell.
Carlsberg don't run I.T. departments, but if they did they'd probably be more fun.
Our mailserver currently works just fine, both internally and externally. If a client wishes to download their messages via POP3 their client simply checks mail.ourdomain.com. Internally, the clients simply check using outlook at mailserver.domain. That's just peachy.
However, now that we have salesmen using tablet PCs both in and out of the office, I thought it would be a good idea for the client to check for mail using the LAN connection when it was available. I (foolishly) assumed that since the client was looking at mail.ourdomain.com, when they were on the LAN and were using our DNS servers, mail.ourdomain.com would resolve to the mailserver as usual and be routed internally.
This is true, it does instantly resolve to our public IP address, but SMTP/POP3 connections are refused. Has anyone ever come across this before, or knows why they might be refused?
Much obliged for any assistance.
Russell.
Carlsberg don't run I.T. departments, but if they did they'd probably be more fun.