Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[JoeKhar]

Hmmm..having those other wifi routers near by could also be causing problems. I would hoping the lowering the power might help. Darn it.

Ok, can you try this?
Set single mode N, then try single mode G then B.
Set a manual channel thats not being used if possible, pick one. Try 4 or 8 maybe?
Set the Band Width to 20Mhz Only.
Turn OFF WiFi security as a test, can turn it on later.

Do any of the device still disconnect after trying these modes with the suggested settings?

I'm attempting to see if any of these setting help or not.

I'm the only one using 6 and 11. Everybody else is running default out of the box settings on belkin routers (They didn't bother changing the SSID, either.)

I'll try the security shut off one more time.

[FurryNutz]

Figures, and not sure what models they are or how old they are, might not have any "Good Nieghbor Policy" depending the age of them. So might be putting up with some interferences. If 6 and 11 are open, that should be good for testing.

Keep us posted on the G mode results.

[JoeKhar]

After further testing..

All modes except for N have no issues. I have narrowed the problem when using AES encryption. If no security is present, then N will stay connected. As soon as AES is enabled, everything goes downhill. 15 minutes into a connection, everything drops.

I had actually done this before, but forgot the results. Same thing happened.

So in summary. Only when Wireless N and AES is enabled. N itself, with no security has no issues.

Went back to my Wireless G TKIP setting, which works flawlessly.

[FurryNutz]

Awesome, this is great info..
WPA2 right?

Now, one last thing, does Mixed G and N and Auto TPIK and AES work?

What were the bandwidth settings? Auto 20/40Mhz?

[JoeKhar]

Yep, WPA2 AES

Auto 20/40 (tried both, made no difference)

Mixed works - However, it never goes up to AES default when connecting. I'll explain.

If you have g/n mixed enabled with auto tkip and aes, the devices will go to tkip first (which then goes to G). However, I can manually change my surface pro in mid connection to use AES (which will enable N, since N only uses AES) then 15 minutes later, it drops connection.

Basically, anything that touches AES will drop out after a certain amount of time.

WEP works, WPA, WPA 2 - TKIP etc..

AES just drops out.

One more thing may confirm what I am seeing. Monitoring the connection speed on N the last time I had the security off had a constant 130mbps. When aes is enabled for those 15 minutes before it drops out. It goes up and down constantly.

edit - fixed some sentences

[FurryNutz]

Awesome. I'll run a quick test with my 657 this weekend and run this same test. My 657 is an early version so there could be differences. I do remember running in mostly in single mode N however back then I still had 1st gen iPhones so I could have been running Mixed G and N.

Thank you for your time and efforts. I would recommend that you phone contact D-Link as well and let them know about this. The more people call in, the sooner this should be addressed by D-Link.

I'm sending D-Link an email now with this information. I hope someone will have a look and get something going for the 657. Seems like a big problem.

I'll keep everyone posted if i hear anything.

Please be patient.

[JoeKhar]

That's why I wanted to provide my info. Hard to fix when you don't have any info to go on. Troubleshooting is a process of elimination.

It could be hardware related. Especially since AES is a common theme in at least my disconnections.

Give the connection about 15-30 minutes. Always a good interval to test on.

I'll continue to mess around with it a bit, to get anymore info.

I'll contact d-link support as soon as I can. thank you for all your hard work.

[FurryNutz]

I wish more users would under stand this like you do. 

That's why I wanted to provide my info. Hard to fix when you don't have any info to go on. Troubleshooting is a process of elimination.

It could be hardware related. Especially since AES is a common theme in at least my disconnections.

Give the connection about 15-30 minutes. Always a good interval to test on.

I'll continue to mess around with it a bit, to get anymore info.

I'll contact d-link support as soon as I can. thank you for all your hard work.

[FurryNutz]

Just FYI, I wanted to re-test my 657 so I put it back online yesterday. It's got v1.02 beta loaded. Set WiFi for Single mode N, WPA2 Only and AES Only and manual channel 11. Set up a 3rd party wireless bridge adapter for a xbox down stairs. Put the 657 in the living room up stairs. Wireless adapter connected to the 657 at 130Mb. Checked the signal and connection rate on the 657 and it was at 100% at 130Mb. Checked the Adapters status and signal was "Good". Roommates gaming was initially odd as we entered into gaming match, however his xbox got stuck not fully entering the game however we could each each other in chat. We believe this was a game service issue. We've noticed this when our xboxes are freezing up for no reason.   Power cycle clears this. After the 1st attempt to game, all other gaming was great. We are using the gaming QoS sticky info for XBL in the FAQ Library. My xbox was wired. Both xboxes seemed to work well. Green bars for most of of the games, we did see 1 moment of Red bar, however it soon cleared and was back at green again. Was the only 2 devices online. I wanted to see if either one of us would see any issue. We didn't get dis-connected at all, we played for 2 hours non-stop and had a good time.

I'm wondering if this could be localized to HW on your units. 

[JoeKhar]

Well, if the only thing that was different is the hardware revision, then yes.

H/W Version: A1

If you go to newegg.com you will see lots of reviews saying the exact same thing.

It is too bad there wasn't a released list of changes between the versions. I did run into somebody with an older hardware model. They were not able to reproduce the bug that was hitting mine.

Maybe I will flash one of them with beta 1.02 again and try it out.

[FurryNutz]

Yep, mines an A1....

[JoeKhar]

Interesting. While that does change the dynamic, a lot of people are still having disconnect issues.

I'm going to try 1.02 again.. actually it is almost loaded up. We're about to find out.

As far as I knew though, 1.02 was just fixing some security setting not related to any encryption. Unless I read that wrong.

edit: I will figure this out one way or another. I am annoyed a bit. Didn't get an N router to run at G. I'll continue posting here with any other data until I get it 100%.

[FurryNutz]

Be sure to do a factory reset, send FW file, factory reset once more then set up from scratch.
Again, I'm using WPA2, AES only and Single mode N, manual Channel 11. Auto 20/40Mhz. I think I left Coexistance enabled.

[FurryNutz]

What devices do you have connected to the Wifi again?

[JoeKhar]

Two gs3 phones, one note 2 (same wifi chipsets) Surface pro, a kindle fire HD on and off (disconnects as well), BB tablet that I have left on recently just to test. And a Roku XD. Does the same thing no matter how many are connected.


1.02 so far seems to be showing a more constant speed. Have no seen it drop yet. only 10 minutes in.