Server socket bind error
 

News:

29 December 2022 - PtokaX 0.5.3.0 (20th anniversary edition) released...
11 April 2017 - PtokaX 0.5.2.2 released...
8 April 2015 Anti child and anti pedo pr0n scripts are not allowed anymore on this board!
28 September 2015 - PtokaX 0.5.2.1 for Windows 10 IoT released...
3 September 2015 - PtokaX 0.5.2.1 released...
16 August 2015 - PtokaX 0.5.2.0 released...
1 August 2015 - Crowdfunding for ADC protocol support in PtokaX ended. Clearly nobody want ADC support...
30 June 2015 - PtokaX 0.5.1.0 released...
30 April 2015 Crowdfunding for ADC protocol support in PtokaX
26 April 2015 New support hub!
20 February 2015 - PtokaX 0.5.0.3 released...
13 April 2014 - PtokaX 0.5.0.2 released...
23 March 2014 - PtokaX testing version 0.5.0.1 build 454 is available.
04 March 2014 - PtokaX.org sites were temporary down because of DDOS attacks and issues with hosting service provider.

Main Menu

Server socket bind error

Started by ruler, 26 September, 2005, 00:41:24

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

ruler

can anyone help?
when starting my Ptokax 0.3.3.21 [debug] i get nothing but server socket bind error on port 411?
i was normally working ok but now i cant get the dam thing to work at all :(
the port 411 is not in use by any other programs and this computer is not linked to any other computer, its running on a standard DLS modem (not firewalled)
any idea's. thanks

The Direct Connect Global Banlist get protected.

bastya_elvtars

QuoteOriginally posted by ruler
can anyone help?
when starting my Ptokax 0.3.3.21 [debug] i get nothing but server socket bind error on port 411?
i was normally working ok but now i cant get the dam thing to work at all :(
the port 411 is not in use by any other programs and this computer is not linked to any other computer, its running on a standard DLS modem (not firewalled)
any idea's. thanks

There is an error code as well. Post it.
Everything could have been anything else and it would have just as much meaning.

ruler

Server socket bind error: WSAEADDRNOTAVAIL (10049) for port: 411
its been almost an hour now and still cannot connect. same result everytime

The Direct Connect Global Banlist get protected.

bastya_elvtars

QuoteOriginally posted by ruler
Server socket bind error: WSAEADDRNOTAVAIL (10049) for port: 411
its been almost an hour now and still cannot connect. same result everytime

B0rked DNS service?
Everything could have been anything else and it would have just as much meaning.

ruler

heh after 1h 30mins i got connected :S
hmm that server socket error is a real pain and it does seem a little pointless having an Auto Start button  on the hub because after robooting  i always seem to get that error?
its strange that only this version gives this error.

The Direct Connect Global Banlist get protected.

PPK

Disable on Network tab "Listen only on IP of this address" :))
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

ruler

yup i tried that and found the hub started right away but was unable to connect to the hub, infact nobody could connect.
the hub did eventually start with "Listen only on IP of this address" checked but only after waiting 1h 30 mins approx.
actually im not sure if it's better to have that option ticked or not?
:)

The Direct Connect Global Banlist get protected.

SMF spam blocked by CleanTalk