Black-Cell.net

  • October 18, 2018, 07:31:05 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: Issue with particular teamspeak server  (Read 2143 times)

kobrakeen

  • Offline Offline
  • Posts: 33
  • But they won't let dream to live or live to dream.
    • View Profile
    • Facebook Me!
Issue with particular teamspeak server
« on: August 08, 2006, 01:11:31 AM »

Hey, I was wondering if anybody out there could help me solve my problem with TeamSpeak. I am unable to connect 70.84.203.226:9400 (NXC server).
I continually get a message saying "No reply from server" etc etc, which happens when the server is down. But I know for a fact that the server is not down, because friends of mine have told me that they are on it at the exact time that I'm trying to connect.
I have never had problems with this before. It may have something to do with the fact that I've just switched rooms, so my IP is different and all now. But I am able to connect to BC ts server, so I guess I'm just really confused. I have a few ss if people want to see them.

Thanks.
Logged

bmruze

  • Renegade Server Moderator
  • Offline Offline
  • Posts: 987
    • View Profile
Re: Issue with particular teamspeak server
« Reply #1 on: August 08, 2006, 04:48:57 AM »

check/recheck the port
Logged

ccfan4326

  • Network Administrator
  • Offline Offline
  • Posts: 1608
    • View Profile
Re: Issue with particular teamspeak server
« Reply #2 on: August 08, 2006, 05:06:45 AM »

That is indeed odd, especially since the BC server and NXC server both in the same datacenter.

Could you try pinging both of them? Start -> Run -> cmd and then "ping IP". Don't include the port. 67.19.75.20 is BC's IP.
Logged

zepher03

  • Offline Offline
  • Posts: 248
    • View Profile
Re: Issue with particular teamspeak server
« Reply #3 on: August 08, 2006, 03:30:14 PM »

Well the ts went down again, it will probably be down for about a day or less, try again when it's back up, see if it fixes the problem.

kobrakeen

  • Offline Offline
  • Posts: 33
  • But they won't let dream to live or live to dream.
    • View Profile
    • Facebook Me!
Re: Issue with particular teamspeak server
« Reply #4 on: August 08, 2006, 05:58:07 PM »

Yes, it is definitely odd. I pinged both of them, and BC pinged just fine. Obviously, since NXC ts server is down at the moment, it timed out. But I'll try again once it's up and running.

And I would need more help to check/recheck the port. I don't know how to do that.

Thanks!
Logged

kobrakeen

  • Offline Offline
  • Posts: 33
  • But they won't let dream to live or live to dream.
    • View Profile
    • Facebook Me!
Re: Issue with particular teamspeak server
« Reply #5 on: August 09, 2006, 01:04:19 AM »

double post ftl ... anyway, the server is up again, and i have tried to ping it again. it tried 4 times and each time the request timed out. so, any other ideas? this is going beyond frustrating ...
Logged

ccfan4326

  • Network Administrator
  • Offline Offline
  • Posts: 1608
    • View Profile
Re: Issue with particular teamspeak server
« Reply #6 on: August 09, 2006, 03:42:27 AM »

Do a traceroute. Instead of the ping command, use "tracert IP". This should show the route between you and the server and where it's dropping off. If you could, paste the results of that and the results of a traceroute to our server as well. If you don't know how to copy from the command line, right-click the window's titlebar, go to Properties, and then check QuickEdit Mode.
Logged

kobrakeen

  • Offline Offline
  • Posts: 33
  • But they won't let dream to live or live to dream.
    • View Profile
    • Facebook Me!
Re: Issue with particular teamspeak server
« Reply #7 on: August 09, 2006, 04:29:34 AM »

this is the tracert to the NXC ts server.
Code: [Select]
1    <1 ms    <1 ms    <1 ms  router-10-10-161-0.iastate.edu [10.10.161.254]
 2    <1 ms    <1 ms    <1 ms  b31gb1-vlan254.tele.iastate.edu [129.186.254.131

 3    <1 ms    <1 ms    <1 ms  e63gb2-436.tele.iastate.edu [192.245.179.22]
 4     8 ms     8 ms     8 ms  kscymo2wcx010-gige10-1-wcg.net [65.77.99.177]
 5    20 ms    19 ms    19 ms  brvwil1wcx2-pos4-0-oc48.wcg.net [64.200.240.49]

 6    19 ms    20 ms    20 ms  64.200.249.186
 7    20 ms    20 ms    20 ms  te-4-3.car2.Chicago1.Level3.net [4.68.110.33]
 8    20 ms    20 ms    20 ms  ae-1-51.bbr1.Chicago1.Level3.net [4.68.101.1]
 9    38 ms    37 ms    37 ms  as-0-0.bbr1.Dallas1.Level3.net [209.247.11.22]
10    38 ms    38 ms    38 ms  ae-24-56.car4.Dallas1.Level3.net [4.68.122.176]

11    38 ms    38 ms    39 ms  4.78.224.14
12    39 ms    38 ms    38 ms  vl32.dsr02.dllstx3.theplanet.com [70.85.127.62]

13    39 ms    39 ms    38 ms  po31.dsr01.dllstx5.theplanet.com [70.85.127.106]

14    39 ms    39 ms    41 ms  po1.car02.dllstx5.theplanet.com [70.84.160.132]

15     *        *        *     Request timed out.
16     *        *        *     Request timed out.
17     *        *        *     Request timed out.
18     *        *        *     Request timed out.
^^it just kept timing out after that.


and this is the tracert for the BC ts server.
Code: [Select]
C:\Documents and Settings\Keenan>tracert 67.19.75.20

Tracing route to 14.4b.1343.static.theplanet.com [67.19.75.20]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router-10-10-161-0.iastate.edu [10.10.161.254]
  2    <1 ms    <1 ms    <1 ms  b31gb1-vlan254.tele.iastate.edu [129.186.254.131
]
  3    <1 ms    <1 ms    <1 ms  e63gb2-436.tele.iastate.edu [192.245.179.22]
  4     8 ms     8 ms     8 ms  kscymo2wcx010-gige10-1-wcg.net [65.77.99.177]
  5    20 ms    19 ms    20 ms  brvwil1wcx2-pos4-0-oc48.wcg.net [64.200.240.49]

  6    20 ms    20 ms    20 ms  64.200.249.186
  7    20 ms    20 ms    20 ms  te-4-4.car2.Chicago1.Level3.net [4.68.110.37]
  8    20 ms    20 ms    20 ms  ae-1-55.bbr1.Chicago1.Level3.net [4.68.101.129]

  9    38 ms    38 ms    37 ms  ae-0-0.bbr2.Dallas1.Level3.net [64.159.1.110]
 10    38 ms    38 ms    38 ms  ae-24-56.car4.Dallas1.Level3.net [4.68.122.176]

 11    38 ms    38 ms    38 ms  4.78.220.10
 12    38 ms    38 ms    38 ms  vl31.dsr01.dllstx3.theplanet.com [70.85.127.29]

 13   236 ms   243 ms   227 ms  vl41.dsr01.dllstx4.theplanet.com [70.85.127.83]

 14    39 ms    39 ms    39 ms  gi1-0-2.car17.dllstx4.theplanet.com [67.18.116.8
5]
 15    42 ms    40 ms    39 ms  14.4b.1343.static.theplanet.com [67.19.75.20]

Trace complete.


so it's obvious that it's not making it there. for now, however, NXC has a new ts server which i am able to connect to. but i would still like to get this figured out. thanks ccfan.
Logged

ccfan4326

  • Network Administrator
  • Offline Offline
  • Posts: 1608
    • View Profile
Re: Issue with particular teamspeak server
« Reply #8 on: August 09, 2006, 07:47:12 AM »

Yeah, it looks to be an issue with The Planet. Nothing you can do about it. I'd suggest that NXC open a support ticket with The Planet about the problem and give them the traceroute you just gave me. They may also want a traceroute from NXC's server to you, in which case you'll need to give NXC your IP address.
Logged

kobrakeen

  • Offline Offline
  • Posts: 33
  • But they won't let dream to live or live to dream.
    • View Profile
    • Facebook Me!
Re: Issue with particular teamspeak server
« Reply #9 on: August 10, 2006, 01:11:03 PM »

Alright. I guess it's up to NXC now if they want to open a support ticket. They have now moved to the new ts server for sure (it's twice as big), so this isn't a problem anymore. But needless to say, your help is greatly appreciated!
Logged
Pages: [1]   Go Up