Jump to content

Disco And Penalties


7 replies to this topic

#1 P

    Member

  • PipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 107 posts
  • LocationI bask in the fire, and look into the stars, Laughing

Posted 15 January 2018 - 09:12 AM

Tonight i have 3 occasions over the span of two hours
where i was kick from the server during a match
and unable to log back in
Told me to check if i have Internet Connection which i have
since i am able to talk to folks in discord and watch videos

Only to log back in with penalties
its rather disheartening
Is there something I'd missed
Or is there anything to prevent disco from happening? :(
the Disco, unable to log back in and tells me to check internet and then get the penalty
I feels like the game is screwing with me.
What should I do?

#2 Ch_R0me

    Member

  • PipPipPipPipPipPipPip
  • The Named
  • The Named
  • 613 posts
  • Twitter: Link
  • Twitch: Link
  • LocationIn DireStar with Heavy Naval PPC

Posted 15 January 2018 - 10:58 AM

Yeah, sometimes I get into this too as well.
PGI should give dispensation for these, until the connection is stable (at least).

What's your connection? Fiber? Mobile? Something else?

Try to launch "traceroute" to mwomercs.com, like me:

C:\Users\spyde>tracert mwomercs.com
Tracing route to mwomercs.com [192.99.109.143]
over a maximum of 30 hops:
  1	 1 ms	 1 ms	 1 ms  192.168.8.1
  2    30 ms    25 ms    21 ms  172.18.134.201
  3    36 ms    19 ms    19 ms  172.18.48.59
  4    32 ms    19 ms    17 ms  172.18.48.26
  5    38 ms    27 ms    29 ms  172.18.48.6
  6    36 ms    19 ms    26 ms  80.50.105.161
  7    37 ms    41 ms    26 ms  ols-r2.tpnet.pl [194.204.175.233]
  8    40 ms    28 ms    30 ms  be100-158.var-5-a9.pl.eu [213.186.32.176]
  9    71 ms    51 ms    66 ms  be100-1166.ams-1-a9.nl.eu [91.121.215.190]
10    63 ms    51 ms    64 ms  be104.rbx-g1-nc5.fr.eu [178.33.100.160]
11	 *	    *	    *	 Request timed out.
12   144 ms   130 ms   139 ms  vl1304.bhs-g1-a75.qc.ca [213.186.32.249]
13   147 ms   142 ms   133 ms  bhs-g5-a9.qc.ca [178.32.135.194]
14   161 ms   156 ms   194 ms  192.99.109.143
Trace complete.

Edited by ManganMan, 15 January 2018 - 10:58 AM.


#3 P

    Member

  • PipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 107 posts
  • LocationI bask in the fire, and look into the stars, Laughing

Posted 17 January 2018 - 12:11 AM

View PostManganMan, on 15 January 2018 - 10:58 AM, said:

Yeah, sometimes I get into this too as well.
PGI should give dispensation for these, until the connection is stable (at least).

What's your connection? Fiber? Mobile? Something else?

Try to launch "traceroute" to mwomercs.com, like me:

C:\Users\spyde>tracert mwomercs.com
Tracing route to mwomercs.com [192.99.109.143]
over a maximum of 30 hops:
  1	 1 ms	 1 ms	 1 ms  192.168.8.1
  2	30 ms	25 ms	21 ms  172.18.134.201
  3	36 ms	19 ms	19 ms  172.18.48.59
  4	32 ms	19 ms	17 ms  172.18.48.26
  5	38 ms	27 ms	29 ms  172.18.48.6
  6	36 ms	19 ms	26 ms  80.50.105.161
  7	37 ms	41 ms	26 ms  ols-r2.tpnet.pl [194.204.175.233]
  8	40 ms	28 ms	30 ms  be100-158.var-5-a9.pl.eu [213.186.32.176]
  9	71 ms	51 ms	66 ms  be100-1166.ams-1-a9.nl.eu [91.121.215.190]
10	63 ms	51 ms	64 ms  be104.rbx-g1-nc5.fr.eu [178.33.100.160]
11	 *		*		*	 Request timed out.
12   144 ms   130 ms   139 ms  vl1304.bhs-g1-a75.qc.ca [213.186.32.249]
13   147 ms   142 ms   133 ms  bhs-g5-a9.qc.ca [178.32.135.194]
14   161 ms   156 ms   194 ms  192.99.109.143
Trace complete.


alright will do
im running on Fibre
just had a hiccup few minutes ago giving me the penalties again
cant even access the mwomercs webpage as well Until now

#4 BTGbullseye

    Member

  • PipPipPipPipPipPipPipPip
  • The Solitary
  • The Solitary
  • 1,540 posts
  • LocationI'm still pissed about ATMs having a minimum range.

Posted 17 January 2018 - 12:17 AM

Sounds like your ISP or modem is at fault. Might even be that their hardware is having trouble. Depending on your traceroute, it might be time to give your ISP a call.

Edited by BTGbullseye, 17 January 2018 - 12:17 AM.


#5 Tarl Cabot

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Tai-sho
  • Tai-sho
  • 7,660 posts
  • LocationImperial City, Luthien - Draconis Combine

Posted 17 January 2018 - 04:19 AM

Your location and ISP?

Are all servers checked? When disc, do you recall which server you were on? The log in/patching will always be the NA server.

Generally though a disconnect will happen when your connection is dropped somewhere along the way. It could be on your immediate end, your ISP network, anywhere along, PGI ISP, or PGI network/server. The closer it gets to a PGI server the likelihood it effecting more than just one person, unless a subset of people are being channeled through a specific location (one of the jumps listed in your tracert)

https://mwomercs.com...-your-gameplay/

Again though, you need to identify the server being used during a combat drop. Are you DC at all when in mechlab/not in combat?

Edited by Tarl Cabot, 17 January 2018 - 04:28 AM.


#6 P

    Member

  • PipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 107 posts
  • LocationI bask in the fire, and look into the stars, Laughing

Posted 18 January 2018 - 01:45 PM

i dropped at the NA server while in combat
instead of the usual 250ms, i get 370+ms if i get to join back in 5 to 10 minutes later

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\System32>tracert mwomercs.com

Tracing route to mwomercs.com [192.99.109.143]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 20 ms 330 ms 21 ms 10.100.0.1
3 5 ms 8 ms 4 ms 58.71.241.78
4 55 ms 82 ms 159 ms 58.71.241.21
5 * * * Request timed out.
6 * * * Request timed out.
7 4 ms 3 ms 3 ms 172.22.144.134
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * 13 ms 12 ms ae-6.r21.sngpsi07.sg.bb.gin.ntt.net [129.250.3.51]
14 12 ms 12 ms 11 ms ae-2.r01.sngpsi07.sg.bb.gin.ntt.net [129.250.3.130]
15 14 ms 16 ms 18 ms ae-1.a01.sngpsi07.sg.bb.gin.ntt.net [129.250.2.240]
16 * 12 ms 12 ms ae-0.level3.sngpsi07.sg.bb.gin.ntt.net [129.250.8.46]
17 258 ms 258 ms 260 ms ae-1-3110.edge3.London1.Level3.net [4.69.140.198]
18 255 ms 255 ms 255 ms be100-102.ldn-1-a9.uk.eu [178.33.100.213]
19 314 ms 314 ms 314 ms be100-1295.nwk-1-a9.nj.us [192.99.146.127]
20 * * * Request timed out.
21 * * * Request timed out.
22 341 ms 341 ms 340 ms bhs-g5-a9.qc.ca [178.32.135.194]
23 339 ms 338 ms 338 ms 192.99.109.143

Trace complete.

i get these tho from the tracing
idk if its my provider or something

#7 General Solo

    Member

  • PipPipPipPipPipPipPipPipPip
  • Legendary Founder
  • 3,625 posts

Posted 19 January 2018 - 05:19 AM

Annoying
but not disabling

#8 BTGbullseye

    Member

  • PipPipPipPipPipPipPipPip
  • The Solitary
  • The Solitary
  • 1,540 posts
  • LocationI'm still pissed about ATMs having a minimum range.

Posted 19 January 2018 - 01:55 PM

Looks like the edge3.London hop is where you're getting issues... Looks like it's a switchover from your provider to another system. I'd say to contact your ISP, because you shouldn't be getting 250 average pings to the USA servers from that traceroute. (should be getting closer to 200)





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users