Ok! here we go
Me and my friend used to play a bunch...
we stopped, and I bought a wireless router. now wanting to start up again it doesn't work.
My set up goes as follows
Phoneline into standard Router, from that Router into the wireless one.
from the Wireless one into my PC
so heres the deal
Trying to port forward on my Wireless router.
it askes for an IP addy (duh)
but I'm not sure what to put in....
My standard router ports to the IP addy XXX.XXX.1.47
When I go into Ipconfig on the command prompt my Ips XXX.XXX.0.100
and my Wireless router's standard IP is XXX.XXX.0.1
and I ported Zsnes to 0.100
I'm running XP and the Firewall is killed
I've got a funny feeling I gotta change my standard router IP (1.47) to (0.100)
Help Needed!
**EDIT!**
I tryed changing my standard router... no luck.
My standard DSL router is a Westell 2200
and my Wireless is a D-Link DI-624
Thanks in advance
Router Problems...
Moderator: ZSNES Mods
Router Problems...
Why does the weasil go pop?! there is no reason it should do that
Re: Router Problems...
I'm using the exact same setup and since a few daus ago i'm also having problems with netplay.Fox wrote: I tryed changing my standard router... no luck.
My standard DSL router is a Westell 2200
and my Wireless is a D-Link DI-624
Thanks in advance
**Prince of the Zsnes board**
*Smash Champ*
*Smash Champ*
Here's the easy solution:
Use the wireless router as an access point only.
Some wireless routers have an option to do this in their setup pages. Others have to be tricked into doing it by assigning them a static IP in the same range as your main router (duh), disabling the DHCP server on it (if you don't, the 2 will conflict and nothing will work) and connecting the LAN sides of both routers, which may require a crossover cable if neither one supports auto-uplinking. It really doesn't matter what the IP address is on the WAN side of the second router/AP, since no traffic is going to be routed to it anyways.
Use the wireless router as an access point only.
Some wireless routers have an option to do this in their setup pages. Others have to be tricked into doing it by assigning them a static IP in the same range as your main router (duh), disabling the DHCP server on it (if you don't, the 2 will conflict and nothing will work) and connecting the LAN sides of both routers, which may require a crossover cable if neither one supports auto-uplinking. It really doesn't matter what the IP address is on the WAN side of the second router/AP, since no traffic is going to be routed to it anyways.
[i]"It is better to have tried and failed than to have failed to try, but the result's the same." - Mike Dennison[/i]