navigating Windows network files (frustrating)
navigating Windows network files (frustrating)
Well, it seems you're checking if the Mellanox cards function as 10Gb NICs and are directly connected to your workstation. For general networking, you should confirm whether the server has a fixed IP address. Usually, when I encountered this issue, I needed to set my PC as the primary DNS server for the client.
They're PCIe cards linked together directly, similar to the networking setup in a Linux 10GB video. The server keeps a fixed IP address, which is set through the router's LAN configuration (MAC address reservation), IPv4 settings (for the built-in NIC, not the betweenox) and possibly in the system registry. I'm not sure which device acts as the main DNS server—wouldn't be surprising if the router handles that role. If you do this, it might influence other W10 and OSX machines on the same workgroup, though they're still part of the same network. Regarding your PC issue, it seems like it might have left the homegroup and can't rejoin, which could affect its connectivity.
Here’s a revised version of your text:
—I’m interpreting your request carefully. You’re aiming to link your workstation via the Mellanox card to your home server using the same card, rather than relying on gigabit Ethernet. Please confirm if this is correct.
Let’s begin with these points:
1) Give each Mellanox device a fixed IP address. I usually do this for interconnects, especially when you have direct passive copper wiring between the cards across separate subnets from your main network. This setup isolates your internal segments (like 10G and 100G PHY layers) from external access—designed that way.
2) Workgroups aren’t necessary. I’ve always kept all connections public, mainly because a partially open firewall makes passwordless SSH between systems tricky, especially with the apps I run for parallel processing.
3) DNS settings for your Mellanox devices don’t matter much. If you needed them, assigning them would be pointless since they’re directly linked.
4) The DNS server assigned to your cards isn’t crucial either. Unless you specifically need it, leave it off. It wouldn’t help if the network path is as direct as yours—no need for a gateway or DNS on the 10G ports.
5) If you assign a static IP, try these steps:
- Check if the card supports PXE boot over the 10G ports. If so, the FlexBoot BIOS may start up during boot. Look for this behavior.
- If it boots, inspect Device Manager for errors or warnings about driver loading.
- Download Mellanox tools; after installation, look for a “Diagnostic Tools” folder and additional utilities like mst, mlxconfig, mlxfwmanager.
- Run mst to launch the configuration tools.
- Use mlxconfig or mlxfwmanager with commands like `mlxconfig <<device id>> --query` to query the card.
- If that fails, disconnect all relevant drives and install a small drive (SSD or mechanical) on one system. Then load drivers on Linux—this often resolves issues.
I’m writing this to reflect some of the actions I took when troubleshooting my Mellanox ConnectX-4 cards with Windows Server 2016. My current setup runs Linux, which made it much easier to diagnose problems. If you need further help, let me know.**
OP here again with the same issue using Windows 7 and a Linksys EA8100. The problem isn’t the router itself—it was swapped in over a year ago without any problems. Now, on two wired clients, I’m getting a 0x80070035 “cannot find path” error. Both devices can ping each other and see each other in network devices, but they’re directly connected to the router. I’ve removed the Mellanox cards from both machines and manually installed KB4487345 on them. No passwords, everyone access allowed. Suddenly connections stopped. This is frustrating. It’s Windows 7, supposedly EOL—Microsoft doesn’t seem to support it anymore. What’s going on? Any advice would be appreciated.