Kyp

I would tell Avast to set an exception over all the related folders for Net7 and the E&B client. Avast can get overzealous about blocking applications that are not code signed. While the E&B executable itself is signed, basically nothing else is because it's an extra expense and maintaining a public cert for that purpose when the exceptions will eliminate it trying to do that. It's trying to protect you from yourself so you're not just running some code from the internet.

It sounds like packets are being dropped and not delivered either to or from us. There's not much we can do but if you want to attempt taking a packet capture we might be able to help confirm what's happening from that.

Depends on the service, the game service uses a small range of ports and it's built into how the client itself works we just sorta attach to it and accept it.

Rough couple of years, honestly forgotten about it. I will have to look at the numbers. Open a PM with me so I don't forget this time, it's late and i'm about to be off to bed.

Avast -- which I also use, incidentally -- defaults to distrusting unsigned applications. This is the only reason it's flagging it, it categorizes such as PUPs (Potentially Unwanted Programs). If you feel like it's getting in the way just set it to ignore all of the E&B paths. We don't code sign the executables because it would be extra charges to maintain a public certificate for code signing for no useful benefit other than calming down overzealous virus protection.

that said, you provided it once before, but it didn't show anything that was failing at a network level, i'm pretty sure that capture was taken while you were on the other connection so we would need to redo it on the "old internet" that seems to work. It's all going to boil down to what the provider is doing with the connection.

Use the option to delete TH6 files and see if that changes anything. Those files have to do with what you see in the sectors and if they get screwy it can cause them not to load or to have strange issues that's why the option is there. As for this whole thing with teredo tunnellng etc (Ipv6 -> 4 etc), the server will still allow you to connect but the game client may not play ball, ultimately i'd have to see a packet capture to try to determine what happened there if anything on our side of the conversation.

Alright so all I'm picking out (and it could be not enough coffee yet) is that your client side is sending an RST to end the connection with us after a response. This would seem to indicate that for sure you have the wrong version of LaunchNet7 at a glance. What was the version number your instance was showing? Also how are you currently connecting? I see you reported version 543 above which *seems* to match

Just tell it to capture everything over your LAN and then attempt to make the full connection until you run into the problem, then stop it and save a pcap or pcapng file to attach back for us. It might be suggested to zip it up and put a password on it then PM me that for me to open it for review, it *could* contain more sensitive data than intended if something not properly encrypted.

This means something is wrong with the version of your Net7 launcher application, or it seems to be detecting as such. It could be something the broadband device is doing to connect you to their network. I would suggest -- if you're familiar with using Wireshark -- a packet capture that could be reviewed to understand what's going back and forth between you and our servers.

I hadn't yet installed Windows 11 because my last build has finally aged to the point where it can't yet upgrade so I am sorta End of Lifing my rig before I rebuild. That said, do they still have the option to run an executable in previous windows compatibility modes? Had you tried that for the E&B client.exe?

fixed again.

back up.

back up.

Navigate to the Net7 install directory Find the authlogin.dll file Delete or rename that file From launcher or tools menu in upper left there's a patch reset and/or fix option (sorry don't have it installed on the computer i'm replying from) choose that option and let it reset the patching and repatch everything That should take care of things.

It had an issue with the script that does this (it isn't human). I just fixed it and restarted it. It should be back in a few minutes.

Just restarted the game server, try again in about 5 minutes from this message. May have been kinda stuck with the issue that caused the website to be erratic this morning. Login server would possibly have been affected which might result in the above described message.

It's back.

Just to be clear, *we* (Net-7) can't distribute files over the original client without you acknowledging those changes and we can't change any copyright/trademark etc for anything that was originally part of Westwood/EA as part of what we deploy to you. That *does not* say that you cannot share these files or acknowledge and install them separately for improvements. We can certainly host that/those files if shared from the net-7.org site since it will link to wherever the author puts it / them as well as any additional mirrors set up.

Have to run the config utility, did you do that? Kinda a requirement for modern systems due to the age of the game.

Apologies, as Zackman indicates the disk array experienced a failed disk and the other went into a mode to protect the data. This was unfortunately the pair of disks that hosted our operating system. Unfortunately it means monitoring failed to alert me properly as to degradation of a disk but hey, it's back now. So.. plus side, everything should be ready to go again.

For a fastest resolution in the short term. Uninstall and reinstall the Net 7 Launcher but this will probably need some logs from the existing one in order to truly diagnose.

Yes, the outage last night was unintentionally caused by our data center vendor. As soon as ArthurDent hit me up to let me know, I sorted it out with them. Thanks @Arthurdent

if that doesn't do it you might also consider running an elevated command prompt i.e. So it says "Administrator: " at the front of the cmd window title bar and then running: dism.exe /online /cleanup-image /restorehealth This should cause it to check with your local component store and then MS to return you to the correct value for most/all system files for Windows with your installed version.

Try this (assuming the version of Windows is genuine): Stop the Windows Installer service and ensure it remains disabled (don't forget to turn it back on after testing): Navigate to this path on the computer(s): C:\Program Files (x86)\Common Files (or equivalent) Look for an InstallShield folder. Rename this to something like InstallShield 1 Reboot the computer and bring up the Windows Installer service. Try again and see if it repeats. 1628 is an error from the installshield installer saying the script setup failed to complete so it's either corruption in your local installshield files or a corrupt installation file.