Obtaining Server IP w/o WPE

Rather than messaging individuals, I thought it may be smarter just to ask everyone.. Since server.dat is no longer able to be decrypted (or at least not publicly), I was wondering (and have been partially answered) if there was a way to obtain the server IP. P4n explained that WPE was an option, to obtain the IP through packet logging, so I can log into a server (recent patched) through a proxy. Of course, the connection goes client > proxy > server, but since I haven't gotten the Server's IP/Port, I'm not yet able to log in through the proxy. Does anyone have a solution besides WPE to obtain the IP &/or port? It would be greatly appreciated.

-Yup stigs

Task Manager -> Performance -> Resource Monitor -> Network -> TCP Connections

Login conquer and you'll see Conquer.exe with ports and IPs it's using.

Alright, I did that but have run into a little problem. Every time I reopen a conquer.exe, the port switches to another port, and it doesn't seem to be changing before or after auth.

Ports:
1428,
1956,
2672,
4980,
2432,
1782,

IPs: (seem to be the same)
game: 216.93.191.60
auth: 208.96.34.46
(?): 69.59.128.188

any idea?

Possibly anticheat?

#edit

we got it. thanks to stefan.

No we don't, but we need to have a conquerloader that works on the turkish conquer.

Quote:

Originally Posted by Yup Stigs Alright, I did that but have run into a little problem. Every time I reopen a conquer.exe, the port switches to another port, and it doesn't seem to be changing before or after auth. Ports: 1428, 1956, 2672, 4980, 2432, 1782, IPs: (seem to be the same) game: 216.93.191.60 auth: 208.96.34.46 (?): 69.59.128.188 any idea?

Are you sure those ports you listed are server sided?

This is the usual flow of events on co's client-server connection.

1. client opens a random port to connect to specified server ip and port
2. after account authorization, auth server returns a gameserver IP and port to inform client where to connect.
3. client opens another random port to connect to the gameserver.

It all make sense if the list of ports you supplied are client sided.
I am not saying i know much about co servers, it's just that it doesn't make much sense for 1 particular server to implement so many listeners on different ports. Reason being, each port corresponds to an non blocking socket, which corresponds to a couple threads being used, and in turn takes up quite a portion of your system resource.

There's an anti cheat server that the client connects to periodically with a random remote port.

It was really stupid of me to be honest, the gameserver and authserver port are the same as normal.. 5816 & 9958 (or 9959 I don't remember) but either way before we make any progress to continue with the proxy we will have to begin logging packets from the server.. We are able to login through the conquerloader, but I want to say OELABOLA said there was something wrong with the loader. I didn't login through the proxy yesterday, only him, but he said something was corrupt about it. I'll post on it later