asked on how to connect to devices through vpn when both subnets are the same?
Hi, some networks I have inherited had subnets of 192.168.1.*, like most home networks. Now that VPN's are more essential, this causes problems for me.
So when the user connects to the office vpn with the same subnet they cannot rdp to stations on the remote network, sometimes.
Sometimes they can and sometimes they cannot. Sometimes they can rdp to one computer but not another.
Question: is there a way to connect consistently to computers on the remote network using the same subnet?
Thanks all.
So when the user connects to the office vpn with the same subnet they cannot rdp to stations on the remote network, sometimes.
Sometimes they can and sometimes they cannot. Sometimes they can rdp to one computer but not another.
Question: is there a way to connect consistently to computers on the remote network using the same subnet?
Thanks all.
* subnettingVPN
Last Comment
Dan
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
It's a no go in the current situation. If you don't want to keep spending time changing IP numbers, you HAVE TO redesign your network.
ASKER
Yes, like I said this is only when I inherited it like that. If they don't have a domain I do, but if they have a domain controller I'm scared to go schema changing.
IP subnets are not something that goes deep into the domain set up. Assuming all servers have fixed IP numbers, change the DC IP and DHCP accordingly, follow it by all member servers and member computers. There's no intricated schema things going on, it will work after one reboot.
ASKER
OK so the domain won't care? I figured the dns setup would implode.
No, the procedure described above will work. There might be some temporary issues like devices not getting a DHCP address at first attempt, or still using their old address.
ASKER
Thanks Qlemo
Thanks Kimputer