Guten Tag zusammen,

ich stehe vor der Aufgabe an einem bestehendem Win Server 2012 (DNS, DHCP, Router, Fileserver) weitere LAN Leitungen ber NIC-Teaming an den zweiten Switch zu verbinden.

##Ist Stand
30 Clients (Win7) -> 2 HP Switche -(LAN2)> 1 Server (2012 Standard) -(LAN1)> KabelRouter -> Internet

##Soll Stand
30 Clients (Win7) -> 1. HP Switch -(LAN2)> 1 Server (2012 Standard) -(LAN1)> KabelRouter -> Internet
                  -> 2. HP Switch -(LAN3)> 1 Server (2012 Standard) 
                  -> 2. HP Switch -(LAN4)> 1 Server (2012 Standard) 

Nic-Teaming ist das Mittel der Wahl. Nur das nach der erfolgten Umstellung der Netzwerkadapter und Anpassung der IP-Adressen, die Clients nicht ins Internet kommen. Ich vermute es gibt noch eine DNS Einstellung die man nach dem Teaming anpassen muss?

Momentan ist die Ausgangssituation wieder hergestellt und alles funktioniert wie gehabt ber eine Leitung.

Fr Hilfestellung und Troubleshooting Tipps bin ich sehr dankbar!

From bing.com/translator

Hello together,

I am faced with the task to an existing win Server 2012 (DNS, DHCP, routers, file server) more LAN to connect cables from NIC teaming on the second switch.

NIC teaming is the drug of choice. Just come to the recent conversion of the network adapter and adaptation of IP addresses, the client not on the Internet. I suspect there's still a DNS setting which you must adjust to the teaming?

At the moment, the situation has been restored and everything works as usual over a line. For help and troubleshooting, I am very thankful tips!

Hi,

According to your description, my understanding is that client cant connect to internet after configuration NIC teaming on Windows server 2012.

I am not sure the detailed configuration of your teamed NICs, some general troubleshooting steps just for your reference:
1. DNS server services interface: DNS Manager Properties Interfaces, check the IP address which will be used to service DNS request.
2. On client, make sure that correct IP address of DNS server has been configured on TCP/IP properties. 
3. Some tools, such as nslookup(https://support.microsoft.com/en-us/kb/200525) or network monitor(down load link: http://www.microsoft.com/en-us/download/details.aspx?id=4865), might be helpful for further troubleshooting this problem.

This is Microsoft TechNet forum in English language, if you preferred to use German, you can post the thread to the below forum(in German language):
https://social.technet.microsoft.com/Forums/windowsserver/de-DE/home

Best Regards,
Eve Wang