9 replies
by russelsc Accepted solution
by ossyemeh Accepted solution
by russelsc Accepted solution
by churdoo Accepted solution
If I understand your setup correctly, your server 192.168.1.6 has 2x NIC's with one being on the 192.168.1.0 network and the 2nd NIC is on the 192.168.10.0 network? This means that all of the PC's on the 192.168.10.0 network are connected to a distribution behind the server, with the server providing routing and/or NAT as you've described. If the server is running NAT, it's NAT on the server that's stopping the 192.168.1.0-->192.168.10.0 traffic.
The first router 192.168.1.1 is probably also providing NAT, so you probably don't need to be running NAT on the server as well (outbound 192.168.10.0 traffic is double-NAT'd in your case). You should be able to reconfigure RRAS to disable NAT and provide routing between the networks and to the internet without losing any functionality.
by russelsc Accepted solution
Thanks to all. I have disabled the NAT on the which having 2 NICs server but nothing helped. Still i'm trying to fix the problem but i cant much more on that because users are facing link down so i m moving slowly. For your better understanding let me figure out the infrastructure a bit more: ISP--->WiFi Router (DHCP)---->Server (DHCP)----->All PCs via a normal 24 port switch I------->All WiFi PCs.
Wifi having public ip for connect internet and local ip 192.168.1.1 and its the WiFi gateway. The server having 2 NICs, one is 192.168.1.6 and other is 192.168.10.1 and this is the gateway address of all wired LAN PCs. Server having NAT that is forwarding all request from 192.168.10.x to 192.168.1.6. Hope this information enough to make clear concept. Now all wired LAN PCs can ping and connect all wireless PCs but wireless PCs cant. Kindly help me to connect both subnet that all PCs from those two subnet can connect each other.
by cg it Accepted solution
why do you have a WiFi router in there when from what you describe, you need an Access Point?
If your router doesn't support multiple LAN subnets, then even with a routing protocol enabled, it's not going to route to a different subnet on the LAN.
by churdoo Accepted solution
Only disabling NAT would not have solved the problem. Step 2 of the solution is proper routing.
1. Disable NAT on the server
2a. make sure your server will pass inbound traffic destined to the 192.168.10.0 network from the external interface to the internal interface
2b. put a static route in what you're calling your wifi gateway 192.168.1.1 to route 192.168.10.0 traffic to the server external interface 192.168.1.6
Perhaps you should hire a local consultant to assist as they will be able to do this for you quickly.
--C
by cg it Accepted solution
by russelsc Accepted solution
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending