Need help with your equipment?
velocedge's profile

Teacher

 • 

12 Messages

Tuesday, April 5th, 2016 10:02 PM

Port forwarding not working on 2-wire

I followed the instructions in http://www.att.com/esupport/article.html#!/u-verse-high-speed-internet/KM1010270 and set up a computer with a web server on port 8090.  If I enter http://192.168.1.21:8090 the web page displays inside the LAN.

 

I created an entry for the user defined application which included that port in the from and to fields.  Then I selected the specific IP for the web server and applied that user defined application to it.  

 

If I go to the status tab, I see 192.168.1.21 tcp 8090 and the public IP.  However, if I go to a browser and enter http://mypublicip:8090 it just times out... why??

Community Support

 • 

6.7K Messages

8 years ago

Hi,

 

We apologize about the issues you are having with your services, but we will be glad to help. You can try to do a trace route to see if the packet is making it to your gateway. From there, the best thing to use is a packet tracing program like wireshark to see if the packet is making it to your computer. If it is, and there is no response, check for firewalls on your computer.

 

Hope this helps.

 

-ATTU-verseCare

Teacher

 • 

12 Messages

8 years ago

It doesn't appear to get back to my router.  Here are a couple of tracert's from external servers.  The computer I'm trying to reach at 192.168.1.21:8090 doesn't have a firewall installed.

 

Tracing route to 99-82-247-xx.lightspeed.livnmi.sbcglobal.net [99.82.247.xx]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ip-173-201-33-251.ip.secureserver.net [173.201.33.251]
2 <1 ms <1 ms <1 ms ip-208-109-113-141.ip.secureserver.net [208.109.113.141]
3 1 ms 1 ms <1 ms ip-208-109-113-173.ip.secureserver.net [208.109.113.173]
4 2 ms 2 ms 2 ms ip-184-168-5-77.ip.secureserver.net [184.168.5.77]
5 2 ms 2 ms 2 ms ip-184-168-5-77.ip.secureserver.net [184.168.5.77]
6 11 ms 11 ms 11 ms ae57.bar1.Phoenix1.Level3.net [4.16.137.145]
7 14 ms 15 ms 14 ms ae-207-3607.bar2.Tustin1.Level3.net [4.69.158.122]
8 15 ms 14 ms 15 ms ae-207-3607.bar2.Tustin1.Level3.net [4.69.158.122]
9 16 ms 15 ms 15 ms 192.205.37.145
10 58 ms 59 ms 59 ms cr1.la2ca.ip.att.net [12.122.128.102]
11 59 ms 58 ms 58 ms cr1.slkut.ip.att.net [12.122.30.29]
12 62 ms 59 ms 60 ms cr2.dvmco.ip.att.net [12.122.30.26]
13 * * * Request timed out.
14 57 ms 59 ms 59 ms 12.122.99.26
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

 

Tracing route to 99-82-247-xx.lightspeed.livnmi.sbcglobal.net [99.82.247.xx]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.100.1
2 <1 ms <1 ms <1 ms joltage.com [209.10.104.2]
3 <1 ms <1 ms <1 ms te0-1-0-0.core1.suw1.qualitytech.com [204.193.132.21]
4 1 ms <1 ms <1 ms te0-0-0-1.core2.suw1.qualitytech.com [204.193.132.6]
5 2 ms 3 ms 2 ms xe-0-1-0-19.r03.atlnga05.us.bb.gin.ntt.net [204.2.241.53]
6 2 ms 1 ms 1 ms ae-3.r04.atlnga05.us.bb.gin.ntt.net [129.250.5.205]
7 5 ms 5 ms 2 ms 192.205.36.157
8 42 ms 44 ms 41 ms cr1.attga.ip.att.net [12.122.141.234]
9 45 ms 41 ms 43 ms cr2.nsvtn.ip.att.net [12.122.2.6]
10 * * * Request timed out.
11 45 ms 46 ms 43 ms 12.123.150.50
12 * * * Request timed out.
13 43 ms 43 ms 42 ms 75.26.64.215
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Community Support

 • 

6.7K Messages

8 years ago

Hi,

 

Although the trace route does not always show the full path, since some routers do block/drop the trace route packet requests, it could possibly be an issue with the route. Since it is happening on 2 different servers and 2 different paths, it is hard to believe, but possible. Are you seeing any packet requests coming from these IPs when you check wireshark or the router logs?

 

-ATTU-verseCare

ACE - Expert

 • 

34.4K Messages

8 years ago

Are you trying the public IP address from inside or outside your LAN?  It will not work from insider, because the U-verse Gateways do not support NAT loopback.  Have you tried it from a mobile phone on your carrier network or from somewhere else outside your network?

 

Teacher

 • 

12 Messages

8 years ago

As I said in the earlier post, both servers are external to the LAN.  One from a server hosted at GoDaddy and the other hosted at QualityTech.

 

I haven't had a chance to check wireshark but will and let you all know.

Teacher

 • 

12 Messages

8 years ago

I really don't know what happened but I went back to the QTS server to close the tracert window and thought I'd just try the web address again and it worked!!  I have no idea why since I haven't touched the router since we've been posing.

 

Wish I had better feedback but I'm at a bit of a loss myself right now...

 

Anyway, thanks a ton for the responses... maybe next time!  😉

Not finding what you're looking for?
New to AT&T Community?
New to the AT&T Community? Start by visiting the Community How-To.
New to the AT&T Community?
Visit the Community How-To.