LFS Forum - Server Dedicated Problem

#1 - BIzO

Server Dedicated Problem

Sat 20 Oct 2007, 16:56

Hi,
I have a problem server
I can run a server by clicking on "New Party" with the port 63392 with the IP address "auto" but when I met the port 63392 in the dedicated server configuration, in the window, I mark "TCP Socket: bind failed "
How to solve this problem please?
Please answer

#2 - the_angry_angel

Sat 20 Oct 2007, 23:39

Either it's trying to use the wrong IP, port 63392 is already in use, or something is preventing it from binding to that address and port - for instance this can be acheived through a number of home firewall solutions.

#3 - BIzO

Mon 22 Oct 2007, 19:51

On the configuration, the IP address, I have not touched at xxx.xxx.xxx.xxx, the problem may come to?

#4 - BIzO

Thu 25 Oct 2007, 20:36

Up Pliz

#5 - BIzO

Sat 27 Oct 2007, 12:06

Up

#6 - Krammeh

Sun 28 Oct 2007, 09:14

xxx.xxx.xxx.xxx = un-defined.

Try changing the game port to a different port.

Also, make sure that any firewall is not blocking the LFS process.

#7 - franky500

Sun 28 Oct 2007, 15:38

also make sure that infront of the ip=XXX.XXX.XXX.XXX that there are TWO forward slashes..

eg:

//ip=XXX.XXX.XXX.XXX

instead of:
/ip=XXX.XXX.XXX.XXX

#8 - BIzO

Sun 28 Oct 2007, 17:53

Quote from Krammeh :xxx.xxx.xxx.xxx = un-defined.

Try changing the game port to a different port.

Also, make sure that any firewall is not blocking the LFS process.

I try another port, but it still does not

Quote from franky500 :also make sure that infront of the ip=XXX.XXX.XXX.XXX that there are TWO forward slashes..

eg:

//ip=XXX.XXX.XXX.XXX

instead of:
/ip=XXX.XXX.XXX.XXX

Yes, there are 2 slashes

#9 - franky500

Sun 28 Oct 2007, 18:10

i would guess its a firewall issue of some kind then.

#10 - BIzO

Sun 28 Oct 2007, 19:53

My firewall lets LFS Dedi and ports 63392, I do not see or is the problem!

#11 - the_angry_angel

Sun 28 Oct 2007, 22:35

Ok, 2 things.

Can you run this in a command prompt (start > run, type "cmd" and press ok):

cd Desktop & netstat -an > output.txt

On your desktop should appear output.txt, can you copy and paste the contents of that please.

Can you also copy and paste the contents of your config file, and tell us the name of the setup file, and how you're running the LFS dedi. Thank you.

#12 - BIzO

Sun 28 Oct 2007, 23:18

Here is the content of output.txt

Connexions actives
  Proto  Adresse locale         Adresse distante       tat
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49155          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49156          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49157          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:63392          0.0.0.0:0              LISTENING
  TCP    127.0.0.1:5354         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:27015        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:27015        127.0.0.1:49161        ESTABLISHED
  TCP    127.0.0.1:49158        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:49161        127.0.0.1:27015        ESTABLISHED
  TCP    192.168.1.10:139       0.0.0.0:0              LISTENING
  TCP    192.168.1.10:50430     207.46.111.73:1863     ESTABLISHED
  TCP    192.168.1.10:50518     213.40.20.2:29339      ESTABLISHED
  TCP    192.168.1.10:50534     213.40.20.2:80         CLOSE_WAIT
  TCP    192.168.1.10:50570     213.40.20.2:80         TIME_WAIT
  TCP    192.168.1.10:50572     207.46.26.253:7001     TIME_WAIT
  TCP    192.168.1.10:50573     85.68.75.59:1384       ESTABLISHED
  TCP    192.168.1.10:50587     91.121.29.152:80       TIME_WAIT
  TCP    192.168.1.10:50593     91.121.29.152:80       TIME_WAIT
  TCP    192.168.1.10:50600     91.121.29.152:80       TIME_WAIT
  TCP    192.168.1.10:50621     213.40.20.2:80         TIME_WAIT
  TCP    192.168.1.10:63392     83.113.132.161:1785    ESTABLISHED
  TCP    [::]:135               [::]:0                 LISTENING
  TCP    [::]:445               [::]:0                 LISTENING
  TCP    [::]:2869              [::]:0                 LISTENING
  TCP    [::]:3389              [::]:0                 LISTENING
  TCP    [::]:5357              [::]:0                 LISTENING
  TCP    [::]:49152             [::]:0                 LISTENING
  TCP    [::]:49153             [::]:0                 LISTENING
  TCP    [::]:49154             [::]:0                 LISTENING
  TCP    [::]:49155             [::]:0                 LISTENING
  TCP    [::]:49156             [::]:0                 LISTENING
  TCP    [::]:49157             [::]:0                 LISTENING
  TCP    [::1]:49159            [::]:0                 LISTENING
  UDP    0.0.0.0:123            *:*                    
  UDP    0.0.0.0:500            *:*                    
  UDP    0.0.0.0:3702           *:*                    
  UDP    0.0.0.0:3702           *:*                    
  UDP    0.0.0.0:4500           *:*                    
  UDP    0.0.0.0:5355           *:*                    
  UDP    0.0.0.0:49152          *:*                    
  UDP    0.0.0.0:49154          *:*                    
  UDP    0.0.0.0:49751          *:*                    
  UDP    0.0.0.0:63392          *:*                    
  UDP    127.0.0.1:1900         *:*                    
  UDP    127.0.0.1:44301        *:*                    
  UDP    127.0.0.1:49725        *:*                    
  UDP    127.0.0.1:49776        *:*                    
  UDP    127.0.0.1:49779        *:*                    
  UDP    127.0.0.1:49796        *:*                    
  UDP    127.0.0.1:49902        *:*                    
  UDP    192.168.1.10:9         *:*                    
  UDP    192.168.1.10:137       *:*                    
  UDP    192.168.1.10:138       *:*                    
  UDP    192.168.1.10:1900      *:*                    
  UDP    192.168.1.10:5353      *:*                    
  UDP    192.168.1.10:15793     *:*                    
  UDP    192.168.1.10:49901     *:*                    
  UDP    [::]:123               *:*                    
  UDP    [::]:500               *:*                    
  UDP    [::]:3702              *:*                    
  UDP    [::]:3702              *:*                    
  UDP    [::]:5355              *:*                    
  UDP    [::]:49153             *:*                    
  UDP    [::]:49155             *:*                    
  UDP    [::1]:1900             *:*                    
  UDP    [::1]:49899            *:*                    
  UDP    [fe80::3c74:3f57:a5e8:4680%11]:1900  *:*                    
  UDP    [fe80::3c74:3f57:a5e8:4680%11]:49900  *:*                    
  UDP    [fe80::6c88:f535:b865:f74e%10]:1900  *:*                    
  UDP    [fe80::6c88:f535:b865:f74e%10]:49897  *:*                    
  UDP    [fe80::7575:779c:32c6:9d70%8]:1900  *:*                    
  UDP    [fe80::7575:779c:32c6:9d70%8]:49898  *:*

#13 - the_angry_angel

Sun 28 Oct 2007, 23:31

TCP    192.168.1.10:63392     83.113.132.161:1785    ESTABLISHED
  UDP    0.0.0.0:63392          *:*

Something using the ports LFS uses appears to be running. It could be an LFS dedicated server. Check your process list for LFS.exe.

Or run "netstat -ano" which will give your the process id of the executable using those ports, and then run "tasklist /svc", or add the "PID" column to the taskmanager to find that process.

#14 - BIzO

Sun 4 Nov 2007, 21:19

Problem solved