Francis N. Phiollips
New Around Here
See my later post correcting the errors contained in this one.
This is NOT an Merlin ASUS issue. It is a Windows 10 problem.
I am running an ASUS RT-N66U. I installed Windows 10, which is when the network disconnect error would appear intermittently. Ran the Windows network troubleshooter multiple times, which reported that the network adapter had successfully reset. I tried loading different versions of the Merlin firmware, which, of course, did not fix the problem. This is what I have learned:
The Windows 10 installation re-configures your network settings. The wizards at Microsoft obviously know more about your network configuration than you do.
To undo what has been done to you:
1. Set the TCP/IPv4 properties to use specific DNS server addresses. For example, for the Google DNS ids use 8.8.8.8 and 8.8.4.4. For the OpenDNS.org DNS ids use 208.67.222.222 and 208.67.220.220.
2. Whichever DNS addresses you set up for TCP/IPv4, set up the same ones in Merlin (Advanced Setting -> Lan -> DNS and WINS settings).
3. Open a command prompt and enter:
netsh interface ipv4 show config
...and note the results.
4. Create the following command file (.cmd):
---------------------------------------------------
@echo cleaning up windows shirt...
@echo on
cd C:\Windows\System32
ipconfig /flushdns
netsh winsock reset
netsh int ip reset "C:\resetlog.txt"
msiexec /unregister
msiexec /regserver
shutdown -r
pause
-------------------------------------------------------
5. Run the command file
6. After signing on to Windows, run "netsh interface ipv4 show config" again and compare the output from your first invocation.
The contents of the restart command file are the result of talking to some knowledgeable tech support guys at Tim Wiener (call on Friday or Saturday night after 8:00 PM to get a hold of someone who is actually interested in your problem and will help you fix it) and bits and pieces from researching the disconnect problem on different websites. If you are unfamiliar with configuring TCP/IPv4 and Merlin, do not attempt any of this and forget completely that you saw it.
This is NOT an Merlin ASUS issue. It is a Windows 10 problem.
I am running an ASUS RT-N66U. I installed Windows 10, which is when the network disconnect error would appear intermittently. Ran the Windows network troubleshooter multiple times, which reported that the network adapter had successfully reset. I tried loading different versions of the Merlin firmware, which, of course, did not fix the problem. This is what I have learned:
The Windows 10 installation re-configures your network settings. The wizards at Microsoft obviously know more about your network configuration than you do.
To undo what has been done to you:
1. Set the TCP/IPv4 properties to use specific DNS server addresses. For example, for the Google DNS ids use 8.8.8.8 and 8.8.4.4. For the OpenDNS.org DNS ids use 208.67.222.222 and 208.67.220.220.
2. Whichever DNS addresses you set up for TCP/IPv4, set up the same ones in Merlin (Advanced Setting -> Lan -> DNS and WINS settings).
3. Open a command prompt and enter:
netsh interface ipv4 show config
...and note the results.
4. Create the following command file (.cmd):
---------------------------------------------------
@echo cleaning up windows shirt...
@echo on
cd C:\Windows\System32
ipconfig /flushdns
netsh winsock reset
netsh int ip reset "C:\resetlog.txt"
msiexec /unregister
msiexec /regserver
shutdown -r
pause
-------------------------------------------------------
5. Run the command file
6. After signing on to Windows, run "netsh interface ipv4 show config" again and compare the output from your first invocation.
The contents of the restart command file are the result of talking to some knowledgeable tech support guys at Tim Wiener (call on Friday or Saturday night after 8:00 PM to get a hold of someone who is actually interested in your problem and will help you fix it) and bits and pieces from researching the disconnect problem on different websites. If you are unfamiliar with configuring TCP/IPv4 and Merlin, do not attempt any of this and forget completely that you saw it.
Last edited: