enter image description here

Router ip:
Windows server: (WLan) and (LAN)
PCs: 192.168.2.x

I am able to access from laptop (in 3.x network) but unable to access through other interface and its lan pcs 192.168.2.x.

I added a route in my router with Destination LAN NET, Subnet Mask and Gateway but still unable to access.

Do I need to add a route in my Windows server as well? If so what will be the route like?

- Server and laptop connected to Router through wireless.
- All the PCs are connected to the server through a switch.
- Server is able to access the internet through WLAN interface (
- Server and PCs are communicating through LAN interface (192.168.2.x)
- I am able to ping from router but not

Problem - 3.x machines (in my case laptop) is not able to access 2.x machines. Not even (which is another ip for server). ping works not

As @0wn3r suggested I changed the mask to in router and server but still the same problem.

  • 1
    Can you check if IP forwarding is enabled ( itgeared.com/articles/… )? And can you reach other 192.168.2.x devices from your windows server?
    – mulaz
    Dec 28, 2012 at 11:16
  • ...and check if there are any firewall rules.
    – mulaz
    Dec 28, 2012 at 11:52
  • @mulaz IP forwarding is enabled and I can reach 2.x machines from the server
    – Praveen
    Dec 28, 2012 at 12:03
  • Problem is 3.x is able to access 2.1 but not 2.101 2.102 etc whereas the server is able to access 2.x
    – Praveen
    Dec 28, 2012 at 13:01
  • What is the Firewall / Router OS?
    – Zapto
    Sep 4, 2015 at 11:26

2 Answers 2


Hmm, sorry to double post too, but I believe the StackOverflow one may be redirected or deleted (as not appropriate for that site).

Here are my questions again (can't put it in a simple comment):

This is weird: the router should be the one with enough dedicated interface to separate all your lans as needed and route between them.

From the picture it's as if your server (3.50) has 2 interfaces, one in 3.x, the other in 2.x. This should mean that between it and the PCs, there is another device (a switch? hub? another router?) so that they can talk together.

Please update the picture to give all the interfaces you use on each device (router, and server, especially) so we can clearly see what you need to do.

from the picture I can guess:

  • the router you show is the Wifi router.
  • the laptop and the server both connect to it via WiFi.

But I can't guess:

  • how does the server and the PCs connect together? via another switch? via the LAN port of the router? The fact you can't route between them seems to indicate they are not on the same lan at all...
  • You are right. The PCs are connected to the server through a switch. I updated the picture but unable to upload it. The problem is 3.x is not detecting 2.x machines but the network is accessible in their own subnets.
    – Praveen
    Dec 28, 2012 at 11:50
  • then you have a bit of a problem: for PCs to reach the other 3.x machines, they need to all have a route saying " is to be sent to" and you also need to have your 3.50 server able to route, and you also need your other 3.x hosts know that 2.x is behind 3.50 ...complex. I'd recommand: unplug LAN (2.1) from your server at all. Plug the switch to an available LAN interface on the router (and give that specific interface the 2.x/24 network, if you use the others for another LAN. OR all to the 2.x network, if possible and available). Dec 28, 2012 at 11:54
  • 1
    in a nutshell: better to route via the router ^^ Dec 28, 2012 at 11:56
  • if you want, you could describe what you need, ie what needs to be separated on different networks, what could be on the same (for example, lan is much faster than accessing through a router if you want to transfer files between hosts, but in the other hand it lacks separation and can't be filtered/firewalled easily or at all...), what dhcp you need to have, etc... Then list what devices you have (or just precise what the router model is), and we can give an "optimal" setup Dec 28, 2012 at 12:00
  • Thanks. Please see the original post in stackoverflow for updated image
    – Praveen
    Dec 28, 2012 at 12:59

You have to configure your Windows server as a Gateway. You will have 2 ips on Windows server. One on 192.168.3.x and one on 192.168.2.x subnet.

First of find ip on 192.168.2.x subnet using


command in terminal , which would be like 192.168.2.x. You have to provide this ip as a gateway in pcs that are connected in lan.

  • Your subnet mask will be
    – KK Patel
    Dec 28, 2012 at 12:05

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .