CAT_101st Posted December 8, 2013 Posted December 8, 2013 Ok can someone explain this one to me. "Can't start server, error:-1004" I can log into ED net fine. And now I cant host a sever at all on my gaming rig. My sever PC is running with no problems. I have ben hosting 2 severs for quite some time. and today this just started. :cry: Home built PC Win 10 Pro 64bit, MB ASUS Z170 WS, 6700K, EVGA 1080Ti Hybrid, 32GB DDR4 3200, Thermaltake 120x360 RAD, Custom built A-10C sim pit, TM WARTHOG HOTAS, Cougar MFD's, 3D printed UFC and Saitek rudders. HTC VIVE VR. https://digitalcombatmercenaries.enjin.com/
CAT_101st Posted December 21, 2013 Author Posted December 21, 2013 um hello no answer from anyone. Home built PC Win 10 Pro 64bit, MB ASUS Z170 WS, 6700K, EVGA 1080Ti Hybrid, 32GB DDR4 3200, Thermaltake 120x360 RAD, Custom built A-10C sim pit, TM WARTHOG HOTAS, Cougar MFD's, 3D printed UFC and Saitek rudders. HTC VIVE VR. https://digitalcombatmercenaries.enjin.com/
riboyster Posted January 4, 2014 Posted January 4, 2014 bump -SnakeShit [sIGPIC][/sIGPIC] Peace through Superior Firepower EVERYTHING YOU'LL EVER NEED FOR LOMAC: http://flankertraining.com/ironhand/news.html
Hiccup Posted April 13, 2014 Posted April 13, 2014 I ran into the same error code (error -10049) today after relocating my computer and trying to host a MP mission. The error led me to look at my network.cfg file (C:/Users/username/Saved Games/DCS/Config). The suspect "interface" line in that file contained the correct static IP I had previously assigned to my PC from my router. When I checked my router, it still showed that static mapping to my PC's MAC address. When I then did an "ip config" from the DOS prompt and saw the actual assigned IP address, I realized the router had assigned my PC a different, dynamic IP address. Then it hit me that my motherboard has two Ethernet ports (each with a different MAC, of course) and I had plugged the Ethernet cable into the "wrong" port. Once I plugged into the other Ethernet port, everything worked fine again. Out of curiosity, I plugged the cable back into the "wrong" port and replaced the IP address in the network.cfg file to the one my router had dynamically assigned to that Ethernet port, and was also able to host a MP mission with no problem.
Recommended Posts