So I have an Exchange 2010 server at our main office and everything works great. All main works inside and out, with phones, OWA, etc. I don't currently have any MX records set, which is the recommended way MS says for internal mail. I do have MX records set at the ISP level.
I noticed an issue at one of our remote locations today though. All users connect back over a VPN to a terminal server so they just get their mail like the rest of us, or it looks that way to the network. But I had my phone with me connected via wifi there and it won't resolve to our mail server. So it seems like it has to do something with MX records over the VPN.
I am really confused by all of this because I would have thought that the request from my phone would just travel up the VPN and it would be treated as local, resolving using internal DNS. WTF is going on here? Any ideas?
By reading my posts you agree to my terms of service.
The remote location has is't own DC, which does DNS and DHCP and it has it's own IP scope, but it also talks to the DC here, so shouldn't it just forward that request?
I haven't tried pinging but I can connect to RDP sessions using IP and name over that wifi.
By reading my posts you agree to my terms of service.
It's getting too late for me to think, to be honest, but maybe an ACL stopping traffic to certain ports from going over the VPN? Is the local DNS record right for the mail server? I haven't played with DNS for a while so I can't remember the fine details.
