Problems with creating private WoW server

4 posts

1. james123
   
   Member
   Joined: May '08
   Posts: 10

   I've followed the guide found here to make a private server extremely closely and I'm almost certain I haven't made any mistakes along the way.
   However, when I go to connect to my server with my account username and password, I'll always get the "unable to connect" error, preventing me from getting on.
   Another problem I can see is that when I run the "mangosd.exe" executable, I get this error come up:
   http://i202.photobucket.com/albums/aa158/crumble114/untitled-2.jpg

   Any ideas on how I can get my server working correctly?
   Thanks to anyone that can suggest something.

   Posted 1 year ago » Permalink

2. -Poe-
   
   Regular
   Joined: Apr '08
   Posts: 35

   Looks like you extracted the DBC from the wrong Client Version. Reaper MaNGOS 5472 is only compatible with WoW 2.3.3.7799 so be sure you have that version before you rip the DBC/Map/vMap files.

   Posted 1 year ago » Permalink

3. james123
   
   Member
   Joined: May '08
   Posts: 10

   Thanks -Poe-, yeah I found out I extracted the wrong DBC files.
   Another quick question, I have my own private server and I also play on the official servers, how would I go about creating two different WoW directories; one with the 2.4.1 patch (official) and one for 2.3.3 (for this private server), or is there anyway I could update my private server to the current patch?
   Heh, I'd like to apologise for being such a newb with this kind of stuff. :p

   Posted 1 year ago » Permalink

4. -Poe-
   
   Regular
   Joined: Apr '08
   Posts: 35

   Not a problem, we're all n00bs once, and some will always be n00bs at heart.

   Reaper-X hasn't released a repack for 2.4.1 yet, but I wrote a guide on how to move from Reaper MaNGOS 5472 to MaNGOS 5712, which supports 2.4.1

   Here's the link. Just register to the forums, and go here:
   http://www.theghostguild.com/forum/showthread.php?tid=20

   Posted 1 year ago » Permalink

RSS feed for this topic

Reply

You must log in to post.