Tom Clancy's The Division
Delta c-1-200 error code FIX!!
It took me forever to finally fix this error. I've had this error for months now and I finally found a fix. In your router settings go to the firewall settings in the router and change the security level to minimum. I had mine on typical and when I changed it to minimum and launched the game it finally worked and I'm in the Base of Operations. I hope this helps and let me know if it does or doesn't.
< >
กำลังแสดง 1-15 จาก 43 ความเห็น
i just restarted my router to fix it
Well that'll do it i guess
I'll try. Thanks
โพสต์ดั้งเดิมโดย Reborn:
i just restarted my router to fix it
did you ever get it to work again?
โพสต์ดั้งเดิมโดย Reborn:
i just restarted my router to fix it
Did Restarting your router fix the error code????
If you're using antivirus software, allow the division to get through it's firewall setting. Doing this fixed my problem
Yeah,

This could be a fix if anyone ever gets this error in the future.

- Ubisoft Support
How do I change the firewall settings to minimal?
โพสต์ดั้งเดิมโดย Incarnated Autism:
How do I change the firewall settings to minimal?
go to the firewall and add it to the exception list
Don't think I fancy setting my firewall to minimal, make you more open to attacks.
IT DOESNT WORK
Whether this works, or how you do it, is totally dependent upon what router you use and what features it has.

I never had to do anything on my firewall, manually open ports, etc. and the game runs fine. But, I have a pfsense firewall with upnp enabled, and have done all the configuration bits to achieve "open nat" when testing with the win 10 xbox app.

You don't have to have a pfsense firewall to get nat type "open", but where I would start is finding out how one does get "open" nat type on your specific router.

If I were to guess, some routers have upnp disabled in their "maximum" or even default setup. That would be a good idea, because rule #1 in securing your network is you don't run services you do not need, and not everyone needs upnp.

The thing to know about running upnp, is that if you run that on your firewall and it is not configurable to limit it to certain ip address(es), that can be a big problem. Because if upnp is enabled for all ip's, and you install a device that is compromised (like perhaps a cheap ip video camera off ebay), which is designed to be a trojan that get s on your private net, and then uses upnp to provide a backdoor into your net.

The best practice when running upnp is to restrict it only to devices that have a valid need to open ports through upnp.

If one's router does not have a way to restrict upnp in this way, then my recommendation is to get a router that does..... or run a real firewall like pfsense.

In any event, if you get upnp running right, and properly secured, such that your NAT type is reported as "open" by the xbox app, then all your connection issues and problems in all your games will be gone.

Assuming of course that your gaming rig isn't on wireless and your wireless bandwidth is not saturated..... then you would continue to have problems. I never put gaming rigs or consoles on wireless... always wired.
Just do a "netsh winsock reset" and restart your PC, it just worked for me.
I have Avast Antivirus and I just added it to the "exception/allow" list. Worked for me.
New PC game wont start, old PC game works, same router. I will try firewall. already deleted and reinstalled uplay and steam and game files still same on new PC Division wont start.
< >
กำลังแสดง 1-15 จาก 43 ความเห็น
ต่อหน้า: 1530 50