Johnny_FL1

Hi We have found some solutions and are now evaluating which ones the best for us. The Solution will be two physical Load balancers which have a floating IP configured. The clients get the floating IP as DNS. This way, all other traffic will take the same route as it does today and DNS will take the route over the load balancers. Thanks for everyone who has helped me solve this issue. Peace out

Hi tech.guru Thanks for the reply Wouldn't the netscalers cause problems with the Active Directory etc.? Or would it be possible to configure the clients to use the virtual IP of these netscalers for DNS only? Then all other traffic that has to go to the DC's would take the same path as today.

Hi everyone I'm an IT apprentice and got the task to find a solution for DNS failover. I know, that for windows at least, it's possible to set two DNS servers. One primary and one secondary and if the primary doesn't respond, it will switch automatically to the second one. Sadly not all clients in the company I'm working for are able to do that. So I'm searching for a solution on the DNS side. We have three Domain Controllers running DNS and Active Directory. The solution must be able to function internally without internet access, so external health checks are not an option. Please consider, that a possible solution must be higly available and reliable. Cost doesn't really matter in this case, so if additional hardware is needed, it's no problem as long as that is redundant. And again, it must be a server side solution. The Pictures included should visualize the infrastructure and the searched solution a bit. Is there a HSRP like solution, which uses a Virtual IP to which clients refer, and in the background health checks (like heartbeats) are checking the three DC's for connectivity and in an event of failure automatically switches the traffic? Or is there a way to do health checks within the Servers, so that the secondary monitors the connectivity of the primary and automatically "simulates" to be the primary in the event of a failure? EDIT If there is a solution without having to place some hardware in front of the DC's, but to handle the problem amogst the DNS servers themselves, such solutions would be preferred. EDIT END I know my text may be difficult to understand, but I'm open for questions. Thanks for the help in advance Johnny

Sadly the older driver wouldn't work for me. But I installed Windows Server 2019, after that the newest Nvidia driver worked without a problem.

Hi everyone I'm an IT apprentice in Europe and have some problems with drivers for a GPU Server. So here's a little Info that might be important: The Server has 8 Nvidia RTX 2080 Ti's in it and will be used for password cracking. I use Hashcat to crack passwords. I've installed the OpenCL runtime for Xeon CPU's. I've installed Windows Server 2016 64bit on the Server. Hardware specs: 8x GeForce RTX 2080 Ti TURBO 11G 2x Intel Xeon 4110 Silver supermicro x11dpg-ot-cpu Motherboard And now my problem: I want to use the computing power of the RTX 2080 Ti's to crack passwords and to do that, I'll need an Nvidia driver if I'm correct. Problem is, I couldn't find a driver for RTX cards that lists Windows Server as a compatible Operating System. I don't want to game on the machine, Hashcat just has to recognize the GPU's which is done with OpenCL. As I mentioned above, I've installed the OpenCL runtime for Xeon CPU's but that obviously doesn't include the GPU's. Thanks in advance for every help I can get on here. Regards Johnny