Jump to content

Kyp

Lead Developers [LDEV]
  • Posts

    6499
  • Joined

  • Last visited

  • Donations

    0.00 USD 

Posts posted by Kyp

  1. oh yeah, definitely has happened before. I get it, protect yourself. Zero trust is always a good thing if you can get there, but we have no plans to purchase and maintain a code signing cert to sign these applications at present because it's definitely not a constant problem.

  2. 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.

  3. On 12/15/2022 at 3:36 AM, mrtacoman511 said:

    OK so I tried both internets, air advantage succeeds but is not superfast..tmobil is however gets the failed sector map error..but succeeds with vpn on (not all can use port forwarding but mine can) but the connection is very laggy because theres too many ports open. At least i think..is there a way to use a specific port for enb? or does each thing use a different one like 3800 for sector map and 3000 for logging in etc.


    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.

  4. 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.

  5. 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.

  6. On 12/10/2022 at 4:57 AM, mrtacoman511 said:

    switched to my old internet today now it lets me login but crashes saying failed to load sector lol. at this point i think its safe to say I will never return. 

     

    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.

  7. 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

  8. 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.

  9. 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.

  10. 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?

    • 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.
  11. 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.

  12. On 5/20/2022 at 12:09 PM, jazzmag said:

    Hi all! just installed on:

    Win 10 x64

    Ryzen 5 5600x

    RTX 3070

    16gb DDR4 3200

     

    Run launcher (Admin+compatibility win7), update finished, Ran gfx config, tested config, click play, accept user agreement, get splash screen, drop to desktop...

    Only happens when I try to run full screen.

     

    Any ideas?

     

     

     

     

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

  13. 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.

×
×
  • Create New...