Can't access the TS from inside using WAN IP or domain name

Q1: The client used to be able to access their TS from the LAN using registered
domain name. After they switched the ISP to Comcast and replaced the old
router with SMC router, they can't access the TS from inside using public
domain name or WAN IP. They can access the TS using the LAN IP and using
public IP work from outside works fine. You can ping the WAN IP or name from
the LAN but not telnet port 3389. Why?

A1: The nat/router must support something called "loopback" for this to work.

In some cases, a firmware upgrade may allow for this functionality. I'm not sure I've ever seen this listed on a spec sheet, so finding out before you buy is probably not easy.
 

A2: The router probably isn't doing loopback. They should have an internal dns zone matching their external one with internal IPs instead...

Q2: OK, I fixed this issue by adding internal IP and domain name to hosts. I am wondering if I can do that in the internal DNS instead of creating a hosts file on each computer.

Related Topics

What’s HOSTS file
Why do you need HOSTS file
How to use HOSTS file
HOSTS file Troubleshooting and restriction

Bob Lin Photography services

Real Estate Photography services