jander38 Posted April 9, 2011 Report Share Posted April 9, 2011 AFternoon, Everything was find last night and has been for a long time until now w/ Dual Boxing on the same pC, Now i get a "TCP Listener unable to bind to socket on port 3801 / 3500 on my 2nd client login, which locks up my 1st and then nothing now works. What happened? Pretty much looks like server is refusing any and all of my 3801 and 3500 connections. Quote Link to comment Share on other sites More sharing options...
karu [WDL] Posted April 9, 2011 Report Share Posted April 9, 2011 [quote name='Boogieman' timestamp='1302312995' post='38605']Pretty much looks like server is refusing any and all of my 3801 and 3500 connections.[/quote]no, it looks like proxy is unable to bind to those ports locally for client to connect to. one more reason to make proxy bind to dynamic ports, but for some reason TB does not do it. Instead proxy tries to figure out if there is already one running in those ports and then increments said ports by 10. obviously check fails. tho, only time I have encounteded it was when I launcher two proxy's too fast, so make sure you not trigger happy with launching two proxys at once. Quote Link to comment Share on other sites More sharing options...
jander38 Posted April 15, 2011 Author Report Share Posted April 15, 2011 [quote name='Boogieman' timestamp='1302312995' post='38605'] AFternoon, Everything was find last night and has been for a long time until now w/ Dual Boxing on the same pC, Now i get a "TCP Listener unable to bind to socket on port 3801 / 3500 on my 2nd client login, which locks up my 1st and then nothing now works. What happened? Pretty much looks like server is refusing any and all of my 3801 and 3500 connections. [/quote] Same Issue again today after a CTD. i was dual boxing fine and now exactly the same happens. i have reset PC/Router/MOdem/Switch and nothing. I have verified that all .exe's are set to sp3 and admin (they werent before and never was an issue (WIN7)). So now i can no longer dual box. If i port lock it wont let me log my 2nd client. i have toggled every option in the NET7proxy and nothing. If i wait until tomorrow or some random interval of time later i bet it will connect again. Any ideas DEVS as to why this occurs? 14/04/11 17:08:16 TCP connection on port 3500 was reset 14/04/11 17:08:16 Client connections terminated 14/04/11 17:08:17 WARNING: problem finding active E&B client - Attempting to re-establish client link. 14/04/11 17:11:14 MVAS thread running 14/04/11 17:11:14 Received Master login confirm, new UDP port is 3559 Avatar_id = 1073751029 14/04/11 17:11:14 <server> Master Login received - UDP sector port: 3559 14/04/11 17:11:14 >> Commence Login check. 14/04/11 17:11:14 Sending Login packet - connection active 14/04/11 17:11:58 TCP Listener unable to bind to socket on port 3500 14/04/11 17:12:36 Received Master login confirm, new UDP port is 3559 Avatar_id = 1073750605 14/04/11 17:12:36 <server> Master Login received - UDP sector port: 3559 14/04/11 17:12:36 >> Commence Login check. 14/04/11 17:12:36 Sending Login packet - connection active 14/04/11 17:13:53 MVAS thread running 14/04/11 17:13:53 Received Master login confirm, new UDP port is 3559 Avatar_id = 1073750605 14/04/11 17:13:53 <server> Master Login received - UDP sector port: 3559 14/04/11 17:13:53 >> Commence Login check. 14/04/11 17:13:53 Sending Login packet - connection active 14/04/11 17:21:55 TCP Listener unable to bind to socket on port 3500 14/04/11 17:21:55 TCP Listener unable to bind to socket on port 3801 14/04/11 17:22:39 ---> LogOff confirm 14/04/11 17:22:40 TCP connection on port 3801 closed gracefully 14/04/11 17:22:40 TCP connection on port 3500 closed gracefully 14/04/11 17:22:40 Client connections terminated 14/04/11 17:23:02 Received Master login confirm, new UDP port is 3559 Avatar_id = 1073751029 14/04/11 17:23:02 <server> Master Login received - UDP sector port: 3559 14/04/11 17:23:02 >> Commence Login check. 14/04/11 17:23:02 Sending Login packet - connection active 14/04/11 17:24:21 Connecting to Authentication Server on 87.106.131.253:443 14/04/11 17:24:22 TCP Listener unable to bind to socket on port 3801 14/04/11 17:24:22 TCP Listener unable to bind to socket on port 3500 14/04/11 17:25:10 ---> LogOff confirm 14/04/11 17:25:11 TCP connection on port 3801 closed gracefully 14/04/11 17:25:11 TCP connection on port 3500 closed gracefully 14/04/11 17:25:11 Client connections terminated 14/04/11 17:26:03 MVAS thread running 14/04/11 17:26:03 Received Master login confirm, new UDP port is 3559 Avatar_id = 1073750605 14/04/11 17:26:03 <server> Master Login received - UDP sector port: 3559 14/04/11 17:26:03 >> Commence Login check. 14/04/11 17:26:03 Sending Login packet - connection active 14/04/11 17:28:50 TCP Listener unable to bind to socket on port 3801 14/04/11 17:28:50 TCP Listener unable to bind to socket on port 3500 14/04/11 17:30:04 MVAS thread running 14/04/11 17:33:10 ---> LogOff confirm 14/04/11 17:33:10 TCP connection on port 3801 closed gracefully 14/04/11 17:33:10 TCP connection on port 3500 closed gracefully 14/04/11 17:33:10 Client connections terminated 14/04/11 17:38:05 MVAS thread running 14/04/11 17:38:06 Received Master login confirm, new UDP port is 3559 Avatar_id = 1073750605 14/04/11 17:38:06 <server> Master Login received - UDP sector port: 3559 14/04/11 17:38:06 >> Commence Login check. 14/04/11 17:38:06 Sending Login packet - connection active 14/04/11 17:39:57 TCP Listener unable to bind to socket on port 3801 14/04/11 17:39:57 TCP Listener unable to bind to socket on port 3500 14/04/11 17:41:11 MVAS thread running 14/04/11 17:41:53 ---> LogOff confirm 14/04/11 17:41:53 TCP connection on port 3801 closed gracefully 14/04/11 17:41:53 TCP connection on port 3500 closed gracefully 14/04/11 17:41:53 Client connections terminated 14/04/11 17:42:15 TCP Listener unable to bind to socket on port 3500 14/04/11 17:42:47 MVAS thread running 14/04/11 17:42:48 Received Master login confirm, new UDP port is 3559 Avatar_id = 1073750605 14/04/11 17:42:48 <server> Master Login received - UDP sector port: 3559 14/04/11 17:42:48 >> Commence Login check. 14/04/11 17:42:48 Sending Login packet - connection active 14/04/11 17:43:29 MVAS thread running 14/04/11 17:43:31 Received Master login confirm, new UDP port is 3559 Avatar_id = 1073751029 14/04/11 17:43:31 <server> Master Login received - UDP sector port: 3559 14/04/11 17:43:31 >> Commence Login check. 14/04/11 17:43:31 Sending Login packet - connection active 14/04/11 17:49:54 MVAS thread running 14/04/11 17:49:54 Received Master login confirm, new UDP port is 3559 Avatar_id = 1073750605 14/04/11 17:49:54 <server> Master Login received - UDP sector port: 3559 14/04/11 17:49:54 >> Commence Login check. 14/04/11 17:49:54 Sending Login packet - connection active 14/04/11 17:50:04 >> Login check: Login OK 14/04/11 17:52:12 TCP Listener unable to bind to socket on port 3801 14/04/11 17:52:12 TCP Listener unable to bind to socket on port 3500 14/04/11 17:53:03 ---> LogOff confirm 14/04/11 17:53:04 TCP connection on port 3801 closed gracefully 14/04/11 17:53:04 TCP connection on port 3500 closed gracefully 14/04/11 17:53:04 Client connections terminated 14/04/11 18:00:46 TCP Listener unable to bind to socket on port 3801 14/04/11 18:01:03 MVAS thread running 14/04/11 18:01:03 Received Master login confirm, new UDP port is 3559 Avatar_id = 1073751029 14/04/11 18:01:03 <server> Master Login received - UDP sector port: 3559 14/04/11 18:01:03 >> Commence Login check. 14/04/11 18:01:03 Sending Login packet - connection active 14/04/11 18:01:13 >> Login check: Login OK 14/04/11 18:02:40 ---> Server handoff 14/04/11 18:02:41 Received Master login confirm, new UDP port is 3562 Avatar_id = 1073751029 14/04/11 18:02:41 <server> Master Login received - UDP sector port: 3562 14/04/11 18:02:41 >> Commence Login check. 14/04/11 18:02:41 TCP connection on port 3500 closed gracefully 14/04/11 18:02:41 Sending Login packet - connection active 14/04/11 18:02:42 Sending data file 'GalaxyMap.dat' 14/04/11 18:02:43 Sending StartAck to Server 9205 14/04/11 18:02:46 >> Login check: Login OK Quote Link to comment Share on other sites More sharing options...
Tienbau Posted April 15, 2011 Report Share Posted April 15, 2011 have you changed your firewall, or got an update to it or something like that? Perhaps there's something stopping the proxy from binding the relevant ports. The multi-box without VM is really just a glorified hack based on an even worse hack someone posted a while back. Also make sure you aren't using local cert too - that kills multi boxing. The other thing to try is to do a full check disk from the 'my computer' explorer pane. Quote Link to comment Share on other sites More sharing options...
jander38 Posted April 15, 2011 Author Report Share Posted April 15, 2011 [quote name='Tienbau' timestamp='1302833328' post='39149'] have you changed your firewall, or got an update to it or something like that? Perhaps there's something stopping the proxy from binding the relevant ports. The multi-box without VM is really just a glorified hack based on an even worse hack someone posted a while back. Also make sure you aren't using local cert too - that kills multi boxing. The other thing to try is to do a full check disk from the 'my computer' explorer pane. [/quote] nope, nothing has changed..... it's been working fine (dual box) i even tried today disabling the firewall completly.. a CTD caused it to act up today.. local cert doesnt work and never use it.... as for a full check disk? what for? doubt any thing w/ the OS changed to a game crashing. Last time this happened.... i just went 2 bed and next day it was resolved.... but i'd like to figure out what's causing it and try 2 stay away from the scenario all together. Thanks for the heads up. Quote Link to comment Share on other sites More sharing options...
Strayslayer Posted April 15, 2011 Report Share Posted April 15, 2011 (edited) When I multi-box on the same pc, this sometimes happens to me. I close the command prompt associated with that avatar and relaunch net-7 proxy. I'm using win7 x64 as well. I initially had issues when I first started boxing and just letting my command prompt windows build up, but for the last month or so if one of my characters crashes I just restart the whole process. It costs me at most 2 minutes of play time before I have the toon back in, grouped, buffed, and the null item bug taken care of. K.I.S.S. Is my motto. Edited April 15, 2011 by Strayslayer Quote Link to comment Share on other sites More sharing options...
jander38 Posted April 15, 2011 Author Report Share Posted April 15, 2011 wish it was that easy for me... nothing i try gets me back in when this happens Quote Link to comment Share on other sites More sharing options...
Strayslayer Posted April 15, 2011 Report Share Posted April 15, 2011 Hmmm, I'm sorry to hear that. hang in there, tienbau will get you figured out soon. Quote Link to comment Share on other sites More sharing options...
garblesoup Posted April 15, 2011 Report Share Posted April 15, 2011 [quote name='Boogieman' timestamp='1302836843' post='39153'] as for a full check disk? what for? [/quote] Because others, in other threads, have reported that this resolved their issue. It doesn't make sense, I agree, but that's what some have said resolved their issue. Quote Link to comment Share on other sites More sharing options...
jander38 Posted April 16, 2011 Author Report Share Posted April 16, 2011 Afternoon, The fix once again was to go to bed and try next day. Same results the last time this happened... oh well?? @ least dual boxing is working for me again. Quote Link to comment Share on other sites More sharing options...
jander38 Posted April 16, 2011 Author Report Share Posted April 16, 2011 lmao... now i try again today and same issue................ i give up unable to bind [IMG]http://i1097.photobucket.com/albums/g359/jander4172e/1.jpg[/IMG] Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.