[Hosh-pak]

I have a problem:
After a while playing on our sever it shows "connection interrupted" and waiting doesnt help, reconnecting doesnt either
But I can connect to base servers, so I dont know if its a problem with KR server or with JA+ servers..
Does anyone know why thats happening to me and how to fix it?

[AJ]

lag

[Clank]

whel sometimes u dont need to disconect and reconect u can just type in the console

/recon

[jawfin]

That may well be your settings.

Base servers will use the settings from jampconfig.cfg in you base folder, and JA+ uses the jampconfig.cfg in the japlus folder - thus explaining the apparent differences.

As you are most likely on DSL/ADSL try putting these settings in once you are on server: -
/rate 25000
/snaps 40
/cl_packetdup 0
/cl_timenudge 0
/cg_smoothclients 1

If you have a high end machine, also do
/cl_maxpackets 100

Check the Setup/Video and make sure "Video Sync" is turned Off.

[Hosh-pak]

i think that worked, THANKS!

[Hosh-pak]

it happened again. yesterday i could play for an hour without any problems..
maybe it just didnt save the settings, should have writeconfig and exec'd i guess..
and in my server list it wont show KR1 (i only see IP and Ping is "..." and 0 players..) but i can see KR SafeHaven normally

[Hosh-pak]

its still happening, so i reinstalled jka and downloaded ja+
but that didnt change anything. no problems with kr2 or other servers.
no one else whos having problems with the server?

[Clank]

hmmm maybe its because of ur location but that dosent explains that u dont lagg in KR2

[RVCA]

does this happen on other servers that run ja+ or just kr1?

[Hosh-pak]

now it happened on a base server and it couldnt show any servers in the list.. so i guess its my connection, my game, my pc..

[jawfin]

This is on the possibility that the issue is not it your house. You can run a traceroute on your connection on the good days and on the bad days and compare the results.

Do: -
[Windows Key] + "R"
type in "cmd" and press enter

In the command prompt: -
cd desktop
tracert 208.43.15.254 > good.txt
-for a good connection, and do
tracert 208.43.15.254 > bad.txt
- for a bad connection.

Once you got them both open them side by side with notepad (they are on your desktop) compare the pings of each hop and see if you can find any problems.
Note with this that if one hop spikes but the next is low again, its not as issue; some routing computers don't like to be pinged so it'll take longer for the ICMP packet to return. A bad route shows an IP that has a higher IP (like, more than +30 of the previous hop) and stays consistently higher from then on.


In house. Are you playing on WiFi or Cable? Does your router allow for wireless access? If so, are you sure it is secure? (Note that WEP alone is not secure, easy to hack by a script kiddie.) If your router allows wireless access but you don't need it, then disable it - that'll stop wardrivers (neighbours) from flooding your modem.

[Hosh-pak]

wow thanks, jawfin
but i dont have any problems since 2 days now
but if it should happen again, ill have to write that comand
every time i play? and if problems appear again ill write bad and if
it works without any problems ill write good?

[jawfin]

That command builds a textfile. From a cmd prompt you can just put in: -
tracert kr1.knights-reborn.org
or whatever to see the route. The > bit tells the command output to go to a text file, that way you can compare them side to side. Bad and good is just so you can identify them later.

It was using this that I detected a problem with SoftLayer's intranet (ET's ISP) from any connection coming across the Pacific. I told ET of this, they then told SoftLayer who then fixed the problem. So, you still need to be able to detect where any problem actually is and have the proof to show it, and hope the company at fault takes you seriously. This, of course, is only relevant if the issue is not local to your internet connection.