Jump to content

Unable to login


Recommended Posts

So, all 3 my laptops use to connect fine until about a day or two ago now, been having dropouts, unable to login attempts etc. I am noticing the latency between myself and the server is rather right. And have also been running some tracert. See a problem as one or two hops hit in the 400-600ms range.

Right now I was able to get connected on on laptop via VPN to West Coast US. The other laptop after about 20 attempts and reloading the launcher finally passed the proxy login and let me in game. 3rd laptop no join 30+ attempts...

Wonder if any SDEVs feel like going thru the ropes with this (Even teamspeak is hit or miss right now!).

Now here is the funny part... This is only pertaining to anything NET-7 Related. I can view other websites, torrents, etc just fine and dandy including other TS servers. So I assume its something in my region the cause between ISP and Server, but Im wondering if there might be some magic we can put our heads together with on this.

Anyways looking for some SDEVs Tienbau/CDel/whomever wants to take a jump and answer some tech questions with me in private.
Link to comment
Share on other sites

Well a little bit of testing... Has to do with ISP routing of some sorts... Because I can fire up a VPN to Hong Kong/US (East/West Coast) and game loads up fine (albeit a lil more latency now)... But now can only do one connection at a time... UGH hate when I cannot fix something I know how but cant because dont have means to lol!
Link to comment
Share on other sites

Crap looks like they fixed it for now. Yesterday was taking 20-30hops to reach play.net-7.org and once it hit like hop 9/11 (heh coincidence!) it started taking a nose dive till last hop(I dont have the printout. As I assumed it was the ISP because this morning its now only taking 19 total hops to reach play.net-7.org and I can connect fine.

Still have a lil higher latency than would like but I can't do much about that. bout 300-400ms ping range (which was normal before I had connectivity issues. Stupid ISP here just cuz it has 100MB up and down it wants to use an inefficient route lol like 19 hops vs the 9hops with VPN to Hong Kong active lol... Gah oh well.

I guess I was wondering if the servers have some sort of threshold/response expectancy to timeout which I would expect does in regards to errors I got. Just wondering if that's tweakable and if it has any side effects in doing so.

Anyways just me poking finger at places that prevent me my EnB fix you know how it goes lol...
Link to comment
Share on other sites

Here are the current tracerts. Albeit its all working hunky dory now but not the best route if you ask me lol but my EnB Fix is underway!

C:\>tracert play.net-7.org

Tracing route to play.net-7.org [87.106.15.67]
over a maximum of 30 hops:

1 9 ms 1 ms 12 ms DD-WRT [192.168.11.1]
2 7 ms 1 ms 1 ms 218.236.38.1
3 3 ms 1 ms 2 ms 118.220.9.65
4 98 ms 242 ms 3 ms 58.229.31.185
5 4 ms 2 ms 2 ms 58.229.31.117
6 2 ms 2 ms 3 ms 58.229.28.9
7 3 ms 13 ms 15 ms 211.117.1.197
8 2 ms 2 ms 2 ms 118.221.7.46
9 167 ms 168 ms 173 ms 58.229.15.90
10 189 ms 165 ms 171 ms ge11-1-5d0.mcr1.fremont-ca.us.xo.net [216.55.28.17]
11 234 ms 240 ms 235 ms vb1500.rar3.sanjose-ca.us.xo.net [216.156.0.137]
12 233 ms 234 ms 234 ms te-2-0-0.rar3.washington-dc.us.xo.net [207.88.12.70]
13 235 ms 234 ms 238 ms te-3-0-0.rar3.nyc-ny.us.xo.net [207.88.12.73]
14 352 ms 311 ms 311 ms ae0d0.cir1.london2-eng.uk.xo.net [207.88.13.201]
15 376 ms 377 ms 376 ms linx.bb-c.the.lon.gb.oneandone.net [195.66.224.98]
16 390 ms 390 ms 396 ms te-1-3.bb-c.bap.rhr.de.oneandone.net [212.227.120.49]
17 327 ms 325 ms 326 ms ae-10.gw-distp-a.bad.oneandone.net [212.227.121.165]
18 390 ms 391 ms 391 ms ae-1.gw-prtr-r231-a.bad.oneandone.net [195.20.247.50]
19 326 ms 325 ms 326 ms play.net-7.org [87.106.15.67]

Trace complete.



THIS IS THE TRACERT VIA VPN TO HONG KONG KONG

C:\>tracert play.net-7.org

Tracing route to play.net-7.org [87.106.15.67]
over a maximum of 30 hops:

1 46 ms 49 ms 52 ms 192.168.35.16
2 52 ms 45 ms 51 ms 192.168.32.3
3 44 ms 45 ms 47 ms ge9-3.br01.hkg12.pccwbtn.net [63.218.175.17]
4 258 ms 269 ms 267 ms decix.bb-d.fra3.fra.de.oneandone.net [80.81.192.123]
5 259 ms 271 ms 273 ms te-3-3.bb-d.bs.kae.de.oneandone.net [212.227.120.9]
6 254 ms 247 ms 250 ms ae-11.gw-distp-a.bad.oneandone.net [212.227.122.5]
7 271 ms 269 ms 264 ms ae-1.gw-prtr-r231-a.bad.oneandone.net [195.20.247.50]
8 277 ms 261 ms 260 ms play.net-7.org [87.106.15.67]
Link to comment
Share on other sites

[quote name='RojoMuerte' timestamp='1300837347' post='37044']
Crap looks like they fixed it for now. Yesterday was taking 20-30hops to reach play.net-7.org and once it hit like hop 9/11 (heh coincidence!) it started taking a nose dive till last hop(I dont have the printout. As I assumed it was the ISP because this morning its now only taking 19 total hops to reach play.net-7.org and I can connect fine.

Still have a lil higher latency than would like but I can't do much about that. bout 300-400ms ping range (which was normal before I had connectivity issues. Stupid ISP here just cuz it has 100MB up and down it wants to use an inefficient route lol like 19 hops vs the 9hops with VPN to Hong Kong active lol... Gah oh well.

I guess I was wondering if the servers have some sort of threshold/response expectancy to timeout which I would expect does in regards to errors I got. Just wondering if that's tweakable and if it has any side effects in doing so.

Anyways just me poking finger at places that prevent me my EnB fix you know how it goes lol...
[/quote]
Good to hear it's back to normal at least. At some point, the server will probably abort your connection if it takes you too long to respond, but I doubt it was doing do in your case. I get the feeling it might've been more of a packet drop issue (it usually is). If your latency to the server is the problem, I believe net7proxy usually gives you a good yelling-at about it.
Link to comment
Share on other sites

[quote name='C Del' timestamp='1300838906' post='37047']
Good to hear it's back to normal at least. At some point, the server will probably abort your connection if it takes you too long to respond, but I doubt it was doing do in your case. I get the feeling it might've been more of a packet drop issue (it usually is). If your latency to the server is the problem, I believe net7proxy usually gives you a good yelling-at about it.
[/quote]


Ya I would have 1 random packet drop every now and then but oddball thing was kept constant ping and even during straight no loss scenarios did the same thing. Ya Im glad its back to a usable state at least lol. I'll be giving that FB issue a go this weekend hopefully can provide you some better info on that problem.
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...