- Joined
- Jan 3, 2020
- Messages
- 5
- Reaction score
- 0
hi i need help to change port in an exe via olly dbg can any one help me ?
Most visitors online was 12720 , on 2 May 2024
-
Unfortunately, we have experienced significant hard drive damage that requires urgent maintenance and rebuilding. The forum will be a state of read only until we install our new drives and rebuild all the configurations needed. Please follow our Facebook page for updates, we will be back up shortly! (The forum could go offline at any given time due to the nature of the failed drives whilst awaiting the upgrades.) When you see an Incapsula error, you know we are in the process of migration.
Need some guide related to port change in client or any other exe
- Thread starter santabanta
- Start date
- Joined
- Oct 8, 2006
- Messages
- 740
- Reaction score
- 289
I guess we need more info about that xD
What's the game called, because there's a big chance that someone already done that to that game, so it's good to post the game's name too.
Anyway, I can give you a tip. Try to see where the game is trying to connect. TCPView can do the trick.
Searching referenced strings in the debugger can help also, but it can be stored as a string or segmented into decimals or hex somewhere hardcoded.
IP and port doesn't necessarily mean to be stored into the game's executable. These could be stored into some DLL loaded at the runtime and the executable is reading them from that DLL.
Another tip is, traceback the connection handler(WSASend, WSARecv, WSAStartup, bind, etc) --> Winsock.h library
You need to pay a lot of attention and also, you may not find it from beginning, but you need to redo the process. (Breakpointing will help to restart from a certain point of the debugger run). Also, take a pen and write down memory addresses you may find along. This will help you identify easily that function memory address.
What's the game called, because there's a big chance that someone already done that to that game, so it's good to post the game's name too.
Anyway, I can give you a tip. Try to see where the game is trying to connect. TCPView can do the trick.
Searching referenced strings in the debugger can help also, but it can be stored as a string or segmented into decimals or hex somewhere hardcoded.
IP and port doesn't necessarily mean to be stored into the game's executable. These could be stored into some DLL loaded at the runtime and the executable is reading them from that DLL.
Another tip is, traceback the connection handler(WSASend, WSARecv, WSAStartup, bind, etc) --> Winsock.h library
You need to pay a lot of attention and also, you may not find it from beginning, but you need to redo the process. (Breakpointing will help to restart from a certain point of the debugger run). Also, take a pen and write down memory addresses you may find along. This will help you identify easily that function memory address.
RaGEZONE Sponsor
