Download cancelled. Can't download 1/16/08 update or play.

[Triagel]

I have noted that the routes taken to the US and Euro Servers are different. Euro goes via a server which is dropping the connection yet the Us connection is not a problem.

[AuldY]

Have been having the same problem myself. Both my laptop (Vista) and desktop (XP SP2) will not connect. AOL is my ISP, netgear the router.

I have been able to log into EQ2 using nextdoors wireless connection (which is orange) so I guess that the ISP is the problem. Have spoken to AOL and pointed them at this URL. I was able to connect to EQ2 right up until friday the 25th (when an AOL update happened....). All i have got so far is that the network team will look into it (2nd call to technical ended up with someone who listened instead of 'computer says no'- so maybe not all technical help operatives are rubbish )

If they do nothing but say they are not responsible for connecting to the SoE server just the internet (which AOL do have that kind of reputation), the good news (for me) is that I have already served my contract with AOL and changing ISP is not going to be a huge problem. However some people locked into Virgin or AOL are going to end up getting pretty narked!

Well that's my two pence worth. GL on getting online all

Urs.

[rightormig]

wow what a solution I have to change ISP ????

[Triagel]

Seems that way, i got 3 days then i change ISP.

Although it would be great to recieve more communication from SOE, along the lines thatas we are "valued" customers they are also attempting to resolve the issue. What ever theat might be, ie contacting the various ISP to confirm that there is no bottlenecks that could be resolved.

[rightormig]

Tech guy said he escalted the call and i should be getting a reply back in 3 days

All i can really do since SOE have gone quiet on this ????

[Tojan]

rightormight wrote:

Tech guy said he escalted the call and i should be getting a reply back in 3 days

All i can really do since SOE have gone quiet on this ????

I was told the same thing from 2nd level that it would take 3 days, so I waited 3 days, no response, called back and spoke to second level. The person I had dealt with hadnt even logged the issue so tbh I wouldnt hold my breath for that response

Surely it would be significantly easier for SOE to "allow access" to their servers from a certain IP range than it would expecting the numerous EQ2 players that are experiencing the issue to change ISP's.........

[Lenvaren]

Woot....I just wasted 3 minutes of my life coming here to see if there'd been any offical response yet...silly me, should have known better

 Considering I can connect to some US based servers I find it very difficult to believe that it's really something my ISP's done/needs to fix. The only update that AOL and it would seem Virgin have started doing, is , in my case anyway, upgrading the cabling to provide better speeds which in turn has meant an ip chance from what it was before to an IP begining with 92. That is the only similarity between AOL and Virgin. That is at least something if not everything to do with the reason we're currently unable to connect.

I can't see much point in switching ISP's, if that were even an option for me, as it's just as possible that a few weeks/months done the line the new ISP also makes the switch to IP's beginning with 92. Look at the trace routes that have been posted, they all fall over at the same point, which is a server inside SoE, the fact that some will let you through and some won't seriously suggests that's it's something their end not ours that's somply been highlighted by these recent changes.

Yes, switching ISP would probably solve the problem but not because it's a different ISP, simply because the IP address you'll be given isn't one of the new range beginning with 92. The simple fact that some servers are accesible even with these IP's beginning with 92 suggests it's something SOE could resolve by looking at those servers, seeing what's different and why they allow connections from IP's beginning with 92 and applying that too all the other servers...I'm sure it's not as simple as that but that has to be the basics.

Either way, approaching one week now of not being able to connect and 4 days without a response from tech support of any type, you'd almost think they didn't want yer regular payment

[TSR-DanT]

Not a single one of these trace routes help.  It cannot be from behind a router, as I said in my original post.  I have to trace back to you, and if you're behind a router, it's pointless..  And those of you who posted up that might not be behind a router, I wouldn't know, because there's no IP posted for me to use..Please post up a trace route to ONLY your NORMAL play server, NOT behind a router, and INCLUDE your IP address.  Thank you.

[jimbrit]

Plugged directly into my cable modem Microsoft Windows XP [Version 5.1.2600](C) Copyright 1985-2001 Microsoft Corp.C:Documents and Settings>tracert splitpaw.everquest2.comTracing route to amseq2-03-01.everquest2.com [195.33.139.96]over a maximum of 30 hops:  1     7 ms     8 ms     7 ms  10.54.128.1  2     7 ms     7 ms     7 ms  62.31.224.161  3     9 ms    12 ms    12 ms  pc-62-30-243-57-bn.blueyonder.co.uk [62.30.243.57]  4    11 ms    11 ms    19 ms  pc-62-30-243-86-bn.blueyonder.co.uk [62.30.243.86]  5     9 ms    10 ms    10 ms  194.117.136.146  6     9 ms     9 ms    10 ms  ns.de.prserv.net [195.66.224.27]  7    19 ms    18 ms    17 ms  165.87.224.186  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     *        *        *     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.IP Address is 92.232.84.72

[Uther Stormhammer]

Connected through a adsl modemMicrosoft Windows XP [Version 5.1.2600](C) Copyright 1985-2001 Microsoft Corp.my IP 92.8.230.62C:tracert crushbone.everquest2.comTracing route to ableq2-03-01.everquest2.com [199.108.202.97]over a maximum of 30 hops:  1    14 ms    14 ms    14 ms  host-92-8-224-1.as43234.net [92.8.224.1]  2    13 ms    12 ms    11 ms  92.31.253.4  3    11 ms    13 ms    13 ms  xe-11-2-0-scr001.log.as13285.net [78.144.2.3]  4    11 ms    13 ms    13 ms  xe-11-0-0-scr010.sov.as13285.net [78.144.0.226]  5    12 ms    13 ms    13 ms  tge1-4.fr3.lon.llnw.net [195.66.224.133]  6    81 ms    87 ms    80 ms  tge7-2.fr3.lga.llnw.net [69.28.171.125]  7    85 ms    85 ms    94 ms  tge2-4.fr3.iad.llnw.net [69.28.171.157]  8  sony.ge4-12.fr3.iad.llnw.net [68.142.111.254]  reports: Destination net unreachable.Trace complete.

[TSR-DanT]

Thank you, keep them coming please.  I need many different connections.

[rightormig]

Not using the router but if you could run these tests quickly please 

 iP 92.232.86.50 

 1     8 ms  4294967236 ms    75 ms  10.54.128.1  2     9 ms     8 ms    76 ms  62.31.224.161  3    10 ms     9 ms     9 ms  pc-62-30-243-57-bn.blueyonder.co.uk [62.30.243.57]  4    10 ms    11 ms    12 ms  pc-62-30-243-86-bn.blueyonder.co.uk [62.30.243.86]  5    94 ms    13 ms    18 ms  194.117.136.146  6    79 ms     9 ms     9 ms  tge1-4.fr3.lon.llnw.net [195.66.224.133]  7    17 ms   158 ms   152 ms  tge7-2.fr3.lga.llnw.net [69.28.171.125]  8    83 ms    83 ms   152 ms  tge2-4.fr3.iad.llnw.net [69.28.171.157]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

trying to connect to the the runnyeye.everquest2.com server

[Eternal-Goddess]

How do i do a Tracert from not behind a router please? I suck at technical stuff like this

[rightormig]

Eternal-Goddess wrote:

How do i do a Tracert from not behind a router please? I suck at technical stuff like this " width="15" height="15">

unplug your router and plug your pc straight into your cable modem turn off your modem and pc reboot them both

then START RUN,

 in the box type CMD

 then in the screen that opens up do this tracert YOURSERVERYOURTRYINGTOLOGINTOO.everquest2.com 

 example for me would be Tracert runnyeye.everquest2.com

 it should come back with something like

1     8 ms  4294967236 ms    75 ms  10.54.128.1  2     9 ms     8 ms    76 ms  62.31.224.161  3    10 ms     9 ms     9 ms  pc-62-30-243-57-bn.blueyonder.co.uk [62.30.243.57]  4    10 ms    11 ms    12 ms  pc-62-30-243-86-bn.blueyonder.co.uk [62.30.243.86]  5    94 ms    13 ms    18 ms  194.117.136.146  6    79 ms     9 ms     9 ms  tge1-4.fr3.lon.llnw.net [195.66.224.133]  7    17 ms   158 ms   152 ms  tge7-2.fr3.lga.llnw.net [69.28.171.125]  8    83 ms    83 ms   152 ms  tge2-4.fr3.iad.llnw.net [69.28.171.157]Request timed out. 21     *        *        *     Request timed out. 22     *        *        *     Request timed out. 23     *        *        *     Request timed out.

highlight all the text by using MARK then click your left/right mouse button at the same time to copy it then just paste it in here and wait

[Eternal-Goddess]

Microsoft Windows XP [Version 5.1.2600](C) Copyright 1985-2001 Microsoft Corp.

C:Documents and SettingsBecca>Tracert Splitpaw.everquest2.com

Tracing route to amseq2-03-01.everquest2.com [195.33.139.96]over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]  2    47 ms   120 ms    88 ms  host-92-2-192-1.as43234.net [92.2.192.1]  3    47 ms    55 ms   187 ms  92.31.251.14  4    35 ms    35 ms    34 ms  92.31.250.252  5   104 ms   121 ms     *     xe-9-3-0-scr001.log.as13285.net [78.144.2.133]  6    36 ms     *       37 ms  Opal-ge-2/2/0.mpr1.lhr2.above.net [213.161.78.209]  7   179 ms   215 ms   225 ms  208.185.188.186  8   198 ms     *      205 ms  ae-31-51.ebr1.London1.Level3.net [4.68.116.30]  9   236 ms   181 ms    36 ms  ae-1-100.ebr2.London1.Level3.net [4.69.132.118]

 10    44 ms    68 ms    54 ms  ae-2.ebr2.Amsterdam1.Level3.net [4.69.132.134] 11     *      112 ms    46 ms  ge-11-2.ipcolo1.Amsterdam1.Level3.net [4.68.120.169] 12     *        *        *     Request timed out. 13     *     vl155.amsixsw-1.sonyonline.net [213.244.164.38]  reports: Destination net unreachable.

Trace complete.

IP address is : 92.2.197.128

[rightormig]

Eternal-Goddess wrote:

Microsoft Windows XP [Version 5.1.2600](C) Copyright 1985-2001 Microsoft Corp.

C:Documents and SettingsBecca>Tracert Splitpaw.everquest2.com

Tracing route to amseq2-03-01.everquest2.com [195.33.139.96]over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]  2    47 ms   120 ms    88 ms  host-92-2-192-1.as43234.net [92.2.192.1]  3    47 ms    55 ms   187 ms  92.31.251.14  4    35 ms    35 ms    34 ms  92.31.250.252  5   104 ms   121 ms     *     xe-9-3-0-scr001.log.as13285.net [78.144.2.133]  6    36 ms     *       37 ms  Opal-ge-2/2/0.mpr1.lhr2.above.net [213.161.78.209]  7   179 ms   215 ms   225 ms  208.185.188.186  8   198 ms     *      205 ms  ae-31-51.ebr1.London1.Level3.net [4.68.116.30]  9   236 ms   181 ms    36 ms  ae-1-100.ebr2.London1.Level3.net [4.69.132.118]

 10    44 ms    68 ms    54 ms  ae-2.ebr2.Amsterdam1.Level3.net [4.69.132.134] 11     *      112 ms    46 ms  ge-11-2.ipcolo1.Amsterdam1.Level3.net [4.68.120.169] 12     *        *        *     Request timed out. 13     *     vl155.amsixsw-1.sonyonline.net [213.244.164.38]  reports: Destination net unreachable.

Trace complete.

IP address is : 92.2.197.128

your still connecting through your router which he claims is useless epic fail becky

[TipTopp]

Tracert to uk server - cant log in , and unable to for 12 days -

Traceert to Us server , can play anytime !

Microsoft Windows [Version 6.0.6000]Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:UsersAlex>tracert splitpaw.everquest2.com

Tracing route to amseq2-03-01.everquest2.com [195.33.139.96]over a maximum of 30 hops:

  1     9 ms     6 ms     8 ms  10.45.96.1  2     7 ms     7 ms     7 ms  gsr01-st.blueyonder.co.uk [62.30.65.1]  3     7 ms     7 ms     7 ms  195.188.230.73  4    25 ms    21 ms    21 ms  aztw-t3core-1b-ge-010-0.inet.ntl.com [80.1.240.129]  5    20 ms    22 ms    19 ms  bir-bb-b-so-110-0.inet.ntl.com [213.105.175.161]

  6    26 ms    27 ms    25 ms  nth-bb-a-so-100-0.inet.ntl.com [62.253.185.105]

  7    20 ms    21 ms    21 ms  nth-bb-b-ge-000-0.inet.ntl.com [62.253.185.118]

  8     *        *        *     Request timed out.  9    14 ms    13 ms    13 ms  ns.de.prserv.net [195.66.224.27] 10    20 ms    21 ms    21 ms  165.87.224.178 11     *        *        *     Request timed out. 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:UsersAlex>tracert butcherblock.everquest2.com

Tracing route to sdkeq2-08-01.everquest2.com [199.108.13.33]over a maximum of 30 hops:

  1     7 ms     7 ms     7 ms  10.45.96.1  2     7 ms     7 ms     8 ms  gsr01-st.blueyonder.co.uk [62.30.65.1]  3    29 ms    18 ms    25 ms  195.188.230.49  4    15 ms    18 ms    20 ms  aztw-t3core-1a-ge-010-0.inet.ntl.com [80.1.240.69]  5    17 ms    18 ms    16 ms  win-bb-a-so-200-0.inet.ntl.com [213.105.175.157]

  6    16 ms    20 ms    16 ms  bre-bb-b-so-100-0.inet.ntl.com [213.105.172.234]

  7    16 ms    17 ms    16 ms  195.50.91.129  8    17 ms    17 ms    19 ms  ae-0-53.bbr1.London2.Level3.net [4.68.117.65]  9   179 ms   151 ms   149 ms  as-2-0.mp1.SanDiego1.Level3.net [64.159.1.137] 10   156 ms   151 ms   151 ms  so-8-0.hsa1.SanDiego1.Level3.net [4.68.112.130]

 11   150 ms   149 ms   150 ms  vl861.sdtermswitch-1.sonyonline.net [63.215.251.130] 12   153 ms   151 ms   152 ms  vl831.sdkollsw-1.sonyonline.net [64.37.144.82] 13   151 ms   151 ms   153 ms  sdkeq2-08-01.everquest2.com [199.108.13.33]

Trace complete.

Hope this helps !

[TSR-ChrisL]

Hello everyone.It's looking like a routing problem between you, your isp and us. Based off the tracert's that I have been able to run there is a problem on most of them when trying to get into your general areas. Please take the tracert's that you have run to your ISP's and they should be able to get things worked out for you. It may boil down to a simple port being blocked that if they open it for you then you will be able to connect. I can assure you we are not blocking any of those IP addresses so you should be able to connect.If you have further questions please feel free to contact us and we will do what we can to try and help you out.

[jimbrit]

Spoke to my ISP tech support and their reply isHi JamesYou probably pointed out the cause at the end of your post, it looks like they have not updated their Bogon filters to take account of the newly released range of addresses.  These are filters to block data from IP ranges that are not in use.I'll raise it to our networks guys, however the changes will need to be made their endKind RegardsDave LowingsVirgin Media Technical SupportFor reference my post to them was I play everquest 2 and since thursday /friday have been unable to connect to the play server.having posted on the games tech support forums they have told me its an isp issue and have said to raise it hereThe server is splitpaw.everquest2.com and here is my tracert to itTracing route to amseq2-03-01.everquest2.com [195.33.139.96]over a maximum of 30 hops:  1     7 ms     8 ms     7 ms  10.54.128.1  2     7 ms     7 ms     7 ms  62.31.224.161  3     9 ms    12 ms    12 ms  pc-62-30-243-57-bn.blueyonder.co.uk [62.30.243.57]  4    11 ms    11 ms    19 ms  pc-62-30-243-86-bn.blueyonder.co.uk [62.30.243.86]  5     9 ms    10 ms    10 ms  194.117.136.146  6     9 ms     9 ms    10 ms  ns.de.prserv.net [195.66.224.27]  7    19 ms    18 ms    17 ms  165.87.224.186  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     *        *        *     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.This is also happening to 2 friends of mine who also live close to me.After posting on their support forum their reply was thisHello everyone.It's looking like a routing problem between you, your isp and us. Based off the tracert's that I have been able to run there is a problem on mst of them when trying to get into you general areas. Please take the tracert's that you have run to your ISP's and they should be able to get things worked out for you. It may boil down to a simple port being blocked that if they open it for you then you will be able to connect. I can assure you we are not blocking any of those IP addresses so you should be able to connect.If you have further questions please feel free to contact us and we will do what we can to try and help you out.Its also worth noting that everyone that cant connect has recently had their ip address changed to being with a 92Alias is xxxxxxxxxxxxAny help would be extremely appreciatedRegardsJames

[rightormig]

TSR-ChrisL wrote:

Hello everyone.It's looking like a routing problem between you, your isp and us. Based off the tracert's that I have been able to run there is a problem on most of them when trying to get into your general areas. Please take the tracert's that you have run to your ISP's and they should be able to get things worked out for you. It may boil down to a simple port being blocked that if they open it for you then you will be able to connect. I can assure you we are not blocking any of those IP addresses so you should be able to connect.If you have further questions please feel free to contact us and we will do what we can to try and help you out.

1    14 ms    14 ms    14 ms  host-92-8-224-1.as43234.net [92.8.224.1]  2    13 ms    12 ms    11 ms  92.31.253.4  3    11 ms    13 ms    13 ms  xe-11-2-0-scr001.log.as13285.net [78.144.2.3]  4    11 ms    13 ms    13 ms  xe-11-0-0-scr010.sov.as13285.net [78.144.0.226]  5    12 ms    13 ms    13 ms  tge1-4.fr3.lon.llnw.net [195.66.224.133]  6    81 ms    87 ms    80 ms  tge7-2.fr3.lga.llnw.net [69.28.171.125]  7    85 ms    85 ms    94 ms  tge2-4.fr3.iad.llnw.net [69.28.171.157]

11     *        *        *     Request timed out. 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.

after using a web based tracert I got this

 1  telh2.newnet.co.uk (212.87.64.1) [AS9191 - NewNet - Fast Access Internet]  0.223/0.327/0.530 (0.143) ms  3/3 pkts (0% loss)2  telh8.th (81.3.81." width="15" height="15" /> [AS9191 - NewNet plc - Fast Access Internet]  0.397/0.429/0.454 (0.023) ms  3/3 pkts (0% loss)3  tge1-4.fr3.lon.llnw.net (195.66.224.133) [AS5459 - UK-LINX-1]  0.608/0.752/0.982 (0.164) ms  3/3 pkts (0% loss)4  tge7-2.fr3.lga.llnw.net (69.28.171.125) [AS32421 - Proxy-registered route object]  68.2/68.3/68.7 (0.246) ms  3/3 pkts (0% loss)5  tge2-4.fr3.iad.llnw.net (69.28.171.157) [AS32421 - Proxy-registered route object]  84.9/91.6/100 (6.3" width="15" height="15" /> ms  3/3 pkts (0% loss)6  sony.ge4-12.fr3.iad.llnw.net (68.142.111.254) [AS22822 - LLNW]  85.3/85.4/85.5 (0.089) ms  3/3 pkts (0% loss)7  vl46.ashaens-1.sonyonline.net (64.37.144.177) [AS13720 - SOE LA/NY/SD Aggregate (by droisman)]  85.3/85.5/85.7 (0.160) ms  3/3 pkts (0% loss)8  vl46.ashaens-1.sonyonline.net (64.37.144.177) [AS13720 - SOE LA/NY/SD Aggregate (by droisman)] !U  * !U  85.4/85.5/85.5 (0.035) ms  2/3 pkts (33% loss)

 it falls over when it seems to hit your network

[Lenvaren]

Ok, Azlea and myself have been talking to Virgin tech supposrt concerning this issue and this was their response.

 You probably pointed out the cause at the end of your post, it looks like they have not updated their Bogon filters to take account of the newly released range of addresses.  These are filters to block data from IP ranges that are not in use.I'll raise it to our networks guys, however the changes will need to be made their end

 So...have u upgraded you're BOGON filters as they suggested, that would explain not only why we can't access u but also why u can't access us.

Can you get this checked and confirmed please. As IP's beginning with 92 weren't in use until recently there's a good chance you're blocking them purely because you're filters haven't been updated to recognise them.

[rightormig]

can I also get 10 days of play time added to my account if the fault ends up being with you

[Tebos]

Its also worth noting that everyone that cant connect has recently had their ip address changed to being with a 92

It's okay if an ISP changes IP addressing scheme's...that is not an issue. The issue at hand is the ISP (AOL) has made an area wide topology change that is NOW affecting those user's who connect up to SoE location due to some port topology change at AOL end.

All you can say to your immediate ISP is that you where able to play this game PRIOR to them assigning a completely different IP address scheme.  The onus is completly on them when you point this out to them.

The common denomiator is that people with in the same geographic area is affected where as everyone else is NOT, for the most part!

[TSR-ChrisL]

Thank you all for the additional information. We are going to check into any filter issue. However since I have seen posts in here where people are able to connect to some servers but not others I really doubt it would be any filter in our network causing this or it would affect connections to any server. I will put more info in here if we get any, but I am inclined to go with Tebos on this since you were able to play prior to the change in the IP address from your providers.

[jimbrit]

Tebos wrote:

Its also worth noting that everyone that cant connect has recently had their ip address changed to being with a 92

It's okay if an ISP changes IP addressing scheme's...that is not an issue. The issue at hand is the ISP (AOL) has made an area wide topology change that is NOW affecting those user's who connect up to SoE location due to some port topology change at AOL end.

All you can say to your immediate ISP is that you where able to play this game PRIOR to them assigning a completely different IP address scheme.  The onus is completly on them when you point this out to them.

The common denomiator is that people with in the same geographic area is affected where as everyone else is NOT, for the most part!

Shame  I am not with AOL

I just happen to have an IP beginning with 92

[jimbrit]

TSR-ChrisL wrote:

Thank you all for the additional information. We are going to check into any filter issue. However since I have seen posts in here where people are able to connect to some servers but not others I really doubt it would be any filter in our network causing this or it would affect connections to any server. I will put more info in here if we get any, but I am inclined to go with Tebos on this since you were able to play prior to the change in the IP address from your providers.

ISnt Splitpaw physically located in Europe unlike Runnyeye and the US servers though, could that make a difference?Have you checked the bogon filters as my isp suggest? Cmon SOE go that extra mile, I really dont want to be the middle man here between my game's tech support and my ISP's tech supportI just want to play the game I pay for " />

[spooonerism]

It appears that some of you have had better luck communicating with your ISP providers than I have.

I have now had three seperate, very long, converstions with AOL Tech Support and they point blank refuse to accept the notion that the issues we are now all experiencing has anything to do with them.

I have explained that the problem accessing SOE servers has only occured since AOL changed their IP addresses. However they blame the routers, the SOE servers, basically everyone apart from themselves.

It would be most efficient and expeditious if SOE Tech Support could contact AOL/Virgin Tech Support to address this matter rather than hundrends of individual calls from us. This has to be the way forward, surely!

[Lenvaren]

If you can confirm thet the BOGON filters are fully up to date on ALL servers, particularly Splitpaw (the only server not based in the US) then I'll be more than happy to go back to Virgin tech support and pass on the information.

However, at this time the above filer update is what they're using to put the onus on SOE. Until you can provide proof that this isn't the case then we're kinda stuffed tbh..both sides blame the other and we as paying customers are left frantically going back and forth in the middle trying to reolve something that really isn't our fault.

I shall look forward to your update TSR-ChrisL, please don't take too long to return too this thread and post confirmation one way or the other. As I'm sure you can appreciate we're all getting rather frustrated with this situation and would really like to reach a resolution of some sort.

[TSR-ChrisL]

I will try to get an update as quickly as possible. Don't get upset though if it takes a couple of hours for me to get any updates.

[jimbrit]

On to Live chat support at the moment and the TSR says there is no Blackleg to splitpaw serverI dont know what that means but will update as I find out