Huntercounter463

————————————————————————————————————————————

Media Endpoint Discovery is an enhancement of LLDP, known as LLDP-MED, that provides the following facilities: Auto-discovery of LAN policies (such as VLAN, Layer 2 Priority and Differentiated services (Diffserv) settings) enabling plug and play networking. Turned on LLDP and listened for the lldp broadcasts via wireshark. Identified the Chassis ID from the broadcasts as well as the port id and type. We entered these into the LIS using the commands above. Haven't been able to get it to work. The following article still claims that LLDP-MED will only work with Windows. Link Layer Discovery Protocol (LLDP) supports Intel X710 and XL710 adapters with FW 6.0 and later as well as X722 adapters with FW 3.10 and later. Set LLDP driver load param to allow or disallow LLDP frames forwarded to the network stack LLDP agent is enabled in firmware by default (Default FW setting) Set LLDP=0 to disable LLDP agent in firmware.

UPDATE: According to Microsoft, this was never supposed to work. We will need to rely on third party NIC teaming software for client operating systems.

See the Technet thread here: https://social.technet.microsoft.com/Forums/office/en-US/936e8936-810c-434f-9e06-525daafa50b8/teaming-not-possible-in-win10pro-insider-builds-10565-and-10576-error-87?forum=WindowsInsiderPreview

Intel NIC Teaming Software:http://www.intel.com/content/www/us/en/support/network-and-i-o/ethernet-products/000005667.html

1. Lldp run (To enable LLDP for the switch) vlan 100 name '.Data.' untagged A1-A24 (Which ports you want to untag the VLAN for, etc data VLANs) ip address 10.254.254.254 255.255.255.0 (Switch IP address) ip helper-address 10.254.254.250 (DHCP Server) exit vlan 200 name '.Voice.' tagged A1-A24 (Which ports which you want to enable the Voice VLAN for) voice exit.
2. Windows 8 startup proceeds, but a message box is displayed informing you that the MsLldp service has failed to start. Restore Default Startup Type for Microsoft Link-Layer Discovery Protocol Automated Restore. Select your Windows 8 release and edition, and then click on the Download button below.

Broadcom Downloads: https://www.broadcom.com/support

Be sure to check and make sure any NIC you are purchasing is compatible with Windows 10 and the NIC teaming software.

————————————————————————————————————————————

There may be times that you will require more network bandwidth on Windows clients to transfer files much quicker. Because most network cards are 10/100/1000, you are limited to gigabit speeds (using a gigabit switch, of course). There are other alternatives, such as buying a 10Gb NIC and switch to speed up the network, but one simple way to accomplish this is by using NIC teaming.

An easy way to create a network team was included in Windows Server 2012. This functionality was also included in the client version of Windows as well, just without a GUI. Because there is no graphical interface, we will be configuring a team using Powershell.

This example is being presented using a Windows 10 virtual machine with two virtual NICs attached. This same concept will apply to any Windows 8+ computer with two or more network adapters.

Gathering Information

To get started, we will need to gather some information. The command will require you to use the actual name of the adapters to include them in the team. While you can use the default options, I recommend renaming the adapters to something easier to understand. You can see my example of this at the beginning of this article detailing How To Enable NIC Teaming in Windows Server 2012 R2.

1. Open the Network Connections control panel applet by clicking Start and typing ncpa.cpl into the start search. Hit the EnterKey to continue.

2. Note the names of the network adapters exactly as they are displayed. In this example, the two network adapters are named Ethernet and Ethernet 2.

Creating the Network Team

The command we will be running is a Powershell command built into Windows Server and Client Operating systems. Microsoft has a TechNet article detailing all of the parameters for the command that you can check out at: https://technet.microsoft.com/en-us/library/jj130849(v=wps.630).aspx

Windows 8.1 Dpi Fix

1. Click Start and in the Start Search, type Powershell
2. Right click the Powershell icon and choose Run as Administrator
3. If you are prompted to allow the action by User Account Control, click Yes.
4. Enter the command new-NetLBFOTeam [TEAMNAME] “[NIC1]”, “[NIC2]” and press the Enter Key.

[TEAMNAME] – The name you want to give to the team of network adapters
[NIC1] – The name of the first network adapter found from above
[NIC2] – The name of the second network adapter found from above

5. Finally, Open the Network Connections control panel applet by clicking Start and typing ncpa.cpl into the start search. Hit the EnterKey to continue.

Windows 8.1 Rdp Client

You can see that the new team you created is now available. You should also note that the IP Configuration options of the network adapters included in the team are disabled. You can configure a static IP address on the teamed network adapter, or allow it to obtain an IP address from DHCP normally.

If you don’t have 2 network cards in your computer, check out http://amzn.to/1kqsTV3 for an Intel Dual Port PCI-e network card to get you started.

Description

In Windows 8.1/10, during the backup process, the following error may be found in the Windows Event log.

Solution

To suppress this event log entry you must add the correct permissions for the NT AUTHORITYSERVICE to MSLLDP service.

Open an Administrative command prompt and enter the follow command:

Windows 8.1 Rdp Update

Windows 8.1 Dpi Change

On success the following is displayed: