Forum

Page 2 of 2 FirstFirst 12
Results 16 to 22 of 22
  1. #16
    Join Date
    June 2008
    Posts
    18,409
    Ar2rJk < Start your server as said above. The server won't recognize the ip binding without the parameters.
    All official server had to use these parameters and it never workd without.

    Dimmizer Please make sure, that port 9987 UDP is opened for your server and make sure that the ip is correct.
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  2. #17
    Join Date
    September 2007
    Location
    California
    Posts
    6
    Quote Originally Posted by dante696 View Post
    Dimmizer Please make sure, that port 9987 UDP is opened for your server and make sure that the ip is correct.
    I've never screwed with IP tables before since I've always had a control panel to do these kinds of things for me. Would you be so kind to provide me with the command to open the 9987 UDP port please .

  3. #18
    Join Date
    June 2011
    Location
    Russian Federation
    Posts
    204
    Quote Originally Posted by Dimmizer View Post
    I've never screwed with IP tables before since I've always had a control panel to do these kinds of things for me. Would you be so kind to provide me with the command to open the 9987 UDP port please .
    Code:
    sudo iptables -t filter -A INPUT -p udp -m udp --dport 9987 -j ACCEPT
    sudo iptables -t filter -A OUTPUT -p udp -m udp --dport 9987 -j ACCEPT
    edit by dante
    Thank you
    Last edited by dante696; July 3rd, 2012 at 02:54 PM.

  4. #19
    Join Date
    July 2006
    Posts
    1,600

    resolving to binary ip failed

    I checked my server's logs and came upon this errors (Serverversion 3.0.6.1):

    Code:
    2012-08-15 13:12:03.620126|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-15 17:06:33.972160|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-15 22:15:42.601877|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-17 11:58:33.268864|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-18 14:06:09.585633|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-18 15:00:24.536588|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-19 17:32:20.847950|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-19 20:18:19.486270|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-23 09:58:30.604515|ERROR   |ParamParser   |   | Protocol mismatch, old client or old server?
    2012-08-23 09:58:52.467043|ERROR   |ParamParser   |   | Protocol mismatch, old client or old server?
    2012-08-23 21:26:45.027493|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-24 08:19:08.404707|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-24 08:49:00.757839|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-24 09:19:02.939241|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-24 11:51:38.135232|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    I replaced my server's wan ip with xxx.xxx.xxx.xxx. (but notice the dot at the end of the string).

    Does anyone know why and how this error occurs?

    This thread was merged from a moderator
    Last edited by dante696; August 24th, 2012 at 02:55 PM.

  5. #20
    Join Date
    June 2011
    Location
    Russian Federation
    Posts
    204
    I still have the same inifile because the answer was not who did not say all that I have written is to edit inifile put ip 0.0.0.0. I tried in the end nothing happened. tried to enter my external IP - all the same. deleted inifile run standard server - all the same. and this is all after version 3.0.6

  6. #21
    Join Date
    July 2006
    Posts
    1,600
    Quote Originally Posted by maxi1990 View Post
    I checked my server's logs and came upon this errors (Serverversion 3.0.6.1):

    Code:
    2012-08-15 13:12:03.620126|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-15 17:06:33.972160|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-15 22:15:42.601877|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-17 11:58:33.268864|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-18 14:06:09.585633|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-18 15:00:24.536588|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-19 17:32:20.847950|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-19 20:18:19.486270|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-23 09:58:30.604515|ERROR   |ParamParser   |   | Protocol mismatch, old client or old server?
    2012-08-23 09:58:52.467043|ERROR   |ParamParser   |   | Protocol mismatch, old client or old server?
    2012-08-23 21:26:45.027493|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-24 08:19:08.404707|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-24 08:49:00.757839|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-24 09:19:02.939241|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    2012-08-24 11:51:38.135232|ERROR   |              |   | resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead
    I replaced my server's wan ip with xxx.xxx.xxx.xxx. (but notice the dot at the end of the string).

    Does anyone know why and how this error occurs?

    This thread was mered from a moderator
    Thanks for merging the threads.
    However, my server works flawlessly and I did not experience any problems but I still wonder why or how this error appears.
    All binding is set to 0.0.0.0 and was never set to anything else.

  7. #22
    Join Date
    December 2009
    Location
    Germany
    Posts
    4
    Hi, sorry for reactivating the old thread. But I am encountering the same problem with my Ubuntu server. The error message "resolving 'xxx.xxx.xxx.xxx.' to binary ip failed, using 0.0.0.0 instead" continues to appear, although all bindings (voice/query/filetransfer) are set to 0.0.0.0 in the inifile. The external ip xxx.xxx.xxx.xxx isn't mentioned anywhere in my configuration. The .ini is being loaded correctly. It is not a big deal because the server is working properly, but nevertheless it annoys me seeing this error message popping up in the log all the time and being unable to fix it.
    Are there any new ideas on how to solve this issue?

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Music bound to a channel
    By Toelieloe in forum General Questions
    Replies: 1
    Last Post: May 9th, 2013, 07:50 PM
  2. TS3 - Website registration and Nickname bound tokens
    By Frederikoo in forum Linux / FreeBSD
    Replies: 1
    Last Post: December 27th, 2010, 09:38 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •