RDP and SMB servers are accessible over Wi-Fi but not through Ethernet connections.
RDP and SMB servers are accessible over Wi-Fi but not through Ethernet connections.
This is a tough one I can't seem to figure out. My PC runs Windows 10 enterprise and I'm also using it as a SMB file server. I also set up RDP so I can put it to sleep or shut down remotely. All the access are done from the same local LAN. The computer is connected to the main router via wifi 5 (802.11ac) and all is running smoothly. I recently needed to transfer large amount of files to a backup storage and I connected the computer to the same router with an Ethernet cable to bump up the link speed. Internet still works good but I can no longer access the SMB server nor the RDP from the LAN. I did some troubleshooting like checking the ip address, enabling/disabling the services, switched to public and back to private network settings, made sure the firewall is accepting those connections, etc. Nothing works. I can still ping my computer without issues. Out of ideas, I reactivated the wifi connection and I can now access the services again. But as soon as the wifi if disabled (or Windows turns it off because it uses Ethernet), those services become unavailable again. Anyone got ideas how to fix ? This is a stupid issue. specs: Ryzen 5600X Asus rtx 3060ti ROG strix B550-f gaming 16GB x4 XPG spectric 3200 MT/s WD black NV2 2TB gen 4 NVMe (boot) WD red pro 4TB SATA (shared file storage) 550W Seasonic PSU
Check if your Ethernet and Wi-Fi IPs belong to the same network range. Verify if your router has any settings to separate Wi-Fi traffic from other networks.
Same network range works perfectly. I can still reach the router, Ethernet port, and Wi-Fi without any problems. The router IP is 192.168.1.1, the Ethernet is 192.168.1.32, and the Wi-Fi is 192.168.1.111. I double-checked everything and am confident about the isolation settings—currently inactive.
Your file share only allows connections from certain IP addresses. If you set up a whitelist, you’d probably need to permanently assign your Ethernet and Wi-Fi adapters to specific IPs like 192.168.1.2 and 102.168.1.3, and make sure the SMB share permits those addresses. On your SMB computer, check if a ping to the remote machine works. On the remote machine, verify if a ping to your SMB computer succeeds. Also, review firewall settings on both devices and their routers.
I tried using my tablet and phone with different IP addresses on the PC, and everything works as long as I connect via Wi-Fi. I didn’t set up a whitelist because I want the SMB share to be accessible across my entire LAN network. I’ve already configured IP reservations for both my Ethernet and Wi-Fi adapters in the router’s DHCP settings. I confirmed the IP addresses I used are correct and that pings succeed on both interfaces. I’ll recheck later to verify. Previously, I turned off the Windows firewall and it didn’t affect things. The router has its own internet protection but lacks LAN client firewall settings, and LAN isolation is disabled. I suspect a Windows bug might be the issue, and since Windows 10 is no longer supported, it won’t get fixed. Your advice was really useful.
I noted your response as the clue that guided me to the problem. Thanks once more! I resolved it and it turned out to be a simple oversight. No references were found during the search, but it seems the local IP 192.168.1.32 is now reserved for IPv6 functionality. I received a hint while using Wifiman from Ubiquity; my machine was labeled as Xerox, but it never showed up with any IP address. The issue arose only after changing the IP. Verdict: 192.168.1.32 might be a reserved address for certain routers—it’s an undocumented behavior.