neelah

The difference here is the subnet mask. I am using a 255.255.248.0 Subnet. unfortunately changing that accordingly doesn't make it work neither :-(

It looks like my thread was moved here. I don't think that this actually helps reolving the situation but that's just my personal opinion. I still see the same problem. I cannot connect to the server setup in my LAN. It works locally though. Any help will be very much appreciated.

Well, thanks. Let me sum it up again: The config.wtf has SET portal "172.17.17.23" auth DB, realmlist table address: 127.0.0.1 localAddress: 172.17.17.23 localSubnetMask: 255.255.248.0 I have the feeling that it has to do with the subnet I am using. Maybe that's not working?

Thanks. I tried address with 127.0.0.1 as well as 172.17.17.23 and localAddress with 172.17.17.23 and 127.0.0.1 and vice versa. Unfortunately with the same result. LocalSubnetMask is not documented at all so any insight on that would be great. Actually any help would be very much appreciated. I love this project. It's very well documented. It's just the little details that are not. Thanks :-)

I would like to add my LoginREST configuration and try to explain why I think that the comentary in the config file is confusing for me. # LoginREST.ExternalAddress # Description: IP address sent to clients connecting from outside the network where bnetserver runs # Set it to your external IP address LoginREST.ExternalAddress=172.17.17.23 What do I do in my case? I don't want to use the server with an external adress since I don't want to run it public, only in my LAN. Should I just empty it, point it to localhost 127.0.0.1, my LAN address or does it simply not matter, because it won't be used as long as it is not accessed from outside the internal network? # LoginREST.LocalAddress # Description: IP address sent to clients connecting from inside the network where bnetserver runs # Set it to your local IP address (common 192.168.x.x network) # or leave it at default value 127.0.0.1 if connecting directly to the internet without a router LoginREST.LocalAddress=172.17.17.23 I am at a loss here. I guess I should just leave it like this since this is the local adress of the network card of the server. What I don't get is this: "or leave it at default value 127.0.0.1 if connecting directly to the internet without a router" What does it mean? In case the server doesn't use a router and is directly connected to the itnernet I should put the localhost here instead of the external IP?

Hello, as already mentioned in this thread I have some trouble with a TC 6.x that I try to run in my LAN. Since the topic is slightly different than the initial problem, I guess it's ok to open up a new topic for this. The WOW clients are supposed to connect from within the local network. As far as I can tell, I followed the guides to set this up correctly but the clients fail to connect. The login works well with the account that I created and lists all realms. Once I try to conenct to the realm I immediately get disconnected with the error message WOW51900328. Unfortunately I cannot find anything helpful using Google or the forum search. I was thinking that maybe my LAN setup is special and may be causing the trouble. Maybe somebody can give some insight into the following DB fields and if my assumptions are correct. I am using a private class B network. 172.17.16.0/21 Subnet Mask 255.255.248.0 So I configured the "realmlist" table int he auth DB like this: address 172.17.17.23 (the IP of the server with TC) localAdress 127.0.0.1 localSubnetMask 255.255.248.0 Does that sound about right or am I having trouble to understand the meanings of the different datasets? Also I was wondering how I should configure the logging to get some more valuable output that points into the right direction of the root cause of this issue. I assume that the authserver does what it should since I can login just fine. The bnetserver seems to be the problem so I should configure the logging there, correct? Now I am wondering how I should configure that. When using Trace or even Debug I am overwhelemed with data that is not really helpful. is there a way to filter the login process out? Thanks again! Neelah

Thanks for your replies. I compiled the new source and it looks like it works (the incompatible error is gone). Unfortunately once I connect to the realm I get dropped out immediatly with error WOW51900328. The authserver.exe seems to be working though since I can only login with valid name/password. Any ideas what could be the issue? The client is on a different machine than the server. Ports are opened as far as I can tell. What kind of info would you need to help me out? I played aroundwith the log settings but seem to be able to properly configure these for a reasonable output :-(

I just had this happening here. I was able to work around it by starting the patched client from a command prompt with elevated user rights (admin) and using this command. Adjust the locale to your needs (e.g. ENus, etc.) wow-64_patched.exe -uid wow_dede That started the client but didn't solve the root of the probem. I was using the wrong client version. Keep in mind that Trinitycore 6.x is only available with 6.2.4 21335 as we speek.

Hello, I just finished setting up the worldserver and bnetserver from Tryinitycore 6.x that I gitted yesterday. Everything went smoothly thanks to the great documentation on the site. To make sure I don't break anyhing, I copied my original WoW folder to another location andpatched the wow64.exe as described. That went well and after starting it as administrator and with wow-64_patched.exe -uid wow_dede from the command line, the client started up but - surprise surprise - the realm is incompatible with my client. Well I guess this is a correct error message since it looks like I have client version 6.2.4 21463 and according to this, the currently supported client version is 6.2.4 21335. Well, I bet I am not the first person with this question but I was unable to find any solution by myself. People usually refer to the Blizzard launcher which downloads the game. But I fail to see how this is going to help me when it downloads the wrong version automatically. Should I just wait a few days until Trinitycore is compatible with my client version? Does it usually just take a few days until the code is upgraded or will it take months until some update is going to happen? If so, is there any other way to download a specific old client version? Can the Blizzard Launcher somehow do that when for example patching some ini file? Are there patches or something alike out there to download a really old version and upgrade from there? I bet this came up before and I'm sure somebody can help me out and let me know what I should do from here on :-) Thanks! Neelah