I used the hack that makes your nintendo wifi connector into a standard softAP. It works and I manage to connect my DS, Wii, and PC to it, but it randomly decides to stop working. Previously I could unplug the adaptor and plug it back in, but that doesn't even work anymore. (Even if it did, it's frustrating to have it cut out in the middle of my work.) I have a feeling it may have something to do with static IP addresses, however when it comes to these I am frightfully n00bish. I thought when you enabled ICS it automatically set the right settings? Anyway, the light blinks, but my PC and Wii won't connect to it. Do I need to set an IP address? I don't know if there's a specific range or anything. It may be something entirely different. :P Thanks for any and all help! http://oldmanclayton.com

cutting out in the middle isn't ip address related. signal conflict or hardware failure are more likely. what are you plugging it into? Imagine the power of knowing how to internet search http://www.lib.berkeley.edu/Teachin...

I'm plugging it into a laptop, it's routing internet via ICS from an ethernet internet connection. It worked fine when I used the standard Nintendo wifi drivers. I read somehwere that it had to do with IP addresses. Now, please don't tell me to just go buy a standard AP, that's not my question. :D http://oldmanclayton.com

If it works and then stops it has nothing to do with ip addresses. But there is a simple test. It should have a ip address in the 192.168.0.x range since your ICS nic should have 192.168.0.1 First you need to know what ip address its getting. Do you know? Can you access the AP's management interface? Once you know what ip it gets ping it when its working. Ping it when its not. Are both successful? Last but not least have you disabled or configured your windows firewall to "trust" this subnet range? Imagine the power of knowing how to internet search http://www.lib.berkeley.edu/Teachin...

Well, I hope not to jinx it, but I haven't had the problem yet today. If it shows up I'll check what you said. Thanks! http://oldmanclayton.com

Well, here's something interesting. It quit working on my Desktop again, but another laptop that connects with the old preset SSID system didn't stop working. I couldn't find the IP address from the management software, sadly, but I found in the log that it says AP reset, and then such and such MAC address associated. One of them, the laptop, always reconnected after a reset. The other, my desktop, didn't. It sees the network sometimes, and sometimes not, but no matter what it usually doesn't connect. I suppose I could check the IP address via the command line function, but I can't seem to remember what it was. http://oldmanclayton.com

This gets blamed on IP addressing because quite often it means there's a conflict between the client and some other device on the LAN that just tried to access the server using the same IP address. You say you have a static IP address: if one of your other devices has the same IP address it periodically sends a packet to the server as the same time as your client's packet, the server will drdp both packets, and your client will seem to "hang" as it waits for a response that will never arrive. The TCP/IP protocol includes a timer that after (x) milliseconds will retransmit but of course the other device has one of those, too, and submits its replacement packet at about the same time as yours so yet again the packets collide. Pick another IP address or switch to dynamic routing and see what happens.