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...
WiderMouthOpen's avatar
WiderMouthOpen
Esteemed Contributor
2 years ago

If you are using your own router, do you have the Panoramic gateway in bridge mode? Also, when do you get the error, when checking Cox Webmail?

  • WiderMouthOpen's avatar
    WiderMouthOpen
    Esteemed Contributor
    2 years ago

    Reminds me of this thread that is locked. If OP only gets the error with Cox Webmail there are probably problems with the servers. I would test mine but I don't use cox email. Can anyone test it?

    • Bruce's avatar
      Bruce
      Honored Contributor III
      2 years ago

      Me thinks it's probably a customized DNS entry on the Win10 device.

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

    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.