<BLOCKQUOTE class="ip-ubbcode-quote"><div class="ip-ubbcode-quote-title">quote:</div><div class="ip-ubbcode-quote-content">Originally posted by RobM (YankeeRob):
... I would go with the Linksys WGA54G game adapter shown here:
http://shop.ebay.com/?_from=R4...ksid=m38&_nkw=WGA54G
That's the one I use. Works both in ad-hoc and infrastructure so I can take it with me to comps.
-rob </div></BLOCKQUOTE>
Rob,
I just bought a WGA54G and am having a bit of trouble with it.
I am using it in infrastructure mode to connect to my WAP54G. From your comment, I assume you have it working in that mode.
I get what appears to be a successful connection to the WAP54G after entering the necessary security parameters (both when connected to the net for configuration and when connected to the Stoker only). However, once it is wire to the Stoker, even though the wireless light is active, I cannot access either the Gaming adapter or the Stoker behind it.
Initially, I set the IP address of the WGA54G to the address that I had allocated for the Stoker (call it x.x.x.227). Nothing was accessible, so after searching about I found recommendations that I assign one address on the net for the WGA54G and another for the Stoker. I gave the WGA54G the address x.x.x.248.
No apparent change, no access to either. Neither pings nor address scans show either device (when connected to the Stoker).
Did you use two different addresses in this mode?
Did you do anything else that might not be obvious?
Thanks,
John Brisbin