Disconnects all the time

[Thomas Roberts]

hey, i am having the same problem with VRC as i am in FSINN

 

viewtopic.php?f=43&t=48949

 

is my other topic in the FSInn forums, but when i start VRC - i can see a load of aircraft - then the controller list empties - the planes disappear then after a short while i get the message that i disconnected.

 

I have forwarded port 3290 UDP and that hasn't really made any difference

 

Help much appreciated!

[Richard Gerrish]

try connecting to a different server.

[Thomas Roberts]

I have still the same thing happening

[Jordan Krushen 1135174]

hey, i am having the same problem with VRC as i am in FSINN

is my other topic in the FSInn forums, but when i start VRC - i can see a load of aircraft - then the controller list empties - the planes disappear then after a short while i get the message that i disconnected.

 

I have forwarded port 3290 UDP and that hasn't really made any difference

The port forward shouldn't help much for this, it's just for voice timeouts.

 

If you're getting this with other software too, it sounds like a network problem. You could try tracing the route to the servers you're connecting to when it happens, to see if there's congestion or something wonky along the path.

 

It could also just be that your router is acting flakey. Give it a good kick and a power cycle, see if that helps.

 

J.

[Thomas Roberts]

Tracing route to flyin.org [88.198.19.202]
over a maximum of 30 hops:

 1     1 ms    <1 ms    <1 ms  192.168.2.1
 2    17 ms    17 ms    18 ms  esr11.manchester6.broadband.bt.net [217.47.158.1
42]
 3    23 ms    17 ms    18 ms  217.47.158.13
 4    19 ms    18 ms    19 ms  217.47.108.6
 5    18 ms    18 ms    19 ms  217.41.173.25
 6    18 ms    18 ms    20 ms  217.41.173.66
 7    20 ms    22 ms    20 ms  217.41.173.118
 8    19 ms    17 ms    18 ms  217.41.173.62
 9    18 ms    18 ms    20 ms  217.47.109.49
10    20 ms    18 ms    18 ms  londonc-access3-s25.ukcore.bt.net [194.72.2.177]

11    26 ms    24 ms    24 ms  core1-pos0-9-5-0.ealing.ukcore.bt.net [62.172.10
3.66]
12   779 ms   166 ms    31 ms  core4te-0-3-0-0.telehouse.ukcore.bt.net [62.172.
102.17]
13    32 ms    25 ms    26 ms  linx-2.init7.net [195.66.226.175]
14    33 ms    32 ms    33 ms  r1ams1.core.init7.net [77.109.128.149]
15    48 ms    45 ms    44 ms  r1fra1.core.init7.net [77.109.128.153]
16    40 ms    40 ms    39 ms  gw-hetzner.init7.net [77.109.135.18]
17   100 ms    73 ms    49 ms  hos-bb1.juniper1.rz4.hetzner.de [213.239.240.200
]
18    44 ms    46 ms    48 ms  hos-tr2.ex3k3.rz5.hetzner.de [213.239.244.98]
19    60 ms    43 ms    42 ms  flyin.org [88.198.19.202]

Trace complete.

 

Nothing out of the ordinary there is there?

[Jordan Krushen 1135174]

Tracing route to flyin.org [88.198.19.202]
over a maximum of 30 hops:

 1     1 ms    <1 ms    <1 ms  192.168.2.1
 2    17 ms    17 ms    18 ms  esr11.manchester6.broadband.bt.net [217.47.158.142]
 3    23 ms    17 ms    18 ms  217.47.158.13
 4    19 ms    18 ms    19 ms  217.47.108.6
 5    18 ms    18 ms    19 ms  217.41.173.25
 6    18 ms    18 ms    20 ms  217.41.173.66
 7    20 ms    22 ms    20 ms  217.41.173.118
 8    19 ms    17 ms    18 ms  217.41.173.62
 9    18 ms    18 ms    20 ms  217.47.109.49
10    20 ms    18 ms    18 ms  londonc-access3-s25.ukcore.bt.net [194.72.2.177]
11    26 ms    24 ms    24 ms  core1-pos0-9-5-0.ealing.ukcore.bt.net [62.172.103.66]
12   779 ms   166 ms    31 ms  core4te-0-3-0-0.telehouse.ukcore.bt.net [62.172.102.17]
13    32 ms    25 ms    26 ms  linx-2.init7.net [195.66.226.175]
14    33 ms    32 ms    33 ms  r1ams1.core.init7.net [77.109.128.149]
15    48 ms    45 ms    44 ms  r1fra1.core.init7.net [77.109.128.153]
16    40 ms    40 ms    39 ms  gw-hetzner.init7.net [77.109.135.18]
17   100 ms    73 ms    49 ms  hos-bb1.juniper1.rz4.hetzner.de [213.239.240.200]
18    44 ms    46 ms    48 ms  hos-tr2.ex3k3.rz5.hetzner.de [213.239.244.98]
19    60 ms    43 ms    42 ms  flyin.org [88.198.19.202]

Trace complete.

 

Nothing out of the ordinary there is there?

Hop 12's not looking so hot; sometimes large variations in ping to a router can be congestion. It's really something you need to check right at the time of a disconnect, as traffic varies so much on the Internet. Remember, though, that any hop leading up to that one, including your own router, could be the cause of that delay. It takes multiple traces and a bit of intuition to be able to tell what's really the cause of the problem.