Steam is getting to big to handle their people

Post by **Digger[NJLP]** » Wed Oct 09, 2013 8:28 pm

You guys gotta read this!

http://steamcommunity.com/app/40/discus ... 996445309/

bmeister1 · Post by **bmeister1** » Wed Oct 09, 2013 10:15 pm

wow, cant believe that this happen to you. how do you get the ip trace back.

Post by **GenTsoChiken** » Wed Oct 09, 2013 11:08 pm

wow... damn man... and the guy makes edits to all the posts in the thread and then goes to close it... smooth...

Post by **Digger[NJLP]** » Thu Oct 10, 2013 11:14 am

Bmeister this is whats called a trace route. All PC's, Servers, regardless of OS has this ability.
Windows systems use the command tracert

So I check the server logs of the DMC server and I grabbed the ip address recorded for the login for the "Player",
which was 72.165.61.188.

THen I went to a command prompt and typed "tracert 72.165.61.188". What the tool does it goes out and maps each router you pass through on the way to the actual IP location.

The stupidity of the Forum admin was his statment that it doesn't mean anything. I could see if they protected there IP's with NAT, but in this case the route through valve's router or front door is line 10. But the kicker is, line 11 is not blank, due to NAT protection, but actually says static.qwest.net [72.165.61.188], so this guys PC has a public IP address assigned to his or her PC.

There is no getting around that this was someone with in the Valve network.

1 <1 ms <1 ms <1 ms InnerWall [10.0.xxx.xxx] <my firewall router for house network> protects my home PC's from game servers>
My game servers reside in between these two routers.
2 <1 ms <1 ms <1 ms OuterWall [192.168.xxx.xxx] <Verizon firewall router for access to internet>
3 4 ms 4 ms 4 ms L100.NWRKNJ-VFTTP-141.verizon-gni.net [74.105.199.1] <Verizon Router in Newark NJ>
4 10 ms 6 ms 7 ms G0-14-2-1.NWRKNJ-LCR-22.verizon-gni.net [130.81.191.166] <Verizon Router in Newark NJ>
5 7 ms 6 ms 7 ms so-4-0-0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.22.64] <Verizon Router in Newark NJ>
6 10 ms 9 ms 9 ms 0.xe-11-1-0.BR1.NYC1.ALTER.NET [152.63.4.237] <US router in NYC, major backbone for US>
7 8 ms 9 ms 9 ms 63-235-40-53.dia.static.qwest.net [63.235.40.53] <qwest GSP front door Qwest is a Global Service Provider>
8 81 ms 79 ms 79 ms tuk-edge-12.inet.qwest.net [67.14.4.14] <internal routes trough Qwest network
9 * * * Request timed out.
10 81 ms 94 ms 84 ms c2-core.tuk.valve.net [208.64.202.20] <Valve's network front door>
11 79 ms 81 ms 81 ms 72-165-61-188.dia.static.qwest.net [72.165.61.188]

Post by **Digger[NJLP]** » Thu Oct 10, 2013 11:59 am

Oh and BTW, tracert works with both ip and domain I can tracert to an IP, or trace to say www.led4.net or www.njlanparty.com

bmeister1 · Post by **bmeister1** » Thu Oct 10, 2013 1:46 pm

wow,thanks for the information. I will now remember this and use it. Thanks.

Post by **Digger[NJLP]** » Fri Oct 11, 2013 7:58 pm

Just an FYI, I was kinda wrong,

. I was correct that the IP was within the valve network, but I was incorrect as to who was using it. The log file created when you install the HLDS server and DMC game has a server log file that generates a record of the ip of the valve server that is validating the Steam ID as it connects. It looks a lot like the log I needed to turn on when I run DMC and record true IP to Steam ID connection. Alfred Reynolds(Valve dude) gave me a little schooling and as soon as he said it, it all came back to me.

Bottom line, annoying little toad. pissed me off at 1 AM and I should have thought through the install before I jumped the gun.

Steam is getting to big to handle their people

Steam is getting to big to handle their people

Re: Steam is getting to big to handle their people

Re: Steam is getting to big to handle their people

Re: Steam is getting to big to handle their people

Re: Steam is getting to big to handle their people

Re: Steam is getting to big to handle their people

Re: Steam is getting to big to handle their people