PtokaX forum

PtokaX => Support => Topic started by: ruler on 26 September, 2005, 00:41:24

Title: Server socket bind error
Post by: ruler on 26 September, 2005, 00:41:24
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
Title:
Post by: bastya_elvtars on 26 September, 2005, 01:03:52
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.
Title:
Post by: ruler on 26 September, 2005, 01:09:06
Server socket bind error: WSAEADDRNOTAVAIL (10049) for port: 411
its been almost an hour now and still cannot connect. same result everytime
Title:
Post by: bastya_elvtars on 26 September, 2005, 01:17:05
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?
Title:
Post by: ruler on 26 September, 2005, 01:23:45
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.
Title:
Post by: PPK on 26 September, 2005, 03:55:16
Disable on Network tab "Listen only on IP of this address" :))
Title:
Post by: ruler on 26 September, 2005, 14:31:11
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?
:)