Unable to access www.wellsfargo.com

[Hubrisnxs]

cooper, are they able to reach other secure sites.

Banks are all https://

So there are situations where someone can't reach https:// sites, but can reach regular http sites

have them try to go to https://www.microsoft.com    see if they can get there, if they can, then you can rule out the https:// issue.

And if they still can't connect then try what was mentioned above, tell them to power down their Verizon routers over night, and in the am they will have a new IP and likely a new route. 

[Hubrisnxs]

209.200.144.35  belongs to prolix if you do an NS look up.

DNS query results(query type: "A") for a 209.200.144.35
	Name	TTL	Class	Type	Value	35.144.200.209.in-addr.arpa.	86400	IN	PTR	unknown.prolexic.com.

So that is the server in the traceroute giving you an issue? 

your customers would be a Verizon IP address.   so maybe have them go to www.whatismyip.com

[cooper20141]

He can get to other secure banking sites.  Will suggest power down router for 4 hours.

[cooper20141]

My customer received a new router and now can get to wellsfargo.com.  Maybe IP address from router was causing issue?  But he had a technician come out to his home previously and they had shut down router.  But maybe IP address was never flushed out?

[Hubrisnxs · Accepted solution]

that was likely it, it was never flushed out.  The Verizon network is quite large, if you don't leave it off long enough  then you usually get the same ip.  The four hour thing is a good way to garuntee that,. or you could release the IP (commands in the router interface) or calling vz tech support (they can do it remotely), and then the important part is to leave it dead no power no lights, no connection for at least 3, 4 5 minutes or more. 

[jamesm1]

Thank you for the suggestion to release the IP address and power down the router for 4 hours to ensure you receive a new, and not the same, IP address.

I have a FiOS user in NJ who was not able to access wellsfargo.com for 3 weeks.

User has been able to access any and all other sites, including other https sites.

Traceroute was similar to what has been posted, showing timeouts at prolexic.

Tried to access the wellsfargo server directly, using one of 3 IP addresses for that host, still no access.

The IP address before flushing was 100.8.X.X

My guess is that this IP address range is being blocked by Prolexic, on behalf of Wells Fargo, that their may have been DoS attacks launched from this IP address range.

[jakelee]

I just upgraded to FiOS from Verizon's ADSL , and have the 100.8.x.x IP address. I can't get to Wellsfargo.com and Wells Fargo's internet tech support denies they are blocking any address, and suggested me to flush the router (off for 4hrs). However this is not a real solution since I might get assigned the same IP range. 

Is there a better way? 

[smith6612]

---

@jakelee wrote:

I just upgraded to FiOS from Verizon's ADSL , and have the 100.8.x.x IP address. I can't get to Wellsfargo.com and Wells Fargo's internet tech support denies they are blocking any address, and suggested me to flush the router (off for 4hrs). However this is not a real solution since I might get assigned the same IP range. 

Is there a better way? 

---

It's ultimately a gamble. Turning off the router or Verizon force releasing the IP may just give you the same IP the next time the router goes to ask for one.

[epp1]

I also am in NJ and experiencing this problem which occurred suddenly a few months ago.  At that time I thought the issue might be some type of virus on my old computer.  Bought a brand new wireless desktop and issue continues.  If I log on through my work citrix server on the same computer I access immediately.  I will power down my modem overnight and hope that solves the problem, but if not, what can be done?  Quite frustrating.

[Hubrisnxs]

oddly, because this thread is so old you may have received an ip on the original poster's subnet that started the whole thing.

So if that doesn't work for you (which it should) then just rest assured that it will eventually self heal, but to continue using yoru vpn as a work around.  

the real fix is for WF to unblock these Verizon subnet's that cautght in their BOGON Filter list