Topic: D2 Down Today?

[Bonk]

The question is why only us two? What do we have in common? Are we the only two with this issue?

Funny you're on FIOS and I'm on dial-up - the two extremes of speeds. This might tell us something. Did you check out the Speed test thread in engineering. I'd be curious to see your results.

The fact that I have a very slow connection and you have a very fast connection tells me this is more likely a serverside hardware issue. (new switch, changes to the sonicwall firewall - or lack of..). Frey is confident that the directory server is set up exactly as it has been in the past and I do not doubt him, I just wonder if there is something we have missed...

[KBFLordKrueg]

And just when I'm ready to toss the whole system out the window...
I try for about the 20th time today, and...poof...it logs me on pretty as you please...
I try again 5 times...the 4th time I get a firewall message, but the 5th logs in just fine...
*sigh*
Some days it's just not worth chewing through the leather straps...

[KBFLordKrueg]

"tracert" stands for "Trace Route" and that is exactly what the command does.

That means: it looks like too many network hops to me, the added latency could be enough to cause the firewall detector server to timeout. Also the more hops between me and the directory server increases the likelyhood that my packets will pass through some superhorny ISP filter somewhere and get blocked. The directory server behaves exactly like many port scanning programs or scripts, I imagine many security devices flag this kind of thing now and either drop the packets or put them at the lowest priority.

The thing is, I think I would have gotten a similar tracert the last time I was able to login to the Dynaverse. So I don't know if this is the issue or not, I am just leaving no stone unturned.

Have patience Krueg (I know you have lots ), I will get to the bottom of this one way or another. Unfortunately this has stopped me working on other more fun stuff like the sprites file or my NSISBASS radio stuff. I will not return to those tasks until we solve this.

There have been some changes on the net recently: http://it.slashdot.org/article.pl?sid=08/03/25/2124224

Most likely totally unrelated, but as I said, I am leaving no stone unturned.

Part of the new hardware that went in at Dynaverse.net/Xenocorp.net in the last weeks was a new gigabit switch to increase the speed of all things local, but the directory server itself is not connected locally any longer (another change). Next time I'm talking to Frey I'll get the details of exactly what hardware the directory server is connected to the net through. It is possible there is some niggly little setting somewhere that has been neglected or forgotten.

Curious Krueg, can you post a tracert to sfc.client.dynaverse.net for comparison? A tracert from SFHQ who can connect would be good too... if we have way more hops than people who are connecting that may be the issue and it may be possible to adjust the directory server firewall detector to account for it.

Since others can connect I am still assuming this is a client side issue, but certainly have not ruled out serverside issues as a possible cause.

Well, I probably could if I had a clue as to how to do that...
If you can expain how to do so (in layman's terms  ) I will do so...

[Bonk]

lol! It hates us!

I was just thinking of all the people in the community to be unable to login to the Dynaverse, you and I are two that are rather important to the community. (Though every player we have is valuable and appreciated of course.)

But to have the Klingon leadership and the developer of the OCI unable to login is downright evil.

I'll try some repetitions here too, usually I give a connection attempt three strikes, I'll go with five attempts. Its rather time consuming though with so many trials to perform.

If you have made a fresh OP install I will not bother. This is more and more looking like a serverside networking hardware issue. Note also that Symantec Corporate AV is intalled on the directory server IIRC and God only knows when it will decide to interfere, yes Frey, I know it was always fine before but I just cannot trust Symantec not to corrupt running processes in memory or network communications... and its constantly updating itself, continually changing its behaviour... like a virus.

[Bonk]

Well, I probably could if I had a clue as to how to do that...
If you can expain how to do so (in layman's terms  ) I will do so...

Not too hard...

Start...Run... "cmd" ( press enter)
Type: tracert client.sfc.dynaverse.net (press enter - wait)
Right click the bar at the top of the command prompt window, select Edit...Mark then use the mouse to highlight all the output. Then without clicking anywhere else right click the menu bar at the top of the window again and select Edit...Copy... then paste it into a forum post. (using the fixedsys font in a forum font tag will preserve the spacing - but its not necessary).

[FCM_SFHQ_XC]

A tracert from SFHQ who can connect would be good too... if we have way more hops than people who are connecting that may be the issue and it may be possible to adjust the directory server firewall detector to account for it.

I'll have one for you as soon as I get home in about 4 hours

[KBFLordKrueg]

Well, I probably could if I had a clue as to how to do that...
If you can explain how to do so (in layman's terms  ) I will do so...

Not too hard...

Start...Run... "cmd" ( press enter)
Type: tracert client.sfc.dynaverse.net (press enter - wait)
Right click the bar at the top of the command prompt window, select Edit...Mark then use the mouse to highlight all the output. Then without clicking anywhere else right click the menu bar at the top of the window again and select Edit...Copy... then paste it into a forum post. (using the fixedsys font in a forum font tag will preserve the spacing - but its not necessary).

OK...

C:\Documents and Settings\Administrator>tracert client.sfc.dynaverse.net

Tracing route to heimdall.xenocorp.net [67.78.36.183]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     8 ms    10 ms     7 ms  L100.VFTTP-50.TAMPFL.verizon-gni.net [96.228.177
.1]
  3    11 ms    10 ms     9 ms  G12-2-650.LCR-06.TAMPFL.verizon-gni.net [130.81.
105.18]
  4    48 ms    22 ms    22 ms  so-6-0-0-0.PEER-RTR1.ATL81.verizon-gni.net [130.
81.17.141]
  5    21 ms    22 ms    22 ms  66.109.9.141
  6    26 ms    22 ms    22 ms  ae-2-0.cr0.atl20.tbone.rr.com [66.109.6.170]
  7    42 ms    42 ms    42 ms  ae-3-0.cr0.dfw10.tbone.rr.com [66.109.6.36]
  8    44 ms    42 ms    42 ms  66.109.6.89
  9    41 ms    43 ms    41 ms  gig2-0-0.dllatxchn-rtr5.tx.rr.com [72.179.205.73
]
 10    46 ms    48 ms    47 ms  70.125.217.79
 11    47 ms    48 ms    46 ms  gig1-30.dllatxgar-rtr3.tx.rr.com [70.125.217.115
]
 12    47 ms    46 ms    47 ms  gig14-1.dllatxgar-ar41.tx.rr.com [70.125.216.94]

 13    53 ms    54 ms    55 ms  rrcs-67-78-36-183.sw.biz.rr.com [67.78.36.183]

Trace complete.

C:\Documents and Settings\Administrator>

There...
Out of curiosity, I tried logging in 20 times in a row to see how many failed.
None did...  I donno
Whatever it was preventing me from logging in has gone away as mysteriously as it appeared.

[Corbomite]

Out of curiosity, I tried logging in 20 times in a row to see how many failed.
None did...  I donno
Whatever it was preventing me from logging in as gone away as mysteriously as it appeared.

Tribbles in yer engine room laddy? 

[KBFLordKrueg]

Out of curiosity, I tried logging in 20 times in a row to see how many failed.
None did...  I donno
Whatever it was preventing me from logging in has gone away as mysteriously as it appeared.

Tribbles in yer engine room laddy? 

Well, obviously, it was of Federation doing...what else could it possibly be? 

[vortex79]

Only server I don't see is Strayy's, the one I play on x.x :-P

[Highlander11]

For that server, you need Nuclear Wessels last mission package and OP + v4.0 that is about it..

for easier reference.. you can just get the OP Enhancement Package v5.1 and have everything for OP at one time.

Can someone link me to the patch? not sure which one it is on this site



EDIT: Nevermind! found it! doh!

[Bonk]

OK...

C:\Documents and Settings\Administrator>tracert client.sfc.dynaverse.net

Tracing route to heimdall.xenocorp.net [67.78.36.183]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     8 ms    10 ms     7 ms  L100.VFTTP-50.TAMPFL.verizon-gni.net [96.228.177.1]
  3    11 ms    10 ms     9 ms  G12-2-650.LCR-06.TAMPFL.verizon-gni.net [130.81.105.18]
  4    48 ms    22 ms    22 ms  so-6-0-0-0.PEER-RTR1.ATL81.verizon-gni.net [130.81.17.141]
  5    21 ms    22 ms    22 ms  66.109.9.141
  6    26 ms    22 ms    22 ms  ae-2-0.cr0.atl20.tbone.rr.com [66.109.6.170]
  7    42 ms    42 ms    42 ms  ae-3-0.cr0.dfw10.tbone.rr.com [66.109.6.36]
  8    44 ms    42 ms    42 ms  66.109.6.89
  9    41 ms    43 ms    41 ms  gig2-0-0.dllatxchn-rtr5.tx.rr.com [72.179.205.73]
 10    46 ms    48 ms    47 ms  70.125.217.79
 11    47 ms    48 ms    46 ms  gig1-30.dllatxgar-rtr3.tx.rr.com [70.125.217.115]
 12    47 ms    46 ms    47 ms  gig14-1.dllatxgar-ar41.tx.rr.com [70.125.216.94]
 13    53 ms    54 ms    55 ms  rrcs-67-78-36-183.sw.biz.rr.com [67.78.36.183]

Trace complete.

C:\Documents and Settings\Administrator>

There...
Out of curiosity, I tried logging in 20 times in a row to see how many failed.
None did...  I donno
Whatever it was preventing me from logging in has gone away as mysteriously as it appeared.

Bloody hell. I still can't get in, I just made six consecutive tries, all failed.

We are at the two extremes. Your tracert shows only 13 hops and very low latency, compared the the 25 high latency hops to me.

This is most disturbing. I'm glad you can connect but I'm still stuck! 

It occurs to me that we had a nasty ice storm here last week and winds have been in the range of 80-120Km/hr for the last three days straight, perhaps the line from the house to the pole or between the poles themselves have suffered more damage taking my connection quality below some usable threshold. It has been dropping altogether more often recently.  (just did as I was trying to make this post)

[Bonk]

I can see the directory server with the Flipside Client (see attached image) , but for some reason OP cannot. That points to a fresh OP install. Considering Krueg did one and connect now as well.

Well I guess its time for a long overdue cleanup and backup to make room for a fresh OP install.

[Bonk]

WHOAH HO HO... what do we have here? Where did this second registered firewall detector come from? Who's IP address is that? Very suspicious. Very, very, very suspicious and extremely disconcerting.

[Bonk]

Oh, wait... how many servers are up right now? One? Is this IP Strayy's or the Boneyard?

OrgName:    MPOWER COMMUNICATIONS CORP.
OrgID:      MPWR
Address:    175 SULLY'S TRAIL
Address:    SUITE 350
City:       PITTSFORD
StateProv:  NY
PostalCode: 14534
Country:    US

NetRange:   208.57.0.0 - 208.57.255.255
CIDR:       208.57.0.0/16
NetName:    MPOWER-001
NetHandle:  NET-208-57-0-0-1
Parent:     NET-208-0-0-0-0
NetType:    Direct Allocation
NameServer: NS2.MPOWERCOM.NET
NameServer: NS1.MPOWERCOM.NET
Comment:   
RegDate:   
Updated:    2001-12-28

RTechHandle: ZM147-ARIN
RTechName:   MPOWER COMMUNICATIONS CORP
RTechPhone:  +1-702-310-4578
RTechEmail:  ip-mgmt@mpowercom.net

OrgAbuseHandle: MIAA-ARIN
OrgAbuseName:   Mpower IP Abuse Administrator
OrgAbusePhone:  +1-877-642-4375
OrgAbuseEmail:  ip-abuse@mpowercom.net

OrgTechHandle: MITA-ARIN
OrgTechName:   Mpower IP Technical Administrator
OrgTechPhone:  +1-702-310-4578
OrgTechEmail:  ip-mgmt@mpowercom.net

[Bonk]

Looks like the serverkit can talk to the directory server just fine from my connection. I am running a test server. Can anyone confirm its in the serverlist? (actually I just saw a client query hit it so it can be seen in the serverlist)

Interestingly it has not added me to the list of firewall detectors as shown by the Flipside client. Which makes me suspicious about that second firewall detector (A misconfigured serverkit? A hacker?)

And since I am closer to New York than Texas, I'll probably hit that firewall detector first.

Are any other Canadians able to get to the serverlist (in OP)?

Might be time to fire up a sniffer to look closer at this. I guess Wireshark 1.0 was released recently too!

If that New York IP address is not one of our server hosts (Strayy's or The Boneyard) then we should ban it instanter.

Who runs The Boneyard? I need to contact all of our active admins ASAP.

[KBF-Kurok]

ya i saw your server

[FCM_SFHQ_XC]

Code: [Select]

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

C:\Documents and Settings\Starfleet HQ>tracert client.sfc.dynaverse.net

Tracing route to heimdall.xenocorp.net [67.78.36.183]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    17 ms    15 ms    16 ms  user-1121s01.dsl.mindspring.com [66.32.240.1]
  3    17 ms    16 ms    18 ms  dir03-vl-5.ga-atlanta0.ne.earthlink.net [199.174.118.1]
  4    17 ms    16 ms    16 ms  cor02-ve-96.ga-atlanta0.ne.earthlink.net [209.165.96.17]
  5    17 ms    16 ms    17 ms  bor01-g2-4.ga-atlanta0.ne.earthlink.net [207.69.223.169]
  6    17 ms    16 ms    18 ms  acs01.ga-kingslan1.ne.earthlink.net [209.86.66.50]
  7    17 ms    17 ms    16 ms  gi9-2.core01.atl03.atlas.cogentco.com [154.54.12.233]
  8    16 ms    18 ms    17 ms  po13-1.core01.atl01.atlas.cogentco.com [154.54.5.113]
  9    17 ms    16 ms    15 ms  te3-3.ccr01.atl01.atlas.cogentco.com [154.54.5.38]
 10    31 ms    30 ms    31 ms  te9-4.mpd01.iah01.atlas.cogentco.com [154.54.24.6]
 11    37 ms    37 ms    37 ms  te7-1.ccr02.iah01.atlas.cogentco.com [154.54.7.193]
 12    38 ms    38 ms    38 ms  te3-3.ccr02.dfw01.atlas.cogentco.com [154.54.5.137]
 13    37 ms    37 ms    37 ms  te4-3.ccr02.dfw03.atlas.cogentco.com [154.54.6.54]
 14    37 ms    36 ms    36 ms  te8-1.mpd01.dfw03.atlas.cogentco.com [154.54.25.9]
 15    37 ms    36 ms    36 ms  twcable.dfw03.atlas.cogentco.com [154.54.11.50]
 16    41 ms    40 ms    42 ms  ae-1-0.cr0.hou30.tbone.rr.com [66.109.6.180]
 17    40 ms    40 ms    40 ms  66.109.6.109
 18    45 ms    46 ms    45 ms  gig2-0-0.dllatxchn-rtr6.tx.rr.com [72.179.205.75]
 19    47 ms    46 ms    45 ms  gig1-30.dllatxgar-rtr3.tx.rr.com [70.125.217.115]
 20    46 ms    48 ms    47 ms  gig14-1.dllatxgar-ar41.tx.rr.com [70.125.216.94]
 21    61 ms    52 ms    55 ms  rrcs-67-78-36-183.sw.biz.rr.com [67.78.36.183]

Trace complete.

[Bonk]

Thanks SFHQ! 21 hops (not the best and not much different from my 25) but good low latency.

I don't think the route is the issue now. If you look at my last few posts it looks like we have a hacker on the directory server network, or perhaps someone is testing a copy of the directory servers locally inappropriately? Maybe there's weirdly misconfigured game server running out there? Perhaps the old titan servers have leaked out somehow into the wrong hands? In which case we will have to take drastic measures to lock it all down.

I searched for 208.57.228.3 and 208.57.* in the forums database - we have no registered members on that block. (or least not using an  anonymous proxy).

I need to talk both Strayy and the Boneyard admin ASAP.

[FCM_SFHQ_XC]

Already sent you a PM about it, but yea that does look somewhat suspicious.. especially considering the IP isn't pingable anymore, so yea, very very curious and suspicious..