GnatGoSplat
Occasional Visitor
My RT-AC3100 was working perfectly on one of the 385 builds, didn't make note of which one, but probably the last one. I noticed there was a newer firmware version, so I let the router update like I have so many times before with no issues. My router updated to 3.0.0.4.386_41700 and now I cannot access wireless clients by hostnames on my LAN. I did do a full factory reset and manually (painfully) reconfigured everything from a fresh start, which did NOT fix the issue.
All my machines are on Windows default networking settings. 3 run Windows 10 20H2.
Wired computers can access the wifi computers via RDP, network share, and ping if I append a period (.) to the end of the hostname. From what I've read, this means it's failing NetBIOS or WINS name resolutions.
I've tried all number of ipconfig /flushdns, ipconfig /renew, on all the machines. I've tried rebooting them all. ipconfig /all looks no different between any machines.
Running "nbtstat -a <ipaddr>" from a wired machine does return the NetBIOS machine name in the "NetBIOS Remote Machine Name Table".
As mentioned before, factory reset was attempted and didn't help.
Any ideas? I haven't tried downgrading back to 385, but I will later.
All my machines are on Windows default networking settings. 3 run Windows 10 20H2.
- Computer1 - Wired - Can access Computer2 via hostname (ping, access Windows shares, RDP, all works). Cannot access Computer3 or Computer4 with hostname.
- Computer2 - Wired - Can access Computer1 via hostname (ping, access Windows shares, RDP, all works). Cannot access Computer3 or Computer4 with hostname.
- Computer3 (Windows Server 2019) - Wifi - Can access Computer1 and Computer2 via hostname (ping, access Windows shares, RDP, all works). Cannot access Computer4 with hostname.
- Computer4 - Wifi - Can access Computer1 and Computer2 via hostname (ping, access Windows shares, RDP, all works). Cannot access Computer4 with hostname.
Wired computers can access the wifi computers via RDP, network share, and ping if I append a period (.) to the end of the hostname. From what I've read, this means it's failing NetBIOS or WINS name resolutions.
I've tried all number of ipconfig /flushdns, ipconfig /renew, on all the machines. I've tried rebooting them all. ipconfig /all looks no different between any machines.
Running "nbtstat -a <ipaddr>" from a wired machine does return the NetBIOS machine name in the "NetBIOS Remote Machine Name Table".
As mentioned before, factory reset was attempted and didn't help.
Any ideas? I haven't tried downgrading back to 385, but I will later.