Teamspeak Server (fluffy) again?

Yob · Post by **Yob** » Wed Sep 28, 2005 2:37 pm

Is Teamspeak always so erratic? I can't seem to log on to the server today. The beer server works though. What gives? I know we've been having issues with it lately, any news on a fix?

Post by **Cheesy** » Wed Sep 28, 2005 6:51 pm

Sometimes the IP changes, so just use teamspeak2.icongamer.com and you'll never have problems.

Post by **Ash2Dust** » Wed Sep 28, 2005 6:54 pm

TS had downtime issues last night for several hours and I use "teamspeak2.icongamer.com" as the IP.

Post by **Cheesy** » Wed Sep 28, 2005 6:58 pm

Errr sorry lemme clarify: occasionally, the server will go down for whatever reason and then come back up a few hours later. However, that is always followed by a few days of confusion because so many people insist on using the numbers that become outdated.

So never was the wrong word, but the vast majority of the time, people are just using an outdated IP.

Post by **Redman** » Wed Sep 28, 2005 7:56 pm

Actually it has been crashing a lot lately and part of it has nothing to do with the IP. I have been using teamspeak2.icongamer.com and it still crashed twice in the last 72 hours. There is defenitely more than just an IP change going on.

Post by **Cheesy** » Wed Sep 28, 2005 10:57 pm

Here's the reply I got from Icongamer:

Teamspeak is at it's permament home now, it should'nt be going anywhere
now. I apologize for the inconvenience it may have caused, but we were
upgrading some of our network and unfortunately, Ts got caught into the mix.

So it sounds like it should be all better now

Post by **Redman** » Wed Sep 28, 2005 11:44 pm

Thanks Cheesy for looking in to this and letting us know!!

Post by **Ash2Dust** » Thu Sep 29, 2005 12:55 am

I love quick feedback.

Yob · Post by **Yob** » Thu Sep 29, 2005 8:22 am

Thanks, Cheesy! I changed the adress from I.P.# to teamspeak2.icongamer.com and it worked like a charm. Now my issue is with the TS Overlay

Post by **TubEsTeak** » Thu Sep 29, 2005 10:07 pm

I believe the TS server was moved between boxes as they did some internal restructuring of their network and some server re-tasking. Last email I received has it fixed...