Something blocking login

IBMJunkman

Senior member
May 7, 2015
926
402
136
Neighbor has an account on acorn.tv. For what ever reason he could not login. Tried the reset password procedure. Still could not login. So I went over. I went through new password procedure very carefully. Still could not login. Gets a message about userid and password not matching and an error: code BB

Tried on his laptop and desktop. Tried on his wife's laptop. Tried on my iPad with their wifi. All failed. Tried on my iPad with the cellular connection and it worked. Reset their router and cable modem. Still no joy. Tried on my iPad back home with my wifi and it worked great.

He changed the password stored in his Roku (wifi) to the new one and it worked fine.

There appears to be something about his WAN ip or LAN causing a problem. His internet is supplied by Charter.

Ideas?
 

JackMDS

Elite Member
Super Moderator
Oct 25, 1999
29,552
429
126
You spent two paragraphs on stories, then out of the blue you bring in Roku.

Better spend some time on technically describing the topography of the Network.


:cool:
 

IBMJunkman

Senior member
May 7, 2015
926
402
136
The problem is not the Roku device. It seems to work, even with the new password for acorn.tv. But not being able to login into the acorn.tv web site means you can't change billing info or even cancel your account. That is the problem.

Network is as simple as you get. Coax into Charter DOSCIS modem. Ethernet out to a Linksys wifi router. Overall network config has not changed since setup years ago. Router gets IP from WAN. PCs get IP from router. Standard 192.168.x.x.

The problem is why can't this network be used to login into acorn.tv? They can log into all their other websites.
 

Fardringle

Diamond Member
Oct 23, 2000
9,200
765
126
It's possible that the site has blacklisted their WAN IP address for some reason, since the account works in other locations.
 

IBMJunkman

Senior member
May 7, 2015
926
402
136
It appears it was a temp blacklist. He logged in this morning and all was fine. A better error message would have been nice. Case closed. :)