Sites run off of server within network are slow or non-responsive from within network - fine from outside

The issue is that your device sees the public address and gives it to the Gateway.

The Gateway sees the public address and doesn't know what to do with it because it didn't come in the WAN interface.

You can get your own router that has NAT Loopback support (which means that it recognizes its own WAN IP coming from the LAN and loops it back through the WAN interface processing any port forwarding rules) and install it in combination with the AT&T Gateway.  

Or you can use local host naming to redirect the traffic to the local IP address (e.g. on Windows, edit the C:\windows\system32\drivers\etc\hosts. file to contain your local IP address and your DDNS name).  You'd have to do this on each client, because you cannot change the DNS hosts given out by the Gateway's DHCP.

Hi there @AlexApple , We are here to help with the NAT loopback.

For starters, thank you so much for your recent switch to AT&T! We are happy to have you, and invite you to look into SmartHome Manager App, for more detailed look at your network.

Of course I agree with our amazing Ace @JefferMC , we will need a little more detail to fully assist you.

1. What Router do you have with us? Each setup is different.
2. How is the performance with other websites, is it only your sites being impacted? 

Let us know if you need further assistance. 

Megan, AT&T Community Specialist

Megan, I have the BGW320 as the router. Other websites (google, youtube, twitter, etc...) all load just fine.

I did a little playing around last night and found a very weird thing.

Originally, I had the server, my gaming PC, and a switch hard wired to the router. The switch then ran a line to the other side of the house to power my NAS.  I noticed that when I jumped on the server and did a "ipconfig /all" that the server was not given an internal ipv4 address (one that begins with 192.168). 

I moved some lines around and now my current setup is this:

Gaming PC and switch are hard-wired to the router. The switch still has the line that runs to the other side of the house, but now also has two lines that run to the server (the server has two NICs).  NIC #1 still does not get an internal ip address. NIC #2 does get an internal IP.  I went into the router config and made it so the server will always get the same internal IP address (192.168.1.70). 

I'm still unable to get the pages to load locally, however.  I'd really love to resolve this issue as one of my sites makes internal calls to itself to kick off some data processing. These calls are currently failing and my data is becoming out of date.

See my earlier post.  Despite what Megan said above, we really don't need more information in order to help you, and I don't think that Smart Home Manager will tell you anything you don't already know.

I'm surprised that the public address works at all (even slowly) locally.  

@AlexApple,

Just like @JefferMC stated, our routers do not support NAT loopback. However, you do have the option of getting a 3rd Party Router that supports NAT loopback, and connecting it to our router. 

We have an article on the Community Forums labelled Bridge-mode vs IP Pass-through - Setup Information that will assist you with this.

Let us know if you have any further questions!

Donovan, AT&T Community Specialist