While STO is running (it's easier if you close all apps that are using the network, browser, IM, etc), run this command from a windows command prompt:
netstat -na
Look for connections that are in the ESTABLISHED or TIME_WAIT state, most of the Cryptic IP's are in the 208.95.184.0/24 and 208.95.185.0/24 subnets. So you will see something like this:
TCP 192.168.1.20:55868 208.95.184.38:7003 ESTABLISHED
TCP 192.168.1.20:55842 208.95.185.165:7004 TIME_WAIT
You can do a nslookup or ping with reverse lookup now to verify the DNS name:
H:\>nslookup 208.95.185.165
Server: dc.caraway.cc
Address: 192.168.1.2
Name: accounts.crypticstudios.com
Address: 208.95.185.165
H:\>ping -a 208.95.185.165
Pinging accounts.crypticstudios.com [208.95.185.165] with 32 bytes of data:
Reply from 208.95.185.165: bytes=32 time=53ms TTL=109
Reply from 208.95.185.165: bytes=32 time=49ms TTL=109
Reply from 208.95.185.165: bytes=32 time=49ms TTL=109
Reply from 208.95.185.165: bytes=32 time=49ms TTL=109
Ping statistics for 208.95.185.165:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 53ms, Average = 50ms
Yep, that's a Cryptic IP. It is connecting to port 7004 and in TIME_WAIT because the connection has already closed, since this is the login server. The ESTABLISHED connection is the one that is actually sending game data and is on port 7003. (Note this is from Champions Online, but STO will be very similar).
You do not need to forward any ports, since Cryptic's games are purely client/server, i.e. the client opens the connection to the server, the server will never try to open an inbound connection so no need for a port forward and firewall rule on your router. The Windows firewall should automatically add the outbound port the first time you connect, or it will ask one time, you have probably already done this during beta.
So what you want to do is route Cryptic's subnet to your more stable connection, you don't need to worry about port numbers. This command will add a persistent (remains through reboots) route:
route -p add 208.95.184.0 MASK 255.255.255.0 w.x.y.z
route -p add 208.95.185.0 MASK 255.255.255.0 w.x.y.z
Where w.x.y.z is the internal IP of the router with your stable connection, make sure that you are running this in an elevated command prompt if you are Vista or Win7 (run as administrator).
You can check that the route is in your table with:
route print
I will verify the exact IP's tomorrow once the game is up, but if you have any questions, let me know.
|
