4 replies
by bludawg Accepted solution
by robo_dev Accepted solution
First of all the 'static' IP address is the external address of the router, the one facing the Internet. This is outside the firewall and has no relationship at all to the addresses inside your network.
Typically the firewal/router that connects you to the Internet also has a DHCP server on it's internal interface, the one that serves up connectivity on the local network.
IF you plan to use the new server as your DHCP server, then you need to assign a static IP address to the router (so you can manage it), and then disable it's DHCP server. (the DHCP service on the router).
Assuming that the firewall/router is, in fact, a firewall/router, then your server is no different than any other LAN device. Give it one NIC, or two, or as many as you like. Assign it a static IP address. Note that its default gateway is the IP address of the firewall/router.
by bludawg Accepted solution
by robo_dev Accepted solution
Well, yes and no.
You cannot do AD remotely, nor would you want to, security wise. Some VPN services give you the ability to remotely use Windows resources, but that's a whole different subject.
With respect to the internal network:
If you are using AD, that is, you have a Windows Domain, it's best to use the DHCP functionality in the Windows server, and disable it in the router. The answer can be more complicated than this, since there are issues with WINS, DNS, etc. But as long as the Windows server is reliable and on all the time, it works fine as your main DHCP server.
If you are just running a Windows workgroup, use the DHCP server in the router.
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending