Exchange resolves remotely but not locally - why
Posted on 2014-10-30
As part of an ongoing project that I have asked questions about before, I now have another even more obscure question.
I have an existing Exchange server set up in my office, all working perfectly, OWA, Outlook anywhere etc etc. the particular mail domain IP is ***.***.***.244
Clients in the office connect to this exchange box using outlook and all is fine.
I had a need to add another exchange server as we needed to be able to use another domain from the same outlook clients whilst keeping everything separate.
My idea therefore was to set the new exchange box up on a different domain with mail pointing to ***.****.***.246 and then use outlook anywhere to allow the workstations' outlook to connect, in effect giving each office user 2 totally separate e-mail accounts within the same outlook client - exactly what management wants.
I have hit a problem though - everything works perfectly when I use a laptop on a different internet connection to the office (in my house for example) but the moment I try and set it up on a computer on the office LAN it won't even resolve the mail server name.
I'm fairly sure that Exchange is set up correctly because it connects just fine when I'm not in the office - what else could be the problem?