I have experienced this issue as well. The usual response is to check to see if the necessary UDP/TCP ports are open. If you are playing on a PC and a recent version of Windows is your O/S, then those ports are usually opened by the application that needs them. I was getting the "you have been disconnected from the session" problem. The usual help response is to check the ports. This did not help me at all. I open up the suggested ports (both UDP and TCP) to no avail. What worked was uninstalling Origin altogether and re-installing it. But, I do get this particular error message from time to time as well. This is uually not related to Windows opening the correct ports or a firewall blocking data on those ports. Most firewall programs will inform the user if a application has been blocked. And the user has the option to allow access. Sometimes clearing DNS entris can be helpful. One must use the "IPCONFIG" and "NETSH" command line prompt w/admin level access to accomplish this. Resetting one's router may also help. If these steps don't work, then it is most likely a network issue upstream from the user's host machine. Possibly a TTL issue with the routers on the pathway to EA's servers. Which would help explain why it is an occasional issue rather than a persistent one. If it is persistent then one may want to contact their ISP.
EA Staff (Retired)Hello @MoonUtonight and thank you for sharing your knowledge with us here. We all know, how tiresome it can be to track down some connection issues on PC. And indeed ISP can be a culprit sometime, but trying some basic connection troubleshooting first can never hurt.
Cheers,
Archi
I agree. However, that has never been the issue that actually caused the problems for me. I have found the issue to be either corruption in Origin's files and/or BF1's files that the repair tool didn't fix.
I have not seen the "you have been disconnected from the server" for quite some time now. The last instance was prior to the update and new map. But, I was having an issue where BF1.exe would cause the game to crash. This one was quite exasperating. But, I think I have fixed it. At first I checked the forums and EA help for answers. The suggestions were that I disable Origin in game, change the way Windows handles the paging file. And running CHKDSK /F (from the cmd prompt with admin level privilege. Restarting the PC and allowing chkdsk to run. This seemed to fix the problem on a temporary basis. The game would run fine for a few days, and then it would crash again with the same info found in event viewer: BF1.exe caused a fault in a certain module. I had messed with various settings in Windows to see if any of them would resolve the problem. Including changing graphics settings to "performance". Well, what I didn't know is that this may have caused BF1.s graphics settings to revert back to DX11. I hadn't changed back to DX11 because I am running Win10 Pro w/DX12. DX12 is better with games than DX11 was. So, I changed back to DX12 and also changed graphics settings to "high" rather than "ultra" I also tried changing how many processors could be used from 12 (12! rather odd given I have Ryzen 1700x w/8 processors). But this is a setting you would have to change everytime you play. I have not had the game crash since I reverted back to DX12. You can try limiting frame rate, which I did. To 144 which goes along with my monitor's ability to do 144hz refresh rate. There are a lot of settings that can effect BF1. It can be kind of a easter egg hunt to determine what is causing one issue or another. Anyway, I hope this helps someone out there.
