My XV6700 seems to get in alright with my Linksys router at home, but it is not working with the DI-524. This has the latest firmware on it.
I know all the right parameters for my DI-524 network: WPA-PSK, TKIP, mixed mode G and B, the proper key, etc. XV6700 MAC is listed correctly. I have two other desktop machines which I have configured with no problem.
I have tried many things, including assigning a fixed IP. Nothing worked. Doesn't matter if MAC filtering is on or off, or if broadcast SSID id on or off.
What happens is this: The screen with all the MAC and IP addresses ultimately says "connected" but the screen that lists all the available networks says "connecting." Also, the IP address says: 169.284.184.70 rather than what would be normal, e.g. 192.168.0.1xx.
The ONLY things that works so far is to eliminate all encryption, that is, no WEP, no WPA, etc. The XV6700 gets in then. I did not try just using WEP - my time ran out.
This formerly worked, until I did the latest firmware upgrade in the router, but it doesn't seem like a firmware update would take away function...
How long is the pre-shared key you used? The PPC-6700/XV7600 has a limitation of how may characters can be entered for your pre-shared key. Try shortening your wpa-psk key to less than 15 characters and see if that helps. Originally, I had an obscenely long key, but after cutting it down to 15 or less I had no problems connecting in wpa-psk encryption mode.
My PSK is 10 ASCII characters. This is the same as it formerly was on the DI-524 and the same as it is on my Linksys router at home. But at home my router doesn't support WPA, so I use WEP there.
What revision of the DI-524 are you using? A,C,D,or E. If your using Revision C and updated to the 3.20 firmware with WPA2, I can tell you I had nothing but connection issues with that firmware. Dropped connections both wirelessly and wired, frequent router reboots, etc. I would suggest saving your current router config to file, and reflash to your earlier firmware. Set everything the way you like it and test connecting with wpa-psk on the old firmware. You can always reflash the new firmware and restore the saved config if you still cannot connect on the old firmware revision.
I am using Rev. C (the numbering sequence that begins with "3." is only relevent for C, not A, D or E).
I am not using WPA2 - only the first version, but, nevertheless...
I have had other assorted problems with 3.20, like occaisonal drops of shared folders and workgroup computers on desktop PC's.
Barring any other solution, I was thinking of going back to Rev. 3.02 of the firmware, which always seemed to work for me. Your next guess was my next guess.
Do you really have the exact same router as me, and same hardware revision? This is quite coincidental.
BTW, for all those out there, and if your screen name is what I think it is for, the "Catch-22" was this: if you want to get out of the army by claiming you are crazy, you are not crazy, because only sane people want to get out of the army...
One of the reasons I answered your post was because I had similar hardware.
I wasn't sure you had revision C, because you didn't post which firmware you upgraded to (It could have been A or C, because D and E are currently the shipping revisions.) That's neither here nor there. I wasn't using the router in WPA2 Auto either, but nonetheless, I had too many connection issues for comfort.
Luckily, I had figured this out before I got my PPC-6700 and had one less thing to confound me during the setup of it. I did have the issue of my PSK being to long for PPC-6700, and I can tell you that it was a whole lot of fun figuring that out.
Hopefully, the firmware is the root of your issue and a downgrade will solve your problem.
As far as my screen name goes, It's from "Catch-22." However, the catch is that flying bomber missions through flak, AA, and enemy fighters qualifies you to for a Section 8 because you have to be insane to do so. However, in order to get a Section 8, you have to ask the Doctor for one which is the act of a sane person. So as long as you don't ask, your insane and can get out of flying missions, but to get out of flying you have to first ask; and therefore, you are sane and no longer qualify for a Section 8. Tricky thing that Catch-22.
Thanks much for your reply. I wasn't trying to be picayune, but, sometimes the most boring details make a big difference.
Regarding backtracking to 3.02, it seems that at least I must try it. I knew it wasn't a true coincidence; you wouldn't have responded unless you had something relevant to say.
I will report back, maybe in a PM.
Re Yossarian, I came pretty close for not having read the book in more than 30 years, yes?
Yossarian,
Re-installed 3.02 firmware for DI524. Works like a champ with the XV6700 now. No funny IP addresses.
Again, 3.02 has always given me problems. I keep promising my self never to install it. Now I mean it.
I am going to take this up with DLink.
Login
Panel
