D-Link Forums

The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: jopas on February 19, 2010, 11:41:22 PM

Title: Can't connect to the internet when I change from WEP to WPA
Post by: jopas on February 19, 2010, 11:41:22 PM

Hello This is my first post.

I purchased the Dir-655 about a week ago, I had problems connecting to the internet but after a call or two I was able to get my wireless network to connect with the encryption set to WEP. I want to change to WPA and have gone through the process of changing and saving the settings the problem is once I do that I can not connect to the internet.

Can anyone help me resolve this issue?

Thanks in advance.

Title: Re: Can't connect to the internet when I change from WEP to WPA
Post by: DirtyDawg on February 20, 2010, 01:58:40 AM

Did you power cycle everything?  Pretty much everything (modem, computers...etc.) need to be power recycled after changes like that.  Also you need to go through the configuration of your computers NIC's again.  Did you do all that?

Title: Re: Can't connect to the internet when I change from WEP to WPA
Post by: EddieZ on February 20, 2010, 11:19:56 AM

Does your PC OS or NIC driver  support WPA?

Title: Re: Can't connect to the internet when I change from WEP to WPA
Post by: jopas on February 20, 2010, 04:44:53 PM

Thanks for the replies. Computer/OS support WPA. I power cycled the computer, modem and router. Yet no connection. Changed the NICs as well and still no luck. Any other suggestions are appreciated.

Thanks.

Title: Re: Can't connect to the internet when I change from WEP to WPA
Post by: DirtyDawg on February 20, 2010, 05:08:50 PM

What about EddieZ's comment/suggestion?  Did you find out for sure if your NIC's even support WPA?

I cannot think of anything else that may be causing it.

Quote from: jopas on February 20, 2010, 04:44:53 PM

Thanks for the replies. Computer/OS support WPA. I power cycled the computer, modem and router. Yet no connection. Changed the NICs as well and still no luck. Any other suggestions are appreciated.

Thanks.

Title: Re: Can't connect to the internet when I change from WEP to WPA
Post by: jopas on February 20, 2010, 05:13:15 PM

NICs support WPA. I'm stumped.

Title: Re: Can't connect to the internet when I change from WEP to WPA
Post by: davevt31 on February 20, 2010, 10:27:15 PM

What are you running for your Operating System?

Title: Re: Can't connect to the internet when I change from WEP to WPA
Post by: EddieZ on February 21, 2010, 04:17:30 AM

If it is XP < SP2/3 that that's the cause.
Are you sure the driver is WPA2 compatible? And did you choose WPA Persona in the DIR?


Give us some more exact details on your settings, versions and hardware used. This is looking like a guessing game already, so put some effort in it  ::)

Title: Re: Can't connect to the internet when I change from WEP to WPA - FIXED
Post by: jopas on February 21, 2010, 10:35:05 AM

Thanks everyone for your input.

Finally got it to work.

Title: Re: Can't connect to the internet when I change from WEP to WPA
Post by: EddieZ on February 21, 2010, 04:07:31 PM

Could you write down the resolution? It might help future users with a question concerning this...

Title: Re: Can't connect to the internet when I change from WEP to WPA
Post by: lotacus on February 21, 2010, 06:17:46 PM

i'll guess, deleted the old wifi profile and reconnected so that windows could properly detect the current encryption being used. Common problem when encryption type is changed and doesn't match what windows expects using the "old" profile it stored.

Title: Re: Can't connect to the internet when I change from WEP to WPA
Post by: rcloward on February 28, 2010, 02:13:36 AM

I had this same problem.  In fact I couldn't even go from WPA to Open security.  My solution was the same, you must delete the wireless profiles in Win Zero.  In my experience this is not required with PROSet Wireless but it was the only way I could get a computer running Win Zero as the wireless client connected.  Becasue all my PROSet clients didn't require this step it took quite awhile to find the problem.