Jump to content

v0.3 Wifi Lib Connection Troubleshooting Guide


sgstair

Recommended Posts

Ok, there have been a number of people who can't connect with this version of the lib, following are some basic troubleshooting points for the current version of the lib (0.3 ONLY - later versions will fix several of these points)

 

But, before all that - check your router's compatibility on nintendo's wifi site: http://www.nintendowifi.com/ - if it's not compatible there it's probably going to cause you grief.

 

Problem:

Can't see any access points, but they were there in an earlier version (v0.2)

Probable Causes:

* this is probably a bug in the lib, I'm looking for it..

 

Problem:

Hangs at ASSOCSTATUS_SEARCHING

Probable Causes:

* your router has SSID Broadcast disabled, this must be enabled for the current version of the lib, though it is planned to be fixed in the next version.

* your router may be off.... well, it might be!

 

Problem:

Hangs at ASSOCSTATUS_ACQUIRINGDHCP

Probable Causes:

* your router is denying the lib's DHCP request; I've seen this on a few routers and am looking into it.

* You have the wrong WEP key or mode configured.

 

Problem:

Fails to connect (ASSOCSTATUS_CANTCONNECT)

Probable Causes:

* Shared key authentication is enabled - the lib does not support this yet but it is planned for the next release.

* your router has a configuration that is blocking the DS from connecting. (MAC filtering, or etc..)

 

Problem:

Connected OK but can't send/receive data!

Probable Causes:

* WEP could be incorrectly configured.

* IP address may be manually incorrectly configured.

* Router may be incompatible!

 

 

If you guys have other problems connecting, please post them here - I'm sure there are other issues I haven't documented. I'm listing just the problems I know about at the moment.

 

As always, good luck :(

-Stephen

Edited by sgstair
Link to comment
Share on other sites

  • Replies 41
  • Created
  • Last Reply

Top Posters In This Topic

Here is the problem I have: My DS connects to Nintendo Wifi just fine. And, your wifi-lib detects my AP too. But it won't connect to it at all. I'm broadcasting my SSID but the name doesn't appear when it detects my AP. Any ideas as to what it could be?

Link to comment
Share on other sites

Problem:

Connected OK but can't send/receive data!

Probable Causes:

* WEP could be incorrectly configured.

* IP address may be manually incorrectly configured.

* Router may be incompatible!

And what about this error, but happening randomly ? (seeing it works everytime with WFC games)

Router i'm using: Netgear DG384G

 

With packet captures, i'm able to see that it doesn't send anything (not even ARP).

It happens even with WEP disabled.

Edited by thoduv
Link to comment
Share on other sites

754boy: you have either a problem with open system authentication (which will be added in the next lib), or your configuration isn't set up the way you think it is - due to your explanation I can't tell which it is.

 

thoduv: what kind of packet capture?

I'm not sure what your problem is yet.

Link to comment
Share on other sites

754boy: you have either a problem with open system authentication (which will be added in the next lib), or your configuration isn't set up the way you think it is - due to your explanation I can't tell which it is.

 

Thanks for your reply. I will keep tweaking my setting and if all else fails, I'll just wait until your next update :blink:

Link to comment
Share on other sites

  • 1 month later...

hey i have tried several ds wifi programs such as dsremote and pointy remote.

 

i am using a ds lite with a superkey and a sd supercard

 

i am copying the.nds files to my sd card then run the server applications

 

when i start the programs i stop responding after it goes

 

"Waiting for ARM& to init..

ARM7 init confirmed."

 

 

i am new to this

 

any help will be appreciatied

 

khalil.

Link to comment
Share on other sites

khalil: could be a failed connection due to lack of shared key authentication support (mis-stated in previous posts, heh), or because your access point isn't broadcasting a SSID. Beyond that it's hard to tell

 

-Stephen

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...