C Del

Does LaunchNet7 say the server is online?

You may not have the .NET Framework installed. http://www.microsoft.com/downloads/details.aspx?FamilyID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5&displaylang=en

Any net7proxy babble about being unable to bind a listener?

Go to "C:\Documents and Settings\User\Local Settings\Application Data\LaunchNet7\LaunchNet7.exe_Url_33uz3155fe0lw51jyicbrfpxh3h01gh0\1.9.4.0", delete "user.config", and try again.

I have had this happen to me intermittently in the past, mostly on Vista/7. It always seems to work itself out.

Try using the Local Cert option in LaunchNet7. (You will need to change the host drop-down box to "Multiplayer (Custom)")

Do you mean to say that your internet doesn't work after EnB crashes, or simply that you can't reconnect to the Net7 server until you reboot?

I took the liberty of looking up your forum name in the database and it appears that you had an account registered as 'Vatta' and another as 'Lord Vatta'. You wouldn't have been able to log into the second of those accounts because any non-alphanumeric characters like spaces throw the login system off. I've changed 'Lord Vatta' to 'LordVatta'; try logging in with that username.

What is your account name?

You may not have the .NET framework installed: http://www.microsoft.com/downloads/details.aspx?FamilyID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5&displaylang=en

What version of Windows are you using? If it's anything after XP, make sure you're running LaunchNet7 as an Administrator. Other than that, this would seem to indicate data corruption. What kind of internet connection / setup do you have? (routers, firewalls, etc.)

I suggest you go to http://support.net-7.org and ask a GM to reset your password for you, just in case you accidentally entered the wrong password or the password you entered was recorded incorrectly for some reason.

Go ahead and try it now, I've activated your account.

The temp ban message means your account isn't activated. What is your account name?

Try selecting Multiplayer (Custom) and checking the Local Cert checkbox.

The E-Mail you're receiving must have been based off of the database before passwords were encrypted. What you're seeing is the encrypted data, from which your password can't be retrieved. If you still remember your password, go ahead and use it and it should be fine. Otherwise, if you have a couple of different passwords you use regularly, you can run them one-by-one through the encryption method we use and see which one matches that big, encrypted password you got with the E-Mail. There are a bunch of websites out there that will run the encryption for you, such as this one: http://www.miraclesalad.com/webtools/md5.php If you can't geuss your password that way, or don't feel like trying that, you can submit a GM ticket at http://support.net-7.org and a GM will reset your password for you.

There will probably be a post in the announcement forum when this is back up: https://enb-emulator.com/index.php?/forum/5-announcements/

I would pin this... but I don't appear to have moderator permissions. Can someone else do that for me?

Good question, lol. I'm sure there will be a post in the announcement section when they get it back up. I'm not sure, however, if there's a way to donate without the module set up...

Yeah, I've used that in the past and haven't had any problems. What version of VMWare (Workstation?) are you using?

Try deleting the folder "C:\Users\My User\AppData\Local\LaunchNet7"

If you're using Windows Vista/7, change the compatibility mode setting on client.exe. Then, go to Earth & ...\Beyond\EBCONFIG\ and run E&BConfig.exe, change your graphics settings to something in the mid-range and run the Performance Test. Finally, try to log in again.

The server is online at the moment. Do you have a firewall? If so, turn it off and try again.

This error indicates data corruption or loss. I experience this problem as well, and it is likely an issue on the server side. Try to bear with the server developers as they continuously work on the comms system.

Sorry, I can't be of much help with server issues. Try to hang tight, assuming it is in fact a server bug, I'm sure it's being worked on.