![How to view your bill online. Get started How to view your bill online. Get started](https://forums.att.com/485/f8cd9c6d-aa02-496b-89c1-26239ac43063-1418546990.png)
New Member
•
7 Messages
AT&T Gateway Blocking Access to Regions Bank
I have been mystified by my problem for about 6 months now. A previously functioning app I use for my person finances, moneydance, will no longer connect to my bank, Regions. At first it was intermittent but in the last month or so it has become permanent. I find that when the app won't access the bank, it so happens that even my web browser won't access the website for regions.com. After much ado and attempts to resolve through the bank and through AT&T support, the bank denied any association with the issue and said it was an ISP issue. AT&T attempted a check of my system and could not find a problem.
I continued to research on my own and tried a proxy server to access the bank, successfully. So that pinpoints the issue to AT&T gateway not allowing access to the bank. I need help getting this block removed! I am copying the text from my command prompt window in which I did a ping to the regions.com site and I also did a tracert. Please refer to the following for evidence that it times out:
Microsoft Windows [Version 10.0.19041.867]
(c) 2020 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>ping -c www.regions.com
IP address must be specified.
C:\WINDOWS\system32>nslookup www.regions.com
Server: homeportal
Address: 2600:380:ec89:bb02::1
Non-authoritative answer:
Name: www.regions.com
Address: 205.255.103.100
C:\WINDOWS\system32>ping www.regions.com
Pinging www.regions.com [205.255.103.100] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 205.255.103.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\WINDOWS\system32>tracert www.regions.com
Tracing route to www.regions.com [205.255.103.100]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms homeportal [????????????]
2 4 ms 3 ms 2 ms 10.101.169.109
3 69 ms * 59 ms 172.21.211.82
4 * * * Request timed out.
5 61 ms 54 ms 56 ms 107.77.254.116
6 68 ms 61 ms 60 ms 12.83.186.186
7 77 ms 59 ms 73 ms 12.83.185.153
8 76 ms 67 ms 71 ms 12.122.28.125
9 79 ms 77 ms 67 ms attga402igs.ip.att.net [12.122.117.121]
10 72 ms 66 ms 75 ms 192.205.36.158
11 88 ms 72 ms 69 ms ae-6.r23.atlnga05.us.bb.gin.ntt.net [129.250.5.59]
12 103 ms 95 ms 93 ms ae-4.r25.asbnva02.us.bb.gin.ntt.net [129.250.4.165]
13 97 ms 85 ms 85 ms ae-1.a04.asbnva02.us.bb.gin.ntt.net [129.250.2.125]
14 90 ms 88 ms 85 ms ae-1.security-services.asbnva02.us.bb.gin.ntt.net [129.250.192.118]
15 * * * Request timed out.
16 94 ms 79 ms 92 ms 4.53.237.45
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.
C:\WINDOWS\system32>
C:\WINDOWS\system32>
JefferMC
ACE - Expert
•
36K Messages
3 years ago
Another Regions customer posted this AM about the same problem. I did a tracert to Regions.com at that time and mine looks pretty much identical to yours. I get from AT&T to NTT and thence to Level3 (4.53.237.45). And I can also get to regions.com from AT&T.
So AT&T is routing you to a peering/backbone provider and then the packets quit coming back after the second such provider. That indicates that AT&T is properly handling your packets and that the problem is further along.
It could be that there is something in Regions' network causing you issues. I just read a post this afternoon from a customer who had been having issues with Bank5 caused by Bank5 identifying his AT&T IP address as being suspect. Bank5 addressed the issue and now he can access them. Regions may be doing the same to you.
Have you contacted Regions about this?
0
0
wheezerjoe
New Member
•
7 Messages
3 years ago
I have contacted Regions but they don't seem sophisticated enough about routing to be able to address it. I don't know where to turn.
0
JefferMC
ACE - Expert
•
36K Messages
3 years ago
I really don't think this is a routing issue per se, but it is a technical issue that first tier customer service at the bank isn't equipment to handle, even customer service for online issues.
Are you a Fixed Wireless customer?
0
0
wheezerjoe
New Member
•
7 Messages
3 years ago
Yes, I am a fixed wireless customer.
0
0
JefferMC
ACE - Expert
•
36K Messages
3 years ago
I thought so (based on the fact the IPs past your gateway were 10.x.x.x, which means they were in AT&T's CNAT). The other customer is fiber, so you do not have that in common. Your public IP (what the bank sees) will be essentially the same as a lot of other Fixed Wireless (and maybe wireless) AT&T Customers, because of the CNAT.
When you attempt to connect to the website with a browser, what error do you get?
0
0
wheezerjoe
New Member
•
7 Messages
3 years ago
"The connection has timed out"
0
0
JefferMC
ACE - Expert
•
36K Messages
3 years ago
At this point, I don't know what else to tell you. It could be a routing problem in Level3. It could be an issue inside Regions, either a network or server security configuration blocking you based on your IP address or something else.
0
0
wheezerjoe
New Member
•
7 Messages
3 years ago
I can get there using a proxy server but the proxy server I picked (from Auburn University) is blocked by some other sites. Do you suppose that another customer whose IP address is seen the same as mine has caused the blockage? It was intermittent until a month or so ago, no it is always unreachable.
0
0
wheezerjoe
New Member
•
7 Messages
3 years ago
*now it is always unreachable.
0
0
JefferMC
ACE - Expert
•
36K Messages
3 years ago
The older intermittent issue may have nothing to do with the current hard issue, or they could be related. It's so hard to tell.
0