MidKnight

Problem solved. I set the ip address in the .conf files to 127.0.0.1 and the realmd->tables->realmlist to the server local ip adress. Then I set the client realmlist.wft to the server local ip address. Start the clients with wow.exe instead of launcher.exe and it works for my installation. Thanks for the help, Christian

Thanks Thomas, I manually created all of my login names and passwords and then re-booted the system. The client on the same computer as the server works great now. Unfortunately, I can't connect to the server from the other computers on my network. The remote systems can "see" the server, but when I select MaNGOS, it won't login. It just stays on the realm selection screen. The local computer settings match the others and it works fine, but not the remote computers... Any ideas? Thanks, Christian

First off I would like to say that (from a total noob pov) all of the guides on this forum have helped me get a MaNGOS server up and running. Thanks for the excellent directions. That being said - I have both mangosd and realmd up and running. I have also verified (and re-verified) that I have modified my realmlist.wft to match LAN server address (127.0.0.1). But, even using the WoW.exe to start the game, the client software still wants to connect to battle.net and update my client to version 4.0. Correct me if I'm wrong - but this client version would not work with MaNGOS would it? If not, then how do I keep it from updating the client software while still allowing me to play? Sorry if this has been covered elsewhere... It's getting late and I have been looking for an answer for several hours now... Thanks, Christian