Forum Discussion

ChasR's avatar
ChasR
New Contributor II
2 years ago

The 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 erro...
ChasR's avatar
ChasR
New Contributor II

2 COX service men installed the Panoramic and left NO information on it.  I have not idea what Bridge Mode is.  It occurs when I am in COX E-Mail.  After a while it clears.

WiderMouthOpen's avatar
WiderMouthOpen
Esteemed Contributor
2 years ago

Does it only occur on the new Windows 10 PC? Also, check your TP-Link router's internet IP address as seen here. Make sure it isn't 192.168.x.x. Not that I think double NAT is causing this problem, but might be causing others.

  • ChasR's avatar
    ChasR
    New Contributor II
    2 years ago

    192.168.0.1 apply to both the Cox and Tp-Link. Of course this confuses them and I can't get in.

    • WiderMouthOpen's avatar
      WiderMouthOpen
      Esteemed Contributor
      2 years ago

      That's a problem. You should disconnect the TP-Link from the gateway and log into the TP-Link and change it's access IP. See here on how.

      • ChasR's avatar
        ChasR
        New Contributor II
        2 years ago

        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.