• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 471
  • Last Modified:

Help with network setup

I'm trying to set this network up in my house

dsl connection into a netgear nvs124g router
The netgear router has a network drive, a hub, a server and a linksys wireless router connected to it.
Network drive  ip is 192.168.2.179
Server IP is 192.168.2.50
PC's on hub are DHCP they get their address from the netgar router
The netgear lan ip is 192.168.2.2
The wirless router ip is DHCP on the wan side the lan side ip is 192.168.2.20
Everything works but the wireless router.

What should the gateway be on the wireless router?

Thanks


0
whiwex
Asked:
whiwex
  • 6
  • 4
  • 4
  • +3
1 Solution
 
pseudocyberCommented:
I would not use the WAN port on the wireless router.  Connect it with a crossover to the LAN port, turn off DHCP on it.  Then wireless devices can access your new wireless AP (functioning as a bridge) and gain DHCP addresses from the Netgear.

I would put a static IP on the wireless router in the lower range, outside the scope for management.  Something like 192.168.2.5, assuming your scope starts around 50 or 100.
0
 
SorensonCommented:
If the WAN side of the wireless router is getting a dhcp address from the netgear nvs, then the LAN side of the wireless router will need to be a seperate subnet, for example 192.168.100.1, then the default gateway for Wireless clients would be 192.168.100.1 and the wireless addresses will be within the 192.168.100.x range.  If the wireless router is running in NAT/PAT mode (standard for a linksys wireless cable router) then no other changes are neccesary.  If it is not doing NAT/PAT then it will be neccesary to add a route to the netgear nvs router.  This route would be for the 192.168.100.x network it would be via (gateway) the wireless router "wan" address of 192.168.2.20.

0
 
whiwexAuthor Commented:
sirenson
I changed the lan side of the linksys router to 192.168.100.1 and now i can get to the internet from the wireless router.
However I can't see anything on the network. i.e. I can't get to the server or the network drive.
0
Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

 
pseudocyberCommented:
You'll have to go the first network and enter a static IP pointing to the Wireless to reach network 2 from network 1.  So, basically network 1 is routing replies to network 2 to its default route - the Internet.
0
 
pseudocyberCommented:
oops - enter a static route, not static ip.
0
 
SorensonCommented:
psuedocyber's answer is correct, if the wireless AP is not doing NAT/PAT, otherwise answers should be going to to the nat'd address of the wireless router - the wan interface address.  How are you trying to access the internal devices, is it via a web browser, mapping a drive letter, by name or by ip address?
0
 
whiwexAuthor Commented:

I can't ping anything on the netgear network 192.168.2.2 from 192.168.100.151
0
 
Lenney97Commented:
If you want the wireless device to be part of your network you probably want to configure the wired and wireless on the same IP subnet.  I have a setup where the netgear does NAT/DHCP and connected to the internet on the wan port.  I connect the wireless router to the netgear with a patch cable. Then on the wireless router I assign it a IP that is in the same subnet as the netgear, but not in the DHCP range.  Then I turn off the dhcp setting on the wireless.  Basically I'm using the wireless as an access point.  That way don't have to worry about static route.  Because with your network have 2 different subnet you might have problems with port forwarding.  
0
 
JJT2750Commented:
I was looking around the Netgear site for documentation on this particular router and could not find it, could you post a link to the router page.

What version Linksys wireless router are you using?

You are using this router between your internal network and the internet, right?  So that would mean that the dhcp address you are getting on the wan side is from your ISP,  I would set it up like this

Ae you using the wireles router as an AP or as a router?

Here is a suggestion


LAN Side
Inet Router=10.1.0.1 subnet mask 255.255.255.0 use the isp nameservers and gateway
Wireless router =10.1.0.2 subnetmask 255.255.255.0 gateway 10.1.0.1 dns server 10.1.0.1  
network drive = 10.1.0.10 subnetmask 255.255.255.0 gateway 10.1.0.1 dns server 10.1.0.1
server address =10.1.0.11 subnetmask 255.255.255.0 gateway 10.1.0.1 dns server 10.1.0.1
DHCP range 10.1.0.50 - 10.1.0.100

On the wireless router on the WLAN side try

10.2.0.1 subnetmask 255.255.255.0
dhcp range 10.2.0.10 - 10.2.254

Set it to router mode and turn on rip

Good Luck Let me know how you make out.




1
0
 
whiwexAuthor Commented:
here's how I have it configured

netgear router
Wan connects to Internet
Lan 192.168.2.2 mask 255.255.255.0 rip-1 on dhcp--192.168.2.100 to 192.168.2.151
network drive is 192.168.2.179 connected a lan port on the netgear
server is 192.168.2.50 connected to lan port on the netgear

Wirreless Linksys router
wan connects to lan port on the netgear router
wan is dhcp
Lan 192.168.100.1 mask 255.255.255.0 Gateway is 192.168.100.1 dns is isp dns
DHCP is 192.168.100.151 to 192.168.100.171

I can get on the internet from anywhere but I can't ping between wireless and devices connected to the netgear
0
 
Lenney97Commented:
Ok.. that made it more clear.   either you have to add a static route traffice between the wired lan and wireless lan or you can change the wireless lan to be in the wired lan.  The question is why you want to keep the wired lan and wireless lan separate?  If there isn't a reason to do that then you just need to reconfigure the wireless router.  Change the linksys ip to 192.168.2.10 subnet mask 255.255.255.0 gateway 192.168.2.2  remember to turn off the DHCP in the wireless and set the linksys to router mode.  To physical connect the two device, just use a patch cable plugged into the port 1-4.  You don't need to use the WAN on the linksys.  

Now your wireless device should get an IP from the netgear router.  Assume you still have avalible IPs on your DHCP range.  If you get the correct IP address then you should be able to "see" the other computer.  If there is a domain then the wireless device need to join the domain to access the resources.  

After your wireless is working you might want to go enable some sort of wireless security, if you haven't done so yet.
0
 
JJT2750Commented:
Have you turned on routing and rip on the linksy router?  
0
 
atomicfire001Commented:
The configuration you have is unnessciarily complicated. Just plug your internet connection to the WAN side of the Netgear router. Turn on DHCP server\turn off RIP on the netgear router and set its LAN  address to 192.168.2.1 and netmask to 255.255.255.0. On the wireless router, TURN OFF the DHCP server, and set its address to 192.168.2.2, TURN OFF any routing protocols like RIP. IGNORE the WAN port on it, and use it like an access point + network switch all-in-one device :)

This is how I run my network, works fine. Easier to setup with no need for static routes or anything because everything is on the same broadcast subnet. Good luck.
0
 
JJT2750Commented:
If you don't mind having your Wlan traffic and wired traffic together  on one segment I agree with atomicfire001.  I thought you had the two networks segmented for a reason.   Is there something special about the netgear router  that you need to keep it on the network,  otherwise you do only need one router.  If you need to keep the netgear router  then just plug one of the Lan ports from the wireless router into the netgear router and turn everything off on the linksys and use it as an AP.  
0
 
pseudocyberCommented:
Plugging the Netgear into the LAN port of the Wireless Linksys is exactly what I suggested in the first post.
0
 
Lenney97Commented:
Pseudocyber,

why you need a crossover cable to connect the two routers together?

All of us are saying the same thing here.  Wonder how wheiwix is doing.  No response yet.
0
 
JJT2750Commented:
Why is there a need for the 2 routers?
0
 
pseudocyberCommented:
Two routers have the interface the SAME.  DCE-DCE.  Therefore the transmits go to transmits, and receives to receives .... UNLESS ... the equipment has the ability to "autodetect" and electronically change the configuration.  Some equipment has a button which will do it manually - MDI/X.
0
 
Lenney97Commented:
Psedocyber,

to my knowledge most SOHO router from netgear and linksys have the auto MDI/MDI-X.  So it isn't necessary to ask him to purchase a cross over cable.
0
 
pseudocyberCommented:
Ok.  Good to have one around just in case. :)
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 6
  • 4
  • 4
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now