Virgin Media Community

[Crown]

Hi there. I have a problem with my connection on EvE online it keeps disconnecting me whilst i interact with the game, such as, structure bashing and in game missions.

i started getting problems a few months ago with random disconnects but It's very frequent now for about 2-3 weeks every 5 minutes or so and it is very frustrating!  it's making it unplayable and has already cost me money from replacing in game items that have been lost due to these disconnects.

it also has trouble buffering youtube videos. it will pause the video completely through buffering and require a refresh sometimes up to 3 x

I have been a long time Virgin Media Customer and a Long time EvE player. yet never encountered this before. it is 100% on my end. due to other people not disconnecting with the server. and other things causing problems such as the youtube problem.

the service status says my internet is fine. even though there is something not quite right.

any help will be appreciated. thank you.

[Merv75]

I too am having the exact same issue and have been suffering with predictable socket closed errors in game all the time. I have spoken with EVE support and they had me run all sorts of tests which all showed the problem is being caused by the connections timing out. I will copy the trace route info here in case it sheds some light for us.

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

C:\Users\####>tracert 87.237.34.200

Tracing route to srv200-c.ccp.cc [87.237.34.200]
over a maximum of 30 hops:

1 35 ms 2 ms 1 ms routerlogin.net [192.168.0.1]
2 * * * Request timed out.
3 13 ms 19 ms 19 ms bagu-core-2a-xe-723-0.network.virginmedia.net [6
2.252.244.113]
4 * * * Request timed out.
5 20 ms 22 ms 20 ms 86.85-254-62.static.virginmediabusiness.co.uk [6
2.254.85.86]
6 23 ms 23 ms 19 ms ldn-b1-link.telia.net [213.248.84.25]
7 28 ms 29 ms 20 ms ldn-bb3-link.telia.net [62.115.114.234]
8 38 ms 28 ms 29 ms adm-bb3-link.telia.net [213.155.136.99]
9 37 ms 30 ms 38 ms adm-b2-link.telia.net [62.115.112.125]
10 26 ms 29 ms 27 ms verisign-ic-324757-adm-b2.c.telia.net [62.115.15
2.107]
11 34 ms 29 ms 27 ms 64.6.77.223
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\Users\####>ping www.google.com -n 30

Pinging www.google.com [209.85.202.104] with 32 bytes of data:
Reply from 209.85.202.104: bytes=32 time=30ms TTL=44
Reply from 209.85.202.104: bytes=32 time=29ms TTL=44
Reply from 209.85.202.104: bytes=32 time=28ms TTL=44
Reply from 209.85.202.104: bytes=32 time=36ms TTL=44
Reply from 209.85.202.104: bytes=32 time=34ms TTL=44
Reply from 209.85.202.104: bytes=32 time=33ms TTL=44
Reply from 209.85.202.104: bytes=32 time=32ms TTL=44
Reply from 209.85.202.104: bytes=32 time=31ms TTL=44
Reply from 209.85.202.104: bytes=32 time=29ms TTL=44
Reply from 209.85.202.104: bytes=32 time=28ms TTL=44
Reply from 209.85.202.104: bytes=32 time=27ms TTL=44
Reply from 209.85.202.104: bytes=32 time=36ms TTL=44
Reply from 209.85.202.104: bytes=32 time=27ms TTL=44
Reply from 209.85.202.104: bytes=32 time=33ms TTL=44
Reply from 209.85.202.104: bytes=32 time=28ms TTL=44
Reply from 209.85.202.104: bytes=32 time=30ms TTL=44
Reply from 209.85.202.104: bytes=32 time=29ms TTL=44
Reply from 209.85.202.104: bytes=32 time=28ms TTL=44
Reply from 209.85.202.104: bytes=32 time=37ms TTL=44
Reply from 209.85.202.104: bytes=32 time=32ms TTL=44
Reply from 209.85.202.104: bytes=32 time=27ms TTL=44
Reply from 209.85.202.104: bytes=32 time=29ms TTL=44
Reply from 209.85.202.104: bytes=32 time=29ms TTL=44
Reply from 209.85.202.104: bytes=32 time=33ms TTL=44
Reply from 209.85.202.104: bytes=32 time=32ms TTL=44
Reply from 209.85.202.104: bytes=32 time=31ms TTL=44
Reply from 209.85.202.104: bytes=32 time=30ms TTL=44
Reply from 209.85.202.104: bytes=32 time=29ms TTL=44
Reply from 209.85.202.104: bytes=32 time=28ms TTL=44
Reply from 209.85.202.104: bytes=32 time=27ms TTL=44

Ping statistics for 209.85.202.104:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 37ms, Average = 30ms

C:\Users\####>ping www.google.de -n 30

Pinging www.google.de [209.85.202.94] with 32 bytes of data:
Reply from 209.85.202.94: bytes=32 time=37ms TTL=46
Reply from 209.85.202.94: bytes=32 time=28ms TTL=46
Reply from 209.85.202.94: bytes=32 time=37ms TTL=46
Reply from 209.85.202.94: bytes=32 time=29ms TTL=46
Reply from 209.85.202.94: bytes=32 time=37ms TTL=46
Reply from 209.85.202.94: bytes=32 time=30ms TTL=46
Reply from 209.85.202.94: bytes=32 time=32ms TTL=46
Reply from 209.85.202.94: bytes=32 time=31ms TTL=46
Reply from 209.85.202.94: bytes=32 time=37ms TTL=46
Reply from 209.85.202.94: bytes=32 time=29ms TTL=46
Reply from 209.85.202.94: bytes=32 time=28ms TTL=46
Reply from 209.85.202.94: bytes=32 time=30ms TTL=46
Reply from 209.85.202.94: bytes=32 time=33ms TTL=46
Reply from 209.85.202.94: bytes=32 time=34ms TTL=46
Reply from 209.85.202.94: bytes=32 time=32ms TTL=46
Reply from 209.85.202.94: bytes=32 time=31ms TTL=46
Reply from 209.85.202.94: bytes=32 time=29ms TTL=46
Reply from 209.85.202.94: bytes=32 time=37ms TTL=46
Reply from 209.85.202.94: bytes=32 time=35ms TTL=46
Reply from 209.85.202.94: bytes=32 time=29ms TTL=46
Reply from 209.85.202.94: bytes=32 time=33ms TTL=46
Reply from 209.85.202.94: bytes=32 time=36ms TTL=46
Reply from 209.85.202.94: bytes=32 time=33ms TTL=46
Reply from 209.85.202.94: bytes=32 time=32ms TTL=46
Reply from 209.85.202.94: bytes=32 time=30ms TTL=46
Reply from 209.85.202.94: bytes=32 time=39ms TTL=46
Reply from 209.85.202.94: bytes=32 time=38ms TTL=46
Reply from 209.85.202.94: bytes=32 time=37ms TTL=46
Reply from 209.85.202.94: bytes=32 time=30ms TTL=46
Reply from 209.85.202.94: bytes=32 time=34ms TTL=46

Ping statistics for 209.85.202.94:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 39ms, Average = 32ms

C:\Users\####>ping 87.237.34.200 -n 30

Pinging 87.237.34.200 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 87.237.34.200:
Packets: Sent = 30, Received = 0, Lost = 30 (100% loss),

C:\Users\####>

[Crown]

(UPDATE: Last night i took some advice from some Friends on EvE. to put my router into 'MODEM MODE')

Upon doing this, my disconnects and buffer problems have been completely solved. I never had an issue with the SUPERHUB before. 

but this should give it a temporary fix for you sir.

any VM input would be appreciated 

[Merv75]

I can confirm turning Modem Mode on worked for me (wish I had known this some months ago). It is however a bad workaround if you value your manhood in a house full of social media monsters lol.

Today though I got my upgraded hub (2ac up to 3) and now my disconnection woes have ceased completely. Whether this was due to the new hardware, or the fact the connection was reset/restarted I dont know but im now happily crash free 🙂

[Emma_E]

Hi Both,

Glad to see things are now looking better for you, I am unsure as to whether you were playing on a wired or wireless connection but it sounds like you are ok now. 

If you need any help in the future we will be happy to take a look for you all the best

Emma

[Ross-L]

Hi just a little bump pf this topic

I've been dealing with this same issue for years now and never been able to figure it out, turning on modem mode isn't an option as i need wifi for other people in the house(from what i see it disables wifi?)

I only get socket closures when a citadel dies or gets reinforced its really strange but its not my computer as I've recently built a new one and it isn't on CCP's end so its something to do with virgin.

[legacy1]

Or maybe its router mode you can try modem mode with EvE online from a wired PC to test it out.

[Ross-L]

I tried it in modem mode tonight and it fixes my problems but it means other people in the house are doing without wifi, does the new superhub fix this problem? would virgin send me one?

[legacy1]

You could get your own wireless router with 1Gb port to fix your issue with the hub in modem mode.

[Mezmeriza]

I'm getting this problem now...only when doing Incursion sites in EVE Online. (High pop systems, larger fleets and only when warping around). Has this fix ever been solved without having to go back to the stone ages and having no wifi? I'm using a Superhub 2ac we got when we first got virgin 6 years ago and have always been hard wired (who the hell uses wifi for gaming?). I ran all the tests for speed and stuff and everything else looks ok (110 dl, 10 ul), but im the only person having this kind of problem and resetting the router isn't working.