Done Unable to connect to server

This started yesterday (~ 17 hours ago), I was connected to the server, the server restarted, then I was unable to connect to the server once it had come back online.

I managed to connect to the server this morning (~4 hours ago), but now I've been locked out again.

Any messages I'm getting are inconsistent, currently it's just sitting on "Logging in", which it has been for ~10 minutes or so.

Other error messages I've gotten are Time Outs as well as Forced Disconnects.
I only have a log file for the current issue, but if I can get log files for the other problems I'll upload them separately.

I'm also attempting to connect to another server (In this case, Regrowth), but it's having problems updating, and is currently stuck on "Reading package manifest" (It just started to update, but that took a while), so I can't determine if the problem is specifically with Ozone, or with my connection to MYM in general.

I'll add my response with any further information as I can get it.

 

Ok, another connect attempt gave me the Forced Disconnect error ("An existing connection was forcibly closed by the remote host")
Attaching log file for that as well.[DOUBLEPOST=1454809673,1454727870][/DOUBLEPOST]No problem connecting to Regrowth.
It seems that when the server restarts I'm unable to reconnect for some time.

... It actually seems that connecting to Regrowth allowed me to connect to Ozone. Will test again next restart.

 

Best solutions that I can see are (just some trouble shooting stuff):

• Change mini map you are using,
• Hard-force update the pack,
• Update version of java

 

@Ash00182 Thanks, I don't know which it was but I tried all three and it seems to have remedied the situation.

Weird that it would happen like that, but anyway, glad it is fixed.

Thanks again.[DOUBLEPOST=1454840734,1454828974][/DOUBLEPOST]@Ash00182 Ok, so it DID fix it, and it lasted a restart.... but now the issue has occurred again.
It seems strange that I can connect to a server once, then it refuses the connection afterwards.

I've either been getting endless "Logging in..." or actual Time Outs, and honestly the problem is likely just due to the fact I'm on the other side of the world, and the connection goes the longest way it can (Australia -> USA -> Germany).

Attached is the tracert command output.

I did mark this thread as done (as the problem appeared to have gone), but any other suggestions would be great.
I just find it really strange that I can connect, then be unable to connect after a server restart...

 

Seems you might be only able to connect at certain times of the day when the traffic is low. Possibly trying to re-route the connection more directly to Germany rather than going via the US would be optimal.

 

I gotta ask, do you know how to do that?

I'm not sure exactly how much control I have over the path my packets take, but if you know of a way to make it do so, I'd be glad to hear

 

That's what I thought.
I've also found out my ISP had a fibre cable have a run in with a submarine, and it in combination with everything else with them, I've dropped them and now everything is better.

My appologises