Printable View
hello guys,
how to modified chatserver to point in my new exdb. im trying to figure it out by olly and hex but no luck. maybe im looking at the wrong place.btw already searched in muonline section but no result for this issue.
new exdb shortcut properties 127.0.0.1 55926
new chatserver shortcut properties 127.0.0.1 55926
but chatserver still pointing in 127.0.0.1 55906 <---- on its own logs, i need to change it to target in new exdb port.
badly need help.
In the exe there is two place where you can find the port, you need to edit both.
I cant find 55906 in chatserver.exe using hex editor and ollybg allconstant searching for the port but still no luck. Could you please tell me what tools i need. What procedure. Thank you for the responseQuote:
Originally Posted by RevolGaming
I used ollydbg when I made it, btw why you need to change the port?
global post for muengine file. 2 different server.Quote:
Originally Posted by RevolGaming
may i know how do you do that in olly step by step?
Hmm upload your chatserver and give me which offset did you find, and tomorrow if i have time I will find it for you.
this is my chatserver https://mega.nz/#!mB5DSJDb!rM2y1XSzU...LdEmb69hh7Nk1sQuote:
Originally Posted by RevolGaming
its pointing to 55906 port of exdb. please change it to 55926
https://mega.nz/#!FdoGiLbT!OBIocmRXc...hxJc0nNDzye_ZQ
Port changed.
mate this chatserver now is pointing to 55926 exdb port but it has a bind error when i run it i dont know why.Quote:
Originally Posted by RevolGaming
this is the SS. http://i64.tinypic.com/34od8hh.jpg
direct run the chatserver.exe give also a bind error. when i change the properties of chatserver shortcut to 127.0.0.1 55926 still bind error. try it with other other port like 127.0.0.1 55916 no more bind error and still pointing to 127.0.0.1 55926 in its visual logs.
new logs.
Quote:
exdb Server connecting (127.0.0.1:55926)
Exdb server connected
check port fail.
chating server run fail.
can i ask again a chatserver with 55916 port?
thank you so much.
Chatserver port
- Create shortcut properties -> 127.0.0.1 NEWCHATSERVERPORT
so for example chatserver.exe 127.0.0.1 50000
- - - Updated - - -
Okey so 1st of all.
-> 1 Chatserver, 1 exdb on the original port
-> Chatserver 127.0.0.1 newport, exdb 127.0.0.1 newport
Quote:
Originally Posted by RevolGaming
yes already did it. hours ago. but still bind error.
server1 default shortcut
exdb 127.0.0.1
chatserver 127.0.0.1
modified
exdb 127.0.0.1 55926
chatserver <---- try it run directly but still bind error.
chatserve 127.0.0.1 55926 <---- bind error.
test again with this
on default
exdb 127.0.0.1 55906
chatserver 127.0.0.1 55906
in modified.
exdb 127.0.0.1 55926
chatserver 127.0.0.1 55926 still bind error.
if i run the modified 1st the default goes to bind error.
Man... if you run the exdb on 127.0.0.1 and PORT 55926
you cannot run the chatserver on 127.0.0.1 55926, thats why you get bind error, because you try to run the the exdb and the chatserver on the same port.
Use another port in the chatserver startup for example 50000 and you dont will get bind error.
your right mate. but may i know why the result isQuote:
Originally Posted by RevolGaming
hope you can help me to fix thisQuote:
12a ExDb Server Connecting... (127.0.0.1:55926)
07:25:12a ExDb Server Connected
07:25:12a Check Port fail.
07:25:12a Chating Server run fail.
Give me than the chatserver original port than give me the new one..
https://mega.nz/#!GQhiyRwA!q2pNq4QcN...rYiJ35r3BR91EoQuote:
Originally Posted by RevolGaming