It is a Dell PowerEdge R720xd, utilizing Server 2012 R2 Standard.
The NIC is an Intel i340-T rNDC.
I suspect either a bad/damaged NIC or something (not very obvious) configured incorrectly.
- Ports 1, 2, 3, 4 on the server are all bound to a NIC TEAM, ATEAM.
- ATEAM has been a STATIC LINK AGG. and a IEEE 802.3AD Dynamic Link, neither work correctly.
- Each NIC/Port is configured for maximum throughput.
- Has four brand new cables created for it, and were tested for integrity both outside the machine and utilizing the Intel ASN Diagnostic Tool in the driver.
- I believe the Switch is configured correctly (mimicking a similarly setup server's ports.)
- The switch is a Cisco Catalyst 3560X behind a 5512-X ASA.
- The ASA Firewall is not reporting ARP Packet Collision, which is what I normally see with bad "Teaming" configuration is set on the switch.
SWITCH Port Configurations:
interface gi0/
switchport access vlan10
switchport trunk encapsulation dot1q
switchport trunk native vlan10
switchport mode access
spanning-tree portfast
channel-protocol lacp
VLAN 10 is our Server VLAN.
For another layer of pain, this server is a VM Host, and we are trying to establish a Virtual Switch, using the ATEAM (with host OS Managing the TEAM and utilizing it, itself.)
Before anyone asks, yes I disabled the Virtual Switch aspect while troubleshooting.
Everything has been smooth sailing till now.
Specific Problems:
Remote desktop intermittent connectivity issues.
Large file transfers fail for "unspecified error"s.
Settings applied to each NIC/PORT:
Power Management:
Energy Efficient Ethernet - Disabled
Reduce link speed during standby - Disabled
Advanced - Performance Options:
Flow Control - Disabled
Receive Buffers - 2048 (Default: 256)
Transmit Buffers - 2048 (Default: 512)
Nothing in Event Viewer, I literally mean nothing. Server is running unhitched save for this.
Ping Results During File Transfer:
Server to my Machine: Packets Sent: 276, Received: 276, Lost: 0
Machine to the Server: Packets Sent: 277, Received: 277, Lost: 0
I have done a full scan of the integrity of the Server drives, it found no errors, but it also wouldn't explain the Terminal Services hiccup.
I am at the extent of my enterprise NIC troubleshooting skills and I don't want to talk to India.
Any help?