We have one computer out of 40 on our hq network that is having this problem:
We have a terminal server box accessible by internal ip (192.168.2.14) and external. On the problem machine, I CAN:
1. Go to the external ip in Internet Explorer;
2. Go to both the external and internal ip via Remote Desktop Connection.
What I can NOT do is resolve the internal ip address in Internet Explorer. Every other machine here is ok, and does not have this problem.