Unexpectedly Disconnected...

[CaptainElizabeth]

Ok, so I play POTCO pretty much everyday, & literally every 10 minutes of being on the game I will loose "connecton to the servers". It's sooo annoying. My internet connection on my computer is perfectly fine and has a great signal, and its not wireless, so thats not the issue. I've also already restarted my computer many times. I just have no idea on how to make it quit doing this. I'm getting fed up. lol Please Help!
Thanks!

♥ - Captain Elizabeth

[Chris Ironhawk]

Ahoy Elizabeth!

I'm sorry that this has been happening to you.

In order to fix this, you must first access your router's control page by going to the address 192.168.1.1. You must then log in. If you are using a Linksys router, there is no username, and the password is "admin" If you have anything other than that (Cisco, Fios, etc.) the login information should have been supplied for you somewhere.

Once you are into the settings page, you should be in the "Basic Setup" page. Look for the field that says "MTU." Once you have found that, switch it from "Auto" to "Manual." You must then type in "900" in the field that originally said "1500." Go to the bottom, and push "Save Settings." This should fix the problem. It worked for me.

Fair winds,
~Chris Ironhawk

[titanic95594]

Could have helped me if I knew the routers log in and Chris I think you do better then what the tech support for POTCO. I remember getting disconnected 3 times in 10 mins yesterday.

[isnear]

Elizabeth,

It happened to me many many times and I called it in, wrote a report, sent in my logs.

I don't have a router... and yes, they tried to cry FIREWALL FIREWALL but I don't have one (I am on a Mac). So the problem is NOT with your firewall... it is a problem that cropped up with their latest update and they, as usual, try to blame the users.

It didn't happen to me on my last session, so they may have found their error... so please post here if you are still experiencing the problem.

My theory was they left a secure socket layer active AFTER the launching process which caused all sorts of timing problems. I think they found it after I flagged that issue for them in my email, so let us know if your problem went away. I think mine did.