Really really glad you were able to fix it, and . . . I just wish Motorola/Google/Verizon had made Wi-Fi on the Droid easier/more reliable than what it is when people like you and I have to figure out solutions, pass them on, and hope it helps others!

And I’ll tell you what: I’m not happy about this fiasco affecting so many Droid users, but I’ve actually referred to it that way myself :”I have an extra layer of security now!“.

I almost believe myself when I say that, too.

And did a scan with droid (while at the wifi menu in droid, clicked menu… and then scan). My networked popped right up and and accepted me. Like I said, I’m glad that this problem even came up.. because in fact by setting up that whitelist im even more protected than previous.

While testing I figured out that IP addresses worked, just not friendly names. Got me thinkg about my DNS. I had three DNS servers in my router, the first two are for a private network I support. My public DNS was listed third. I moved the public DNS server up to #2 spot and everything now works great. I suspect that the Droid may only support two DNS servers??

Hope this helps someone else. Anyone know of a utility like IPConfig for the Droid?

~Robert

I’m not surprised about you getting it hooked up when you switched to WPA, as most of the issues that the Droid is exhibiting seem to be WEP related. The fact that turning off MAC address filtering fixed your problem is … weird. Sure, I understand it under the circumstances you’ve pointed out, but it’s extremely troubling that turning MAC filtering on works in some cases, but off works in others.

Let’s hope Android 2.1 fixes Motorola ‘s problems for us Droid users. And it’ll be here in a couple of weeks!

As you know, we don’t have a real answer to this mess that Google, Verizon, and Motorola have created with the Droid, and I’ll say right out loud that the problem with your MAC address not being recognized brings this to a whole new level of frustration; I mean, if you can’t get it done that way . . . and with a Linksys, no less (the ‘standard’, if there is such a thing)!

The one piece of good news is that we’re right at the top of all searches on this subject, and I have to believe that if Motorola (and on reflection I believe it’s more their fault that Droid has these problems than either Verizon or Google) is paying any attention at all they’ve seen this.

And of course, there’s always Android 2.1 to look forward to . . .