Quote Originally Posted by Medura View Post
This is one of the reasons theire making a new engine. In 2.0 it should be fixed, hopefully.
This is not a problem of the game engine. It's the company's general firewall.

Anyway, don't rely on ping or nslookup here completely, even though it looks suspicious at first sight. It's ICMP, a completely different protocol on a different network layer, and it's like comparing apples and oranges. I'm quite surprised that the Square routers reply to ICMP at all, which is quite uncommon for companies of this sizes ... but well, it's a company of developers and not administrators and this had been probably outsourced to the guy with the nicest powerpoint, too.

Orophin, the best thing to do would talk to a friend of yours who uses a different ISP than you do and when you observe this again, your friend should check exactly the same IPs on his side, too. Best do this synchroneously when talking on the phone and using a different ISP is of importance to make sure it's not a routing issue which only affects certain address ranges, resulting in CRCs hitting your packets or whatever. If he can not reproduce the problem, then it's probably not directly related to SE (only indirectly).

fyi, I could not reproduce the problem on my side, I had no packet losses. And even if, it's still TCP with flow control and retransmits (which ICMP and thus your ping hasn't).

If your friend can reproduce the problem, then download wireshark (http://www.wireshark.org/) and create a protocol with your ICMP traffic (ping & traceroute for 30-60 seconds) and another one when you are having your symptons while playing the game (you can start wireshark after the problems arise, no need to log off). Make sure you capture the traffic to all the SE networks, so 61.195.* and 219.117.* should suffice as long as you have no other parallel traffic to Tokyo areas. If all that networking stuff is not really clear, then you could ask your ISP to monitor your packets directly on the first switch or router ... or even better, directly ping from their router and check if they can ackonwledge your findings - they can do that, even over longer periods of time, it's part of the daily business of any network administrator and it's just a question if they want to and/or if your support contract with your ISP covers this.

Also make sure that your router is not the problem. Ask a friend to lend him yours, or whatever. Then try to reproduce the problem with his router, too. If the problem disappears, then there may be the root cause (packet filter, cyclic redundancy checks, or perhaps packet inspections, some of todays cheap router try to act smarter than they actually are) or whatever.

When you can reproduce the problem with different router hardware AND a different ISP, then this needs to be adressed directly to SE networking operations. the difficulty will be to find out how. Don't let yourself stressed being out by a first level supporter of the game, that's a) the wrong recipient because this has nothing to do with the game itself and is outside of his responsibilities, and b) he or she probably does not really understand what the problem is. I would directly demand an escalation to the networking team - but when you do that, it would be vital to deliver them a wireshark capture (or, if your ISP can do this for you, a tcpdump / snoop / IOS related ping results / whatever).

Hope that helps a bit to get the train back on the tracks.