Jump to content

Alaestor

Grand Master
 View Profile  See their activity

  • Posts

    209

  • Joined

  • Last visited

 Content Type 

Posts posted by Alaestor

    [Temporary Workaround Found] Unable to login in-game

    in General

    Posted · Edited by Alaestor
    MOAR NEXTS!! SO MANY MORE NEXTS!!

    SIMPLIFIED TEMPORARY WORK-AROUND

    Okay, I've written two CMD / batch scripts as they seem to be in high demand. They should only work if the services are installed in the first place.

    I still recommend waiting for the next next next next next next next next next patch!  screw it; they don't know what they're doing...

    but I understand some people badly want to play. (edit: why? Just leave. They don't care. warframe is horrible)
    Know that you are taking a risk by doing this workaround. Exposing both your system, and the network you're on.

     

    • One to turn the services on as they are needed (makes your system insecure! read the prompt carefully!)
      workaround_ON.bat
       
    • and One to turn the services off once you've logged into warframe. (this will make your system secure again)
      workaround_OFF.bat

     

     

    !!! CAUTION !!! 

    remember to run the "workaround_OFF.bat" after you log in. If the " workaround_ON.bat " fails, you still need to run "workaround_OFF.bat" to be secure!

    edit: if you aren't experiencing this bug, running these bat files may do more bad then good. These aren't security tools.

     

    How To Use Them Safely

    For this to work, the " workstation " service must not be manually set to "Disabled". 
    Search and run the " services.msc ", find the " Workstation " service, double click it, and set the startup type to manual.

    Either download the scripts from the site, or copy+paste them into " .bat " extension files.
    In order to rename the file extensions, you may need to show file extensions if you haven't already.

    Once you have BOTH files:

    1. run the " ON " script (as admin, meaning you need to right-click it).
    2. run the warframe launcher, launch warframe, and log in as you normally would.
    3. run the " OFF " script (as admin)

    If either of the scripts fail, please message me (Alaestor) via my public discord server.
    If only the " OFF " script fails, contact me A.S.A.P. and I'll personally try to help you get it secure again and figure out what went wrong.

     

    These scripts have only been tested on windows 7 professional. I can't confirm if they work on anything else, but in theory they should...

     

    old workaround:

    Spoiler

    ferpgl.png

    • Like 1

    [Temporary Workaround Found] Unable to login in-game

    in General

    Posted · Edited by Alaestor
    rephrased

    4 minutes ago, rusnoob said:

    better just wait for the hotfix,the weekend passed and DE Will start to work

    If you fan his file, it turned on things you don't want. Please run cmd.exe as admin and type these commands to turn them off

    Quote
    1. sc config mrxsmb20 start=disabled
    2. sc config mrxsmb10 start=disabled

     

    [Temporary Workaround Found] Unable to login in-game

    in General

    Posted · Edited by Alaestor
    edit: i'll try to keep the link to the work-around near the latest posts

    4 minutes ago, LeXendZ said:

    Just wondering, if people dont mess with services how is it disabled 

    Good OEMs will likely disable it out of the box for home users, and some anti-threat (anti-malware / virus / ransomware / etc) systems will also nuke vulnerable services to reduce the attack surface of a given machine. edit: also some auto-optimization systems will disable unused services to free up system resources.

     

    For those browsing the thread:

    PLEASE READ THIS FOR THE TEMPORARY WORK-AROUND

    (note, this does cause a security risk. read carefully)

    [Temporary Workaround Found] Unable to login in-game

    in General

    Posted

    Just now, TheUglyOne89 said:

    Man, this is Day 3 of the update and I still can't log in. Is there any news that dev is aware of this and is working to fix it? 

    I am not using the workaround, nor I intend to, security is bigger priority for me than this game.

    Thankfully, Glen has stated that a fix is in the pipeline, and should be arriving with the next hotpatch (regular patching schedule, i believe) 

    [Temporary Workaround Found] Unable to login in-game

    in General

    Posted · Edited by Alaestor

    20 minutes ago, IlKaithe said:

    Im just... sad. Planned to sink in deep for 2 days in WF, as im most likely not going to have time during the week.First couldn't log in, so waited for hotfix while enjoying the update through streamers... Then couldn't link accounts till late night saturday. Then hotfix dropped, but turns out I still cant log in - same problem as described in this thread. Im not going to use workstation workaround just to play WF, sorry but I prefer to keep my bank accounts safe... Now its 6pm, sunday, I hoped when I wake up today it's going to be fixed... but it's slowly getting late, and no signs of fix on the horizon :/ Oh well... FeelsBadMan

    I know the feels. My network is secure so I don't mind turning it on to log in then instantly stopping it, but if you're on a public network or in a house with other computers, or a non-strict firewall (or no fire wall), then it becomes a very big issue. Especially! if you need to use SMB 1.0 ... If it works with SMB 2 or 3, then you're fine(ish). But there have been some people who had issues starting workstation without also enabling SMB 1.0 (but that's quite rare...)

     

    [Temporary Workaround Found] Unable to login in-game

    in General

    Posted

    2 minutes ago, 7NYLO7 said:

    I use Windows 7, and I've been playing just fine for years now without this 'SMB protocol' BS. I'm getting the same error which I guess is good 'coz I thought I was the only one, but I was still looking forward to this update and now I can't even experience it? This better be some sort of mistake and it needs to be fixed ASAP :I

    They will. for now, you can follow the temporary work-around guide i assembled.

    [Temporary Workaround Found] Unable to login in-game

    in General

    Posted

    1 minute ago, Namaste34 said:

    it's really working!!!! THANK YOU SO MUCH

    That opens you to a lot of known remote exploits and makes your computer very vulnerable. 

    Please remember to deactivate workstation when you're finished logging in, and when the hotfix is released please type this into CMD

    Quote

    sc config mrxsmb10 start=disabled

     

    [Temporary Workaround Found] Unable to login in-game

    in General

    Posted

    2 minutes ago, Yonael said:

    Is the hotfix out yet or is it still inbound?

    My understanding is that it will be patched on the regular hotfix schedule 

    Until then, I've written a semi-safe temporary work-around guide. 

     

    ... Some others are asking people to run batch files that will only work on specific versions, and don't tell people about disabling the services afterwards...

    Ugh. This is why a bug like this is a problem.  

    [Temporary Workaround Found] Unable to login in-game

    in General

    Posted

    3 minutes ago, yakrevedko said:

    and save as Ivan.cmd

    lmfao im dyin...

     

    Anyways; it isn't named lanmanworkstation consistently across all versions of windows, and there are some prerequisites that some people may need first. This batch file isn't a very good solution, ALSO you don't tell people to turn it off when they're not using it. Which you should.

     

    ---

     

    PLEASE READ THIS FOR THE TEMPORARY WORK-AROUND

    (note, this does cause a security risk. read carefully

    [Temporary Workaround Found] Unable to login in-game

    in General

    Posted · Edited by Alaestor
    Linked to batchfiles

    TEMPORARY WORK-AROUND

    This is the manual method (and is slightly inaccurate and NetLogon and Server aren't required).

    Click Here for the "on" and "off" batch files.

     

     

    A hotfix patch is on the way... But in the meantime 

    If you are experiencing issues, the problem is the Workstation service, the Server service, and the NetLogon(?) service.

    Enable them (in the "services.mcs" application), launch the game, log in, and then disable them. (it's only required to log in.)

     


    If you are getting the "error 1068" message when trying to start the workstation service, we found a "FIX" for that too...

    Spoiler

     

     Begrudging Thanks to @plusman for solving the error '1068' (missing dependencies) when enabling the workstation service.

     

    This solution exposes your PC to security threats that it would otherwise not be vulnerable to. Please read all the steps carefully!

    You really really really shouldn't do this... But if you are desperate to play...

     

    The solution is to enable SMB 2, (or sometimes SMB 1.0 dear lord help us all ) and enable the workstation service.

    Both SMB 1.0 and 2.0 have known exploits which exposes you (and probably everyone on your network) to very bad things.

     

    TO DO THIS SAFELY or at least partially less stupidly

    1. in the "services.mcs" application, make sure "Network Store Interface Service" is enabled.
      If you can start the workstation service now, skip to step 6
       
    2. in the "services.mcs" application, make sure "Server" service is enabled.
      If you can start the workstation service now, skip to step 6
       
    3. in the "services.mcs" application, make sure "Netlogon" service is enabled. (required?)
      If you can start the workstation service now, skip to step 6
       
    4. run "cmd.exe" as admin and type " sc.exe config mrxsmb20 start=demand " (without quotes) and reboot your pc.
      If you can start the workstation service now, skip to step 6
       
    5. run "cmd.exe" as admin and type " sc config mrxsmb10 start=demand " (without quotes) and reboot your pc
      workstation should start now... If not, I'm out of ideas.
       
    6. launch warframe and log in and disable the workstation service. (it's only required to log in.)


      IF YOU USED STEP 4 when the hotfix arrives...
    7. run "cmd.exe" as admin and type " sc config mrxsmb20 start=disabled " (without quotes) and reboot your pc

      IF YOU USED STEP 5 for the love of everything... when the hotfix arrives...
    8. run "cmd.exe" as admin and type " sc config mrxsmb10 start=disabled " (without quotes) and reboot your pc

    tenor.gif

     

     

    [Temporary Workaround Found] Unable to login in-game

    in General

    Posted · Edited by Alaestor

    32 minutes ago, plusman said:

    I also sufferd from the same error '1068'.

    sc config mrxsmb10

    TBH, I don't recommend this solution untill deploy the hotfix as @Alaestor said.

    I confirmed. The arguments you passed to sc (specifically regarding mrxsmb10.sys) is indeed re-enabling the SMB 1.0... Why is that required? Are you on windows vista?


    Regardless: Everyone... Please... Don't do that...

     

    THIS IS WHY THIS BUG IS A PROBLEM! 

    Some people want to play warframe so badly they will compromise their own security and re-enable the rightfully disabled protocols, as if having SMB on in general wasn't bad enough. I kind of expected it to happen, but to see an example in this thread for my own eyes is depressing.

     

    Jeez, I can't wait for this to be fixed...

    [Temporary Workaround Found] Unable to login in-game

    in General

    Posted · Edited by Alaestor

    16 minutes ago, plusman said:

    means restore default startup configuration for SMB 1.x MiniRedirector

    I feel extremely uneasy to see anything regarding SMB 1.... I'm not educated what that "mini redirector" is... Hopefully just a wrapper for SMB 2 or 3... But dear god I hope it's not actually enabling SMB 1.0 - frankly, I wouldn't risk it, just to be safe.

    [Temporary Workaround Found] Unable to login in-game

    in General

    Posted

    2 minutes ago, DustyB216 said:

    I remember him saying that he is tracking down problem caused by people logging into the game with this workaround method. He didn't say anything about fixing this.

    he said: 

    Quote

    I have tracked down at least one problem that was caused by people disabling windows services and it'll be fixed in the next hotfix. 

    rephrased: People who had windows services (workstation) disabled arre experiencing problems, and it will be fixed in the next hotfix.

    Whether or not the problem he found and fixed is the actual cause of this, we'll only know after the hotfix.

    [Temporary Workaround Found] Unable to login in-game

    in General

    Posted · Edited by Alaestor

    He already said a fix will come out with the next hotpatch... that's a lot, considering it's the only thing we've heard from DE directed at this problem aside from "oh its fixed durp".

     

    I recommend not pestering him further :D I'm just glad we got any feedback at all. I was getting pissy. There's not much he can say with regards to the windows issues that are unrelated to WF. Just be patient, wait, and hope.

    [Temporary Workaround Found] Unable to login in-game

    in General

    Posted · Edited by Alaestor

    1 minute ago, OroDoom said:

    i Search so much for Workstation Start Error 1068 . and i found nothink in internet to fix this 

    i Just want to play warframe . maybe they don't have Time to Fix this but this realy Unfair 

    Players Having Fun with the new updated and others suffering From a POE FAULT .

    Help us. 

    Glen's already working on a fix. Hopefully it will work.

     

    But don't worry! ... POE is buggy as crap right now :D you aren't missing much 

    (not tooooo buggy, but... many people crashing and glitching etc)

    [Temporary Workaround Found] Unable to login in-game

    in General

    Posted

    Just now, alaris10 said:

    Tbh i dont understand what you are talking about. I just dont have thing that SMB 1.x MiniRedirector depend on, SMB MiniRedirector Wrapper and i dont see either of them in services list.

    Uhm, sorry... that was my reply to someone else, unrelated to your issue. I'm not sure what Workstation depends on... (Server? maybe?) sorry xD no clue... and... dont run SMB 1 anything...

×
×
  • Create New...