PS4 News on Facebook! PS4 News on Twitter! PS4 News on YouTube! PS4 News RSS Feed!


 
 
  1. #1
    Join Date
    Nov 2007
    Posts
    126

    [Answered] DNS Error 80710102

    I keep getting this error whenever I try to connect to the PlayStation Network:

    "An error occurred during communication with the server. This is a DNS error. (80710102)"

    Does anyone know what I can do to fix this? I went into the Cmd and did ipconfig/all to find the two DNS servers on my laptop. but it didn't work. I am currently using my university's connection in my dorm room, and it's plugged directly into the wall. Any help would be most appreciated!
    Best Answer - Posted by PS4 News:

    From the error code list: 80710102 - IP conflict, PS3 Cannot connect to the router with current IP information - Try rebooting your router.

    Not sure how accurate that is, but worth a try anyway.

  2. #2
    i used to get that error (or something very similar to it) back when i had simple dns running to spoof the firmware version on my ps3.

    Are you sure its not something as simple as your network settings on the ps3, because if you have a direct connection from your console to the wall its either that or something your uni admins have set up. Has this just recently happened?

    I cant really be of much more help.

  3. #3
    Join Date
    Nov 2007
    Posts
    126
    Well, I set everything to auto the first and third times around, and still no luck. It just keeps stopping on the Internet Connection test. I'm on the latest firmware, so I don't know what else to do about this. I will get in contact with the ISP, though...

  4. #4
    Join Date
    Apr 2005
    Posts
    30,331

    Lightbulb

    From the error code list: 80710102 - IP conflict, PS3 Cannot connect to the router with current IP information - Try rebooting your router.

    Not sure how accurate that is, but worth a try anyway.

  5. #5
    Join Date
    Nov 2007
    Posts
    126
    Yeah, I found out the solution. I just left it alone for a while, came back, and it worked. It could be due to overpopulation, network errors, etc. Just need to be on the latest firmware and just be patient. That's all.

 
Closed Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •