On Thu, 15 May 2014 11:57:02 Nic Baxter wrote: > > 3. Able to authenticate as above if using ip number instead, which makes > > sense, since in office wifi and mail server on same subnet (192.168.1.X) > > Hi Daniel > I suggest this is not an issue with the server but with the client. > My suggestion would be to ping the mail server using the domain name and > see if it resolves. It might also be a good idea to run ipconfig /flushdns
It sounds like the DNS has the external IP address and the routers aren't setup to allow connections to the external address from inside the organisation. The best thing to do is to configure NAT on a router to redirect the external IP to the internal IP. It will be tempting to have separate internal and external views in the DNS, but don't do that, it causes lots of pain in the long term. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/ _______________________________________________ luv-main mailing list [email protected] http://lists.luv.asn.au/listinfo/luv-main
