[Three] extracting vmaps for 4.3.4

[tweex15]

Not sure if this means anything to anyone but I've tested a few different IPs for the realmlist IP in the DB.

-If I set it to 0.0.0.0 and click Okay on the realmlist I get put back to the same screen instantly

-If I set it to the server's IP and click Okay on the realmlist it freezes the client for a good 15 seconds then throws me back.

-If I set it to the stock 127.0.0.1 and click Okay on the realmlist I get a 1-2 second freeze and same result.

A bit strange that these variables are affecting the client like that. Now if I can find what I'm doing wrong so it'll actually let me in, I'd be golden.

[lfxgroove]

Hm, lets start over i'd say, from which computer are you connecting, and where is your server located? Internal/external? And let the bindIp in the config file stay with 0.0.0.0 that should suffice

Also, if possible, start by having wow and the server on the same computer, then you don't need to change the address in the db or anything, that should work out of the box, does it?

[tweex15]

Hm, lets start over i'd say, from which computer are you connecting, and where is your server located? Internal/external? And let the bindIp in the config file stay with 0.0.0.0 that should suffice

Also, if possible, start by having wow and the server on the same computer, then you don't need to change the address in the db or anything, that should work out of the box, does it?

It appears that internal network works good. My server is on another box in the house, and my main PC with WoW client connects to it via IP. My config file is still set to 0.0.0.0 and the db IP is now set to the internal IP of the server box. Ports are forwarded, just doesn't want to hook up externally.

[lfxgroove]

Ah, so connecting in the internal network works well as it should in your current setup. When you're connecting from external you would probably have to set the address to your external ip and connect to the external ip from your internal network aswell iirc.

[bels]

Ah, so connecting in the internal network works well as it should in your current setup. When you're connecting from external you would probably have to set the address to your external ip and connect to the external ip from your internal network aswell iirc.

This is correct. If you have your ports forwarded in your firewall correctly this works fine. I am running a Three server this way.

[lfxgroove]

Thanks for the confirmation bels!

[tweex15]

This is correct. If you have your ports forwarded in your firewall correctly this works fine. I am running a Three server this way.

This is interesting. So the "address" field in the realmlist table needs to be changed to my dyndns hostname? I could put IP but that's bound to change as it's not static. I thought I tried hostname yesterday with no luck.

[tweex15]

For what it's worth I did try my IP address and externally IT WORKS. Now if I can get it to work with hostname instead ... small victories at this point I guess.

[lfxgroove]

What happens when you use your hostname instead in the address field?

[tweex15]

What happens when you use your hostname instead in the address field?

The same issue as before, with a good 5-10 second freeze in the game when I hit OK on the realm select screen.

[Hikari]

As you can read in different topics the Cataclysm client reuquires mandatory an IP address. Hostname doesn't work.

You can try to implement this work around from shlainn into your RealmList.cpp and see if it works afterwards.

[Merlinium]

Hm,

All our servers at covenant-wow use enGB data and they are fully compatible with enUS clients.

For 4.3.4 I took the exe's dlls from a 4.3.4 torrent and then ran the wow regen program to download ll the data fresh from blizzard

I was referring to an issue I had running the extractor on a enGB version, but then again, I didn't pull fresh content from bliz servers like i did with enUS version.