Charles41
asked on
How to connect a client PC to an SBS2003 server through a Sonicwall TZ 210 VPN
My network consists of a Small Business Server 2003 with about 20 client PCs. I need to set up a computer at a remote location. I have two Sonicwall TZ 210 routers set up in a site to site VPN. With help from the archives I was able to get an active tunnel between the routers. No PCs are at the remote location yet. What I'd like to do is disconnect one computer here at the main location, plug it into the Sonicwall at the remote site and have it log in to the server as if it were still physically connected to the main network switch. I would imagine it's not as simple as that though.
Any advice on how best to go about this? Would I need to set up DHCP over VPN? The subnet at the main location is 192.168.16.0 and at the remote location 192.168.15.0. Do I need to make changes to the client PC?
Any advice on how best to go about this? Would I need to set up DHCP over VPN? The subnet at the main location is 192.168.16.0 and at the remote location 192.168.15.0. Do I need to make changes to the client PC?
Just make sure that all the needed ports are opened through your VPN tunnel in order for the PC to communicate with the DNS,and Global Catalogue at your main site.
ASKER
That is correct, I won't have a server at the remote location. The only thing I have now at the remote site is the router. I'm planning to take an unused computer and move it there.
I have turned on "Enable DHCP Server" on the remote Sonicwall router. I'm not sure I understand how to point clients to the domain controller (I'm a complete beginner at this but really want to learn).
So a DHCP server assigns the IP addresses to each computer workstation on the network. When I plug in a computer at the main office network it will get an IP address, say 192.168.16.16, from the server. If I plug a computer in at the remote site it won't get an IP address from the main server. The router at the remote site will have to give the IP address out. So the remote computer would get, say 192.168.15.15. Would the main server be able to see this computer on the remote site? Is this where the point to the domain controller comes in?
I have turned on "Enable DHCP Server" on the remote Sonicwall router. I'm not sure I understand how to point clients to the domain controller (I'm a complete beginner at this but really want to learn).
So a DHCP server assigns the IP addresses to each computer workstation on the network. When I plug in a computer at the main office network it will get an IP address, say 192.168.16.16, from the server. If I plug a computer in at the remote site it won't get an IP address from the main server. The router at the remote site will have to give the IP address out. So the remote computer would get, say 192.168.15.15. Would the main server be able to see this computer on the remote site? Is this where the point to the domain controller comes in?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks eb, I was able to get this to work. I enable DHCP relay in the Sonicwall and added the address of the server. The remote computer now gets it's IP address over the VPN and I can log in to the network just as if I were 10 feet away instead of 10 miles.
The DHCP server should give out addresses in 192.168.15.0 and it should point clients to your domain controller at the main site for DNS.
then when the user logs in from the remote site it should work like normal only a little slower.
eb