Wireless Connection

[Crash!]

Okay, so I've been trying to get a wireless connection on my Wii, PS3, and my PSP. Now the connection percentage is 100% since its like fifteen feet away from the router.

So here's the problem, I put in the WEP password on all three and the IP address. And the result is that none of them work at all. Then I enter the ESSID password to see if that would work. But it didn't.

Help?

[Forever Atlas]

If you manually set an IP maybe you should scratch that and enable dynamic (DHCP) so the wireless router automatically gives each device an IP to connect with... Is that your prob?

There could be many reasons its not working. Many common reasons are that no IP address is obtained on the router thus no IP address is given to the connected devices.

When you say, "It wont work" what exactly wont work?

Is it the range? Security? Passwords? IP addresses? etc.

[Agent007]

What type of router is it? Have you tried to log into it and see if there is protection/limited access anywhere?

[Victor]

Uh, are you selecting the correct Security Types?
Also, CaSe SeNsItIvE

[spoiler] I had to do that [/spoiler]

[Crash!]

Originally Posted by Agent007

What type of router is it? Have you tried to log into it and see if there is protection/limited access anywhere?

I have Verizon...

Originally Posted by Forever Atlas

If you manually set an IP maybe you should scratch that and enable dynamic (DHCP) so the wireless router automatically gives each device an IP to connect with... Is that your prob?

There could be many reasons its not working. Many common reasons are that no IP address is obtained on the router thus no IP address is given to the connected devices.

When you say, "It wont work" what exactly wont work?

Is it the range? Security? Passwords? IP addresses? etc.

Well it says that I've connected with the access point. But then it times out to find the IP address.

Originally Posted by Sir Schmoopy

Uh, are you selecting the correct Security Types?
Also, CaSe SeNsItIvE

[spoiler] I had to do that [/spoiler]

Tried it and still no dice.

[square-enix]

I have Verizon...

I'll assume you have Verizon's standard issue router as well than.
We'll just deal with the Wii, since I'm more familiar with it.

I'm going to assume you accessed your router by entering in 192.168.1.xx (last numbers change depending on router) and that you made a WEP key on the first key area available. (You can have multiple WEP keys but only the first slot will work for Wii/DS)

Anyway, when you Search For the Access Point, your router should be the only thing that it finds. (unless you have other wireless devices) When the Wii is done searching, you want to pick the SSID that matches the one you put when you accessed your router.

Now, what color/type of lock does the access point have? In most cases, you put in a WEP key, your lock should be locked. All you have to do is click it and input the WEP key you made. The key should be 10 characters long.

After you put in the WEP key, it should either work or you get an error code. What's the error code?

[Crash!]

I enter the WEP key and I get the error code: 52030

[Forever Atlas]

Originally Posted by Zangetsu

Well it says that I've connected with the access point. But then it times out to find the IP address.

There's your problem. Its not your wireless, because you can connect to the access point.

So what you need to do is go into the router and set it to DHCP. Make sure also that each end device is set up for obtaining an IP address automatically.

I am not too familiar with the router but if its standard, usually you can go to your web browser and put its IP in (192.168.1.1 is the usual) and configure it from there.

Make sure the router itself is getting an IP from the ISP.

Im going to look it up, but what model router is it?

[square-enix]

Originally Posted by Zangetsu

I enter the WEP key and I get the error code: 52030

Nintendo Support for Error Code 52030
Error Codes is one place where Nintendo's site is actually helpful. It shouldn't be too hard to go through the troubleshooting.