How to make two subnets communicate with each other on Windows Server
Here is my situation:
I have a client using 192.168.1.0/24 for their main network. They are starting to use up their available IP addresses. Their windows server is handling dhcp/dns/vpn. I have routing and remote access installed and functioning, but what I want is to have routing and remote accessing to issue its own range of IP addresses on 192.168.2.1, so that all users who connect in on VPN will get a 19.168.2.1 address, thus leaving the 192.168.1.1 addresses alone. Is there a way to make those two subnets communicate so that 192.168.2.1 vpn users can connect to 192.168.1.1 devices on the network?
I have a client using 192.168.1.0/24 for their main network. They are starting to use up their available IP addresses. Their windows server is handling dhcp/dns/vpn. I have routing and remote access installed and functioning, but what I want is to have routing and remote accessing to issue its own range of IP addresses on 192.168.2.1, so that all users who connect in on VPN will get a 19.168.2.1 address, thus leaving the 192.168.1.1 addresses alone. Is there a way to make those two subnets communicate so that 192.168.2.1 vpn users can connect to 192.168.1.1 devices on the network?
No you can't. What you can do is exclude a range of addresses in the 192.168.2.0 scope from DHCP and specify that the RRAS server uses those.
Actually this might be what you are looking for: http://technet.microsoft.com/en-gb/library/bb878091.aspx
Sorry first comment should have read "What you can do is exclude a range of addresses in the 192.168.1.0 scope from DHCP and specify that the RRAS server uses those". NOT the 192.168.2.0 scope. This would at least prevent those addresses from being leased by DHCP.
ASKER
I don't have any extra addresses to exclude in the 192.168.1.1 subnet. I need to create a separate DHCP server on the 192.168.2.1 subnet that VPN users will get but still be able to communicate with devices on the 192.168.1.1 subnet.
You could use an "Off Subnet" Address Pool as mentioned in the article above. However this will also require some router configuration in order to allow the different subnets to communicate.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.