reddwarf 0 Posted June 25, 2003 Hey folks This is kinda hard issue i am having with repairing the SES squad's dedicated server. The server runs for 10 seconds than returns: unable to start dedicated server: 2302 wonder if anyone had ever saw that message or perhaps have a hint where the bug could be? information: -linux redhat 9.0 running EXT3 fs -the udp port 2302 is opened for those 10seconds only, then closes -the server worked fine before one simple restart -we tryed changing the OS to win2K => same problem which is completely surnatural to me. -i don't think its a hardware problem.. its a well cooled 2.6Ghz athlon with 1GBram -yeah and in order to use the maximum ressources, there are only ofpserver and TeamSpeak server running there. thanks for having a look red Share this post Link to post Share on other sites
benu 1 Posted June 26, 2003 Some people reported fixing that error through correcting wrong network settings (hosts.txt or something). Use the search function, this has come up for a few times. Hope your server gets back up, greets to SkunkMonkey, Junker et al Share this post Link to post Share on other sites
Elvis666 0 Posted June 28, 2003 I have the same problem. Please help somebody My dedicated server works with -dplay fine , but with socket -Server Creation Failed : 2302- it doesn't matter which port 1-65xxx always -Server Creation Failed- my server WinXP pro, AMD 2000+ ,640 MB (Infineon) ,3COM 3C905c-TX Share this post Link to post Share on other sites
kabukiman 0 Posted June 28, 2003 Same Prob here.... since my CoLocation-Hoster chose to change the DNS-Name of my rented Server, Resistance dedicated doesn't start anymore..... Share this post Link to post Share on other sites
GhostX 0 Posted June 30, 2003 1. As BIS net-devel. told me, RedHat 9 has incompatible library, so do not use it for dedic. server until BIS announces new version of the server. 2. I've had the same problem under linux. U need properly set this:  1. network card configuration  2. etc/hosts file (DO NOT USE "space" but TAB key!!)  3. if still the same probl., than run NSCD - name service cache daemon   (very simple to use, just read readme) => shoult work fine And I think it is the same problem under win, so just correct your DNS and hostname settings. Share this post Link to post Share on other sites
Skunk Monkey 0 Posted July 5, 2003 We replaced the Motherboard .. that was the problem. Share this post Link to post Share on other sites
