Cheat Engine

xV

I've tried asking the dlink forum, but failed. I can't find the proper forum @ AOL's site, so I'll try here.

I have a problem using AIM and my new DIR-615. Without using my router, AIM has a constant connection. With my router, AIM loses connection and reconnects about once every 10 minutes. Does anyone know what could be the problem? And it's also not my internet because I'm playing an online game (CS:S or Counter Strike Source) while AIM is disconnecting and the game still keeps the connection.

kls85 · Posted: Sat Aug 14, 2010 10:49 pm Post subject:

update firmware

xV · Posted: Sun Aug 15, 2010 6:15 am Post subject:

Can you link me? Tried searching for an update.

Edit - Nevermind, I found it. It looks like it's working. Thanks!

AhMunRa · Posted: Sun Aug 15, 2010 7:39 am Post subject:

Find out what node you connected to for AOL. Do a trace route and make sure that there is nothing going on between you and the server.

If the problem persisted and interupted your game as well, I'd look at firmware.

xV · Posted: Sun Aug 15, 2010 10:29 pm Post subject:

AhMunRa · Posted: Mon Aug 16, 2010 9:15 am Post subject:

Click start goto Run type cmd press enter.

At command prompt type netstat -a

This will list all your open connections. Look for anything dealing with AOL on most likely port will display along with the other connection info, use the known port for the AOL client.

From here type tracert aol(dot)server(dot)com

This will list all of your hops from you to the AOL server, most should be same latency, look for spikes. You can also ping monitor the AOL server to see if your connection to it is bouncing. If it does then you know it's not your hardware. Most likely it's one hop in your route to the host.

xV · Posted: Mon Aug 16, 2010 6:10 pm Post subject:

AhMunRa · Posted: Mon Aug 16, 2010 6:19 pm Post subject:

aol(dot)server(dot)com was an example it's not a real server name. And line 2 you should blacken out. That's your IP.

Try

login(dot)oscar(dot)aol(dot)com

Connect to AIM, then do netstat -a > aimout.txt pm me the result or post but remove your IP. Really only interested in addresses containing aol(dot)com

Result will be in C:\Users\your username\aimout.txt

Saifallofjmr · Posted: Tue Aug 17, 2010 1:09 am Post subject:

Dude seriously AhMunRa, it was his router obviously if by upgrading his firmware fixed it, please just quit posting.

SF · Posted: Tue Aug 17, 2010 1:54 am Post subject:

Saifallofjmr · Posted: Tue Aug 17, 2010 2:15 am Post subject:

If so maybe it would possibly be a port forwarding problem.

kls85 · Posted: Tue Aug 17, 2010 7:40 am Post subject:

Was it doing this with the old router?
Use a wired connection to see if problem still exist.
Hook back the old router and see what it does

AhMunRa · Posted: Tue Aug 17, 2010 9:44 am Post subject:

It's not his router. He posted the content to me last night. The tracert shows at hop #8 a spike to 208 up from an average of 50 ms, this could be his whole issue. After that hop all the hops return an average of 150 ms. 208 many not seem like alot but depending the number of dropped packets this could cause a disconnect from the server.

His hop from 8 is for atdn(dot)net which is an AOL server our of Melbourne this could be his whole issue. Which firmware will not fix. If the issue was happening across multiple protocols and not just for 1 specific IM service I'd look at firmware.

A tracert from my system to this host, which is halfway around the world from me returned a latency of 80 ms.

If it were port forwarding it would work or not, it doesn't usually go spotty. But if you are concerned this is your issue you can DMZ host your computer, and I would be willing to be you money the problem persists.

I meant to get back with you last night, but I still can not double post.

kls85 · Posted: Tue Aug 17, 2010 11:15 am Post subject:

Instead of this hopping around and stuff which takes time and what not, you need to look at this from a consumer's perspective.

A regular person will buy a router and expect it to work right out of the box with no configuration's whats so ever. To do this all due to some stupid IM chatting program is not acceptable.

Sure you can waste your time on this by doing the netstat-a but it's better off if OP tries easier options first?

One thing you need to understand is does OP have this problem with his old router?
Was his reason getting the new router the exact same reason he had with the old one?
If his old one does not have this problem and assuming it's coming from the exact same location, they why does he have to do all this "work". Also there are a few version of his D-Link DIR-615

The newest one is based on revision F and looks like OP has the one before it.

FCC's internal photos of OP's router
DLink DIR-615 revision E1
https://fjallfoss.fcc.gov/prod/oet/forms/blobs/retrieve.cgi?attachment_id=1173995&native_or_pdf=pdf

AhMunRa · Posted: Tue Aug 17, 2010 11:49 am Post subject:

From consumer standpoint pinpointing a bottleneck on a network costs 0, yes it takes time.

OP has already updated firmware, no fix. Going with hacked firmware from some random vendor could fix but will void the warranty.

And I agree to do this over AIM of all things. I haven't used that program in more than 10 years.