Login then game closes/crashes

[rpyke88]

Hey the game worked fine before the server crash for me today, but now when I go to login it crashes right after i enter my login details. I didn't mess with any settings, so im wondering what this might be, thanks.

[Steptowalk69]

Everytime I try to login and the server is up... I put my login info and stuff correctly.. then the game closes but the dos program still remains up

[C Del[IS]]

Try the fixes outlined here:

https://enb-emulator.com/index.php?/forum-56/announcement-13-read-first-technical-support-faq-and-common-fixes/

Thanks,

C Del

[Falstar [MOD]]

Merged similar topics

[Guest omorbpw]

I wonder if this will ever be fixed? this happens to me each and everytime since 2 patches ago. I have reinstalled netproxy and client to no avail. I must reset updates to be able to log in each time and I still get error message on every combat job kill. I have tried all of Del's suggestions to no avail. Please look into.

thanks

[C Del[IS]]

The only way I can see to solve this is to verify all of your client files every time you start the game, and that's not exactly desirable, because it would cause the launching process to consistently longer. Please post/keep posting the update reports you get when you reset and check for updates; I'm trying to figure out if there's a pattern to which files are being corrupted.

[Guest omorbpw]

Well ok then.. here we go:

Data/client/mixfiles/mixfile_art_02.th6

Data/client/mixfiles/mixfile_art_03.th6

Data/client/mixfiles/mixfile_art_08.th6

Data/client/mixfiles/mixfile_art_10.th6

Data/client/mixfiles/mixfile_art_11- thru 20.th6

Data/common/network.ini

Data/common/network.ini.orig

release/authlogin.log

Seetms to be the same files over again!

thanks

[fuulishone]

Have you considered running a hard drive check? If you're consistently having trouble with the same files, it may be because there's something corrupted on the hard drive. A real simple test would be to run chkdsk on the drive. Another possibility is to reinstall the game, but on a different drive. Lastly, you *could* try to launch the net7proxy with debug launch checked and see if the proxy encounters something at run time.

[Guest omorbpw]

I have run chkdsk .. no failures.. I have re-installed everything, but no on a diff drive.. I will try your last suggestion

thanks

[Guest omorpw]

With debug on, this is what i get.

C:\NET7\bin>cd "C:\NET7\bin"

C:\NET7\bin>"C:\NET7\bin\Net7Proxy.exe" /ADDRESS:87.106.15.67 /CLIENT:"C:\PROGRA

~2\EAGAME~1\EARTH&~1\release\client.exe" /POPT /DEBUGL

Net7Proxy version 1.76

Params: /ADDRESS:87.106.15.67

Params: /CLIENT:C:\PROGRA~2\EAGAME~1\EARTH&~1\release\client.exe

Params: /POPT

Params: /DEBUGL

Using IP: 127.0.0.1 (127.0.0.1)

12/04/10 12:19:33 Attempting to connect to IP address: 87.106.15.67

12/04/10 12:19:33 Sending login.

12/04/10 12:19:34 login OK

12/04/10 12:19:34 Starting E&B...

12/04/10 12:19:35 Launch E&B successful

12/04/10 12:19:35 UDP packet optimisation selected (reduces server load).

12/04/10 12:20:11 MVAS thread running

12/04/10 12:20:11 Received Master login confirm, new UDP port is 3665 Avatar_id

= 1073743370

12/04/10 12:20:11 <server> Master Login received - UDP sector port: 3665

12/04/10 12:20:11 >> Commence Login check

12/04/10 12:20:11 Sending Login packet - connection active

12/04/10 12:20:12 TCP connection on port 3500 was reset

12/04/10 12:20:12 TCP connection on port 3801 was reset

12/04/10 12:20:12 Client connections terminated

12/04/10 12:20:16 Client has terminated. Sending termination signal.

TCP Listener Thread exiting

TCP Listener Thread exiting

[fuulishone]

With debug on, this is what i get.

C:\NET7\bin>cd "C:\NET7\bin"

C:\NET7\bin>"C:\NET7\bin\Net7Proxy.exe" /ADDRESS:87.106.15.67 /CLIENT:"C:\PROGRA

~2\EAGAME~1\EARTH&~1\release\client.exe" /POPT /DEBUGL

Net7Proxy version 1.76

Params: /ADDRESS:87.106.15.67

Params: /CLIENT:C:\PROGRA~2\EAGAME~1\EARTH&~1\release\client.exe

Params: /POPT

Params: /DEBUGL

Using IP: 127.0.0.1 (127.0.0.1)

12/04/10 12:19:33 Attempting to connect to IP address: 87.106.15.67

12/04/10 12:19:33 Sending login.

12/04/10 12:19:34 login OK

12/04/10 12:19:34 Starting E&B...

12/04/10 12:19:35 Launch E&B successful

12/04/10 12:19:35 UDP packet optimisation selected (reduces server load).

12/04/10 12:20:11 MVAS thread running

12/04/10 12:20:11 Received Master login confirm, new UDP port is 3665 Avatar_id

= 1073743370

12/04/10 12:20:11 <server> Master Login received - UDP sector port: 3665

12/04/10 12:20:11 >> Commence Login check

12/04/10 12:20:11 Sending Login packet - connection active

12/04/10 12:20:12 TCP connection on port 3500 was reset

12/04/10 12:20:12 TCP connection on port 3801 was reset

12/04/10 12:20:12 Client connections terminated

12/04/10 12:20:16 Client has terminated. Sending termination signal.

TCP Listener Thread exiting

TCP Listener Thread exiting

Can you try something with the game and net7 launcher/proxy NOT running?

Get a command prompt up and type: "netstat -an | more"

Basically looking for something that's running that might be nuking your connection. Like maybe a torrent, or something else that requires the same ports as net7proxy.

[Guest omorbpw]

C:\Users\Best Buy>netstat -an |more

Active Connections

Proto Local Address Foreign Address State

TCP 0.0.0.0:135 0.0.0.0:0 LISTENING

TCP 0.0.0.0:445 0.0.0.0:0 LISTENING

TCP 0.0.0.0:912 0.0.0.0:0 LISTENING

TCP 0.0.0.0:990 0.0.0.0:0 LISTENING

TCP 0.0.0.0:5357 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:49158 0.0.0.0:0 LISTENING

TCP 127.0.0.1:5354 0.0.0.0:0 LISTENING

TCP 127.0.0.1:5679 0.0.0.0:0 LISTENING

TCP 127.0.0.1:7438 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:49166 ESTABLISHED

TCP 127.0.0.1:49162 0.0.0.0:0 LISTENING

TCP 127.0.0.1:49166 127.0.0.1:27015 ESTABLISHED

TCP 127.0.0.1:49173 127.0.0.1:49174 ESTABLISHED

TCP 127.0.0.1:49174 127.0.0.1:49173 ESTABLISHED

TCP 127.0.0.1:49175 127.0.0.1:49176 ESTABLISHED

TCP 127.0.0.1:49176 127.0.0.1:49175 ESTABLISHED

TCP 192.168.1.2:139 0.0.0.0:0 LISTENING

TCP 192.168.1.2:50347 96.17.108.16:80 CLOSE_WAIT

TCP 192.168.1.2:51065 69.63.180.43:80 ESTABLISHED

TCP 192.168.1.2:51239 72.14.213.191:80 TIME_WAIT

TCP 192.168.1.2:51260 69.63.181.12:80 TIME_WAIT

TCP 192.168.1.2:51261 96.17.108.160:80 TIME_WAIT

TCP 192.168.1.2:51262 96.17.70.72:80 TIME_WAIT

TCP 192.168.1.2:51263 96.17.108.27:80 TIME_WAIT

TCP 192.168.1.2:51273 87.106.15.67:3805 TIME_WAIT

TCP 192.168.5.1:139 0.0.0.0:0 LISTENING

TCP 192.168.136.1:139 0.0.0.0:0 LISTENING

TCP [::]:135 [::]:0 LISTENING

TCP [::]:445 [::]:0 LISTENING

TCP [::]:990 [::]: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 [::]:49158 [::]:0 LISTENING

TCP [::1]:5679 [::]:0 LISTENING

TCP [::1]:49163 [::]:0 LISTENING

TCP [fe80::d92a:a716:fac5:b273%11]:445 [fe80::5d91:5036:57d4:6667%11]:4952

4 ESTABLISHED

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:59224 *:*

UDP 0.0.0.0:59226 *:*

UDP 127.0.0.1:1900 *:*

UDP 127.0.0.1:55922 *:*

UDP 127.0.0.1:59236 *:*

UDP 127.0.0.1:60667 *:*

UDP 192.168.1.2:137 *:*

UDP 192.168.1.2:138 *:*

UDP 192.168.1.2:1900 *:*

UDP 192.168.1.2:5353 *:*

UDP 192.168.1.2:59233 *:*

UDP 192.168.5.1:137 *:*

UDP 192.168.5.1:138 *:*

UDP 192.168.5.1:1900 *:*

UDP 192.168.5.1:5353 *:*

UDP 192.168.5.1:59235 *:*

UDP 192.168.136.1:137 *:*

UDP 192.168.136.1:138 *:*

UDP 192.168.136.1:1900 *:*

UDP 192.168.136.1:5353 *:*

UDP 192.168.136.1:59234 *:*

UDP [::]:123 *:*

UDP [::]:500 *:*

UDP [::]:3702 *:*

UDP [::]:3702 *:*

UDP [::]:5355 *:*

UDP [::]:59225 *:*

UDP [::]:59227 *:*

UDP [::1]:1900 *:*

UDP [::1]:5353 *:*

UDP [::1]:59231 *:*

UDP [fe80::100:7f:fffe%10]:1900 *:*

UDP [fe80::100:7f:fffe%10]:59232 *:*

UDP [fe80::30cb:fcbb:c200:8b19%15]:1900 *:*

UDP [fe80::30cb:fcbb:c200:8b19%15]:59230 *:*

UDP [fe80::3c7a:1b6a:625b:59d4%13]:1900 *:*

UDP [fe80::3c7a:1b6a:625b:59d4%13]:59229 *:*

UDP [fe80::d92a:a716:fac5:b273%11]:1900 *:*

UDP [fe80::d92a:a716:fac5:b273%11]:59228 *:*

[fuulishone]

c:\users\bestbuy ??

If this is a work machine, perhaps there's something on there that's preventing your connection from staying up and happy? Also, I'm guessing Windows 7, so you may need to double/triple check that you're running as Administrator and/or have turned on xp compatibility for the various executables.

[Guest omorbpw]

It is not a work machine, and is Vista not Windows 7, although who can really tell the difference. Everything has been checked and double checked. I have been running same setup since ST3, so nothing has really changed. this all start with 2 patches ago, up till then all was well.

thanks

[fuulishone]

Yeah, I agree about the two patches ago. I started having connection stability issues too, but not to the extent you're having. It feels like something is just real unhappy in the network layer, but I'm at a loss as to what that might be. Might be time to bring in an SDEV or whomever it is that's responsible for the proxy.

[TheZidaneTribal]

Just tried to play this today and ran into the same thing ending with the "TCP connection on port 3500 was reset" thing. Tried reinstall and the common fixes and thus far get the same result. Looks like the exact same problem.

[TheZidaneTribal]

Ok guys...got it up and working with few issues for the past couple days. First off, ALWAYS make sure you run the net7 launcher as admin if you're running vista. I had to check secure auth box, packet optimization, and the local cert boxes. After that, I had to reset updates and do them all again. I'm thinking maybe I forgot to run the net7 updates as admin...because checking all those boxes still got me the same result until I did the reset updates thing. Hopefully this will help with some troubles.

[Shuichii]

I have this problem too. Each time I close the game i have have to run launcher >> reset updates, each time i start the net7 again. If i don't then after putting in my password it crashes

[KapitaenM]

These files never seem to want to "stay" updated on my Windows 7 installation:

mixfile_art_02.th6

mixfile_art_03.th6

mixfile_art_08.th6

mixfile_art_10.th6

mixfile_art_11.th6

mixfile_art_12.th6

mixfile_art_13.th6

mixfile_art_14.th6

mixfile_art_15.th6

mixfile_art_16.th6

mixfile_art_17.th6

mixfile_art_18.th6

mixfile_art_19.th6

mixfile_art_20.th6

also, authlogin.log

Edited July 5, 2010 by Kapitæn M.

[dnmckinney]

Ok guys...got it up and working with few issues for the past couple days. First off, ALWAYS make sure you run the net7 launcher as admin if you're running vista. I had to check secure auth box, packet optimization, and the local cert boxes. After that, I had to reset updates and do them all again. I'm thinking maybe I forgot to run the net7 updates as admin...because checking all those boxes still got me the same result until I did the reset updates thing. Hopefully this will help with some troubles.

That did it! WOOT! I've been fighting the same problem but as a new user. I have Win 7, also. Still, if people do what you did, that ought to sort it out.

I am sooo stoked to be playing e&b again.

[Exolis]

Is there anything else to do? I tried the Settings to NET7 that was said, running in Admin and XP (SP3) compatibility. I had it running before when I had XP installed, but I have 7 Now. But it happens when I select a character and the loading screen comes up. And seems as 1/3 of the Screen has two big squares that looks to be like westwood logos that has 2 arrows. One going L to R and T to B.

[Tienbau]

Ok guys...got it up and working with few issues for the past couple days. First off, ALWAYS make sure you run the net7 launcher as admin if you're running vista. I had to check secure auth box, packet optimization, and the local cert boxes. After that, I had to reset updates and do them all again. I'm thinking maybe I forgot to run the net7 updates as admin...because checking all those boxes still got me the same result until I did the reset updates thing. Hopefully this will help with some troubles.

could you try without local-cert and see if it works - you shouldn't need to use local-cert. It's an emergency option I added when the server cert wasn't valid. You'll find with local-cert you are unable to change characters without quitting and restarting.

[C Del[IS]]

Try setting it to compatibility mode for Windows XP SP2 (make sure you're doing this to client.exe) and try running the E&BConfig tool' (in the Earth & Beyond\EBCONFIG director) performance test.

[Shuichii]

in addition to always having to reset my updates each time i wanna start up the game again I always lose my key binds, they are reset to default. I'm not sure if that has to do with the constant reset of updates or not.

*Edit* Local-cert didn't work, I turned on the Debug mode and now I'm able to log on without reseting update.

Edited July 7, 2010 by Shuichii

[Orga1]

It is not a work machine, and is Vista not Windows 7, although who can really tell the difference. Everything has been checked and double checked. I have been running same setup since ST3, so nothing has really changed. this all start with 2 patches ago, up till then all was well.

thanks

I might be in the same boat as you...

Have you rolled back or uninstalled any updates from M$ and/or updates to your drivers, sense the time you started experience these problems? Assuming you use Nvidia as your video card? Or did you search for similar Win7 user's on a M$ forums thing with the same problem? If it's not the client or it's files and it's not a hardware problem then it must be some crappy updates or compatibility issues with software for Win7. That's what I can think of.