I have two Windows Server 2008 R2 servers which act as both Active Directory primary domain controllers and DNS servers on my network. Both computers have WINS installed and are the primary and secondary DNS servers for all of the computers on the network.
When I enter a URL such as http:// server.mydomain.local, the server's IP resolves properly.
I have two AD servers: 192.168.1.1 and 192.168.1.2. One is a Windows Server 2008 (non-R2) and the other is R2. Both are AD servers for our local network. It's a simple network, 30 clients.
Now I need to replace the hardware of these two servers for newer, most powerful ones. But the server NAMES and IP ADDRESSES must be the same after the replacement.
If got 4 servers. 2 servers on location BOZ en 2 servers on location RSD. These locations both have connection to another network.
Each location has 1 server called VPN-"location" and 1 server DC-"location".
When there is no VPN established between VPN-RSD and VPN-BOZ, VPN-BOZ and DC-BOZ can ping each other on hostname and IP-adres.
If got 4 servers. 2 servers on location BOZ en 2 servers on location RSD. These locations both have connection to another network.
Each location has 1 server called VPN-"location" and 1 server DC-"location".
When there is no VPN established between VPN-RSD and VPN-BOZ, VPN-BOZ and DC-BOZ can ping each other on hostname and IP-adres.
Our AD is a basic hub/spoke design. We have a headquarters in London, and remote offices. The remote offices are connected via VPN to HQ.
We have 3 domain controllers at HQ, and one in each remote office.
I'm having trouble configuring my SuSE firewall and was wondering if anyone has any experience to assist me or point me to some documentation that may help.
We are a development shop where all 50-odd workstation computers run Windows 7 SP1 and most of our 20-30 servers are Server 2008 R2 or Server 2008 (there are a few scragglers still on Server 2003). We have a flat, single subnet environment where servers and workstations are in the same network. We have DNS servers with dynamic DNS registration enabled and currently we have WINS servers too.
People who use OpenDNS and go to a non-existing domain are getting a nice fancy search page telling them that the domain doesn't exists instead of the browser error page.
here in my home network we have a win 2008-r2 server with the dns role enabled.
I have several web application servers that i'd like to convert to using https instead of http. My organization has a purchased wildcard certificate that I have asked to use.