ChasR
New Contributor II
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: The connection to remote server 127.0.0.2 was refused or timed out while attempting to connect.
The COX modem died. When the Techs came they informed me I owned it and needed to get the Panoramic to replace it. Because my wife has Wireless to the Tp_link they somehow connected it to the Panoramic and she works fine. I will be gone this afternoon. Please keep the suggestions on how to access the COX and Tp-Link as well at the 127.0.0.2 issue coming.79Views0likes5CommentsRe: The connection to remote server 127.0.0.2 was refused or timed out while attempting to connect.
I checked and the TP-Link Router is 192.168.100.1. Trying to connect to this gets the message it took to long to connect. I believe this is the default address for most routers and could be causing a conflict.12Views0likes1CommentThe connection to remote server 127.0.0.2 was refused or timed out while attempting to connect.
This has been happening often. 2 things have changed. A Cox Panoramic Modem/Router as installed along with my wife's TP-Link wireless router. I also installed Windows 10 a few weeks ago. The error does not always occur, but to often.1.9KViews0likes21Commentsblocklist rule
I want to change the content of the blocklist rule to those addresses I have identified as BLOCKED. I get as far as edit rule and there is NOTHING I can specify in the CONTAINS option to point to the Blocked list. There were a list of addresses from years ago, but somehow they have now disappeared. The help does nothing and in fact points to E-MAIL which can't be found.585Views0likes2Comments