Is checking a network drive too fast? Or is finding it on your computer taking forever?
Is checking a network drive too fast? Or is finding it on your computer taking forever?
This means the interface is ready, but the operating system isn't using it. Just to be sure, are you using static IP addresses? I would also turn off IPv6 and network discovery while fixing this (even if they are needed, just so we can find the problem). Are you guys using 802.1x? If there is any traffic at all right now, it suggests the problem is higher up in the stack. Don't know if you've read this yet: using 10G speeds has some effects on TCP window size: https://learn.microsoft.com/en-us/w...s/...ance-tools
Noted: "IP addresses have always been assigned via MAC address reservations on the DHCP server (the router) " Look for duplicate MAC's. MAC Addresses From the link: "Each MAC address is unique to the network card installed on a device, but the number of device-identifying bits is limited, which means manufacturers do reuse them. Each manufacturer has about 1.68 million available addresses, so when it burns a device with a MAC address ending in FF-FF-FF, it starts again at 00-00-00. " Could be some error of omission or commission with respect to the MAC reservations being made. Compare MAC's and assigned IP addresses. Ensure that there is no overlap between the allowed DHCP IP address range and any Static IP's in use.
Time to take things to another level. Do you know about Powershell? You can use it with the "Get" commands to learn all kinds of stuff about computers, programs, and how they are set up. For instance: https://learn.microsoft.com/en-us/powers...er-2019-ps https://learn.microsoft.com/th-th/window...er-2019-ps&viewFallbackFrom=win10-ps https://stackoverflow.com/questions...rk...in-windows Get commands are safe since they don't make any changes to the system. However, you need to be careful about long scripts or commands that might change things based on what "Get" finds. The third link uses: get-wmiobject win32_networkadapter -filter "PhysicalAdapter = true" | select * to gather all sorts of information. And the command itself can easily be copied and pasted at the Powershell PS> prompt. (Open Powershell as Administrator.) Run those commands in a test area until you feel comfortable doing so and get a sense of what happens. The goal is to take an in-depth look at the network adapter to see if any settings don't match what you expect. On every different computer or how things differ between computers. Note: You can also easily find lots of scripts that collect data from network computers and other devices. Also, about printers: Powershell can get printer info too via Get-Printer and other options. https://stackoverflow.com/questions...-s...powershell Get-CimInstance -ClassName CIM_Printer -ComputerName $arrayOfComputerName