solap troubles
Ain't logged on for an age, no time
, tried to have a quick fly and can't log on to any of the solap servers, gpz and planet2 seem fine but fail to log on to solap, managed however to create a game on there as a test, can't switch it off now.... sorry 'bout that. Probably just being incredibly stoopid due to extreme sleeplessnessnessszzzzz......
Could you ping solap.fe23.co.uk and copy paste the results?
Open up the command prompt and type :
and see what it throws up.
Open up the command prompt and type :
Code: Select all
ping solap.fe23.co.ukere we gooo
Pinging solap.fe.co.uk [67.63.55.11] with 32 bytes of data:
Request timed out.
Reply from 67.63.55.11: bytes=32 time=95ms TTL=237
Request timed out.
Request timed out.
Ping statistics for 67.63.55.11:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 95ms, Maximum = 95ms, Average = 95ms
tracert solap.fe.co.uk
Tracing route to solap.fe.co.uk [67.63.55.11]
over a maximum of 30 hops:
1 9 ms 8 ms 8 ms 10.0.0.2
2 10 ms 9 ms 10 ms 83.100.248.254
3 10 ms 11 ms 11 ms 10.102.240.65
4 11 ms 10 ms 10 ms po4.nr5.civ.ipc.kcom.com [10.102.240.213]
5 15 ms 15 ms 16 ms 10.102.58.7
6 16 ms 16 ms 16 ms 213.161.93.205
7 72 ms 19 ms 18 ms bcr1-ge-4-3-0.Londonlnx.savvis.net [195.66.224.3
9]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * 97 ms 67.63.55.11
Trace complete.
Pinging solap.fe.co.uk [67.63.55.11] with 32 bytes of data:
Request timed out.
Reply from 67.63.55.11: bytes=32 time=95ms TTL=237
Request timed out.
Request timed out.
Ping statistics for 67.63.55.11:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 95ms, Maximum = 95ms, Average = 95ms
tracert solap.fe.co.uk
Tracing route to solap.fe.co.uk [67.63.55.11]
over a maximum of 30 hops:
1 9 ms 8 ms 8 ms 10.0.0.2
2 10 ms 9 ms 10 ms 83.100.248.254
3 10 ms 11 ms 11 ms 10.102.240.65
4 11 ms 10 ms 10 ms po4.nr5.civ.ipc.kcom.com [10.102.240.213]
5 15 ms 15 ms 16 ms 10.102.58.7
6 16 ms 16 ms 16 ms 213.161.93.205
7 72 ms 19 ms 18 ms bcr1-ge-4-3-0.Londonlnx.savvis.net [195.66.224.3
9]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * 97 ms 67.63.55.11
Trace complete.
Is this what you mean?
I dunno. It could be. There's certainly one way to find out. Can you take that out of the loop and connect your old way?
I dunno. It could be. There's certainly one way to find out. Can you take that out of the loop and connect your old way?
Who is your ISP? And by any chance are you in South London? There's another player experiencing issues and I'm wondering if there's something common to both of you other than being in the UK. I don't think Sgt_Baker has experienced any issues. He might be in a different part of town or using a different ISP (and therefore a different routing path).
It's rather difficult to tell what's going on as it appears that there are some rather strict firewall rules between you and Solap which are preventing a decent network disgnosis. This, incidentally, appears to have nothing to do with your ISP. I have the same problem, except only three of my hops are FWed. Unfortunately, the links we know to be causing problems between Europe and Solap are right in the middle of the * * * mess.
Whilst it's of use to us that you've registered this as an issue, our hands are tied where giving a definitive diagnosis are concerned, so I'd lay a guess on the ge11-2 link problem.
Regards,
Baker
Whilst it's of use to us that you've registered this as an issue, our hands are tied where giving a definitive diagnosis are concerned, so I'd lay a guess on the ge11-2 link problem.
Regards,
Baker

Granary Sergeant Baker - Special Bread Service (Wurf - 13th Oct 2011)



