Jump to content

Remote Name Could Not Be Resolved


1 reply to this topic

#1 Anton Hallis

    Member

  • Pip
  • 11 posts

Posted 01 November 2017 - 01:05 AM

SInce I updated the portal I've been getting the error:

The remote name could note be resolved:
'patcher.mwomercs.com'.

I tried restarting the computer but that didn't work.

Only thing that fixes it is if I uninstall the portal and reinstall.

Then after I play, the issue recurs he next day.

#2 knight-of-ni

    Member

  • PipPipPipPipPipPipPipPip
  • Overlord
  • Overlord
  • 1,627 posts
  • Location/dev/null

Posted 01 November 2017 - 05:11 AM

Looks like a DNS name resolution error.

Do an nslookup from from the command line like so:
$ nslookup patcher.mwomercs.com
Server:        192.168.178.13
Address:    192.168.178.13#53

Non-authoritative answer:
patcher.mwomercs.com    canonical name = patcher.mwomercs.com.edgesuite.net.
patcher.mwomercs.com.edgesuite.net    canonical name = a1982.d.akamai.net.
Name:    a1982.d.akamai.net
Address: 184.51.114.121
Name:    a1982.d.akamai.net
Address: 184.51.114.144


My default dns server at the moment is 192.168.178.13, but yours will be different.

If you get an error, then try the lookup again against Google's dns server, or another known-good dns server:

$ nslookup patcher.mwomercs.com 8.8.8.8
Server:        8.8.8.8
Address:    8.8.8.8#53

Non-authoritative answer:
patcher.mwomercs.com    canonical name = patcher.mwomercs.com.edgesuite.net.
patcher.mwomercs.com.edgesuite.net    canonical name = a1982.d.akamai.net.
Name:    a1982.d.akamai.net
Address: 184.51.114.144
Name:    a1982.d.akamai.net
Address: 184.51.114.121


If the first attempt fails, but the second succeeds then you should consider configuring your tcpip settings to use a DNS server other than the one you are currently using.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users