Connect a wireless to wired router

January 6, 2006 at 05:00:29
Specs: XP Home, 2.8ghz/1048MB

Here is my set up:
I had one wired router(with built in modem,Model: Conexant) hooked up to my PC at home and I was able to connect to the internet through it with no problem. Now I have got a second wireless router(with no modem, model: netgear) which I need to hook up also. I have configured the lan settings on the conexant as follows: IP 192.168.1.1, mask 255.255.255.0, gateway 192.168.1.1;
A cable goes from a lan port on the conexant to the wan on the netgear. The wireless netgear is configured as follows: WAN settings 192.168.1.2 mask 255.255.255.0 gateway 192.168.1.1, and the lan settings are IP address 192.168.2.1, mask 255.255.255.192, gateway 192.168.2.1;
Now when I connect up my PC to the conexant router, I can access the internet through it, but I cant access anything through my netgear router. Can someone please help, lots of hari being torn out at the moment!!

See More: Connect a wireless to wired router

Report •


#1
January 6, 2006 at 08:18:59

First I would try just setting up the netgear router for dhcp and see if that works. (Right now there is a conflict between ip info for your two routers.) So just login to your netgear router and set it up for dhcp. Then you might have to restart it, (Unplug it then plug it back in) to get it to acquire all its info. If it doesn't work post back and we can go from there.

Report •

#2
January 6, 2006 at 08:26:55

Don't guess see here
http://kbserver.netgear.com/kb_web_files/N101236.asp

Golly gee wilerkers everyone. Learn to Internet Search


Report •

#3
January 6, 2006 at 10:08:07

Your wireless router must match the IP range and subnet of your wired router: 192.168.1.x and 255.255.255.0, gateway 192.168.1.1.

The wireless must also be set to act as an access point, with DHCP disabled (the wired router will furnish DHCP for you).


Report •

Related Solutions

#4
January 6, 2006 at 10:39:22

If you've checked all the above posts and still no joy, take a look at your connextant again. You said:

I have configured the lan settings on the conexant as follows: IP 192.168.1.1, mask 255.255.255.0, gateway 192.168.1.1

Now I admit, I'm not familiar with conextant equipment but I know the D-Link router I have at home, I don't put in a gateway address on the LAN interface since it does it's routing internally. You have your LAN interface pointing at itself for Gateway according to what you posted. With a setup like that, your clients will never get beyond that interface to the external one (ergo, to the web).

I'd wager removing the gateway from the LAN interface of your connextant, or changing it to the IP of your external inferface (again, shouldn't be necessary as the NAT/Router should handle the routing internally between interfaces) would fix the problem as well.


Report •

#5
January 6, 2006 at 15:11:36

conexant is IP 192.168.1.1, mask 255.255.255.0?

netgear is IP address 192.168.2.1, mask 255.255.255.192?

netgear is on another subnet. Mask would be 255.255.0.0 to get to 192.168.1.x, no?

Turn off DHCP on netgear and remove staic netgear IP from conexant's DHCP range.

-and/or-

conexant DHCP range = 192.168.1.3 to .127
netgear DHCP range = 192.168.1.128 to .254

You then know everything below .127 is on conexant and anything .128 and above is on netgear.


WILL POST FOR FOOD.



Report •

#6
January 6, 2006 at 15:20:19

You can also check this out:

http://www.subnetmask.info/


WILL POST FOR FOOD.



Report •

#7
January 9, 2006 at 03:23:04

Thanks for all your comments, I have finally managed to get it working. I'm not a 100% certain how this happened but I think it is something to do with NAT on the conexant(like, it was turned off !!!) but I'm not sure, must have a look again this evening. All I know is the thing started working after I reset my netgear device.

Report •


Ask Question