"connection timed out/lost" and not showing server browser/list point to networking problems. Download and run as administrator the netfix (this was shared by MTA AC Team). It usually helps to fix this kind of problem, if not, open this: https://discord.com/channels/278474088903606273/278521065435824128/599929249868283908 (it should forward you to Dutchman's guide on MTA discord)
ECHO ONECHO Attempting to fix your problem.netsh onlinenetsh winsock resetnetsh winhttp reset proxynetsh interface ipv4 resetnetsh interface ipv6 resetnetsh int ip reset c:\resetLog.txtnetsh interface tcp resetnetsh interface portproxy resetnetsh interface httpstunnel resetnetsh rpc resetnetsh http flush logbuffernetsh winsock reset allnetsh int 6to4 reset allnetsh int ipv4 reset allnetsh firewall deletenetsh int ipv6 reset allnetsh advfirewall resetnetsh int httpstunnel reset allnetsh int isatap reset allnetsh int portproxy reset allnetsh int tcp reset allnetsh int teredo reset allnetsh int tcp set global autotuninglevel=normalnetsh interface tcp set heuristics disabledReset Winsock controlnetsh branchcache resetnetsh branchcache flushfsutil resource setautoreset true C:\fsutil resource setautoreset trueipconfig /flushdnsPAUSE
Resetting the TCP/IP stack can be a useful way to clear any issues that might be preventing your computer from accessing the Internet or network. In Windows, there are lots of things that could screw up a systems TCP/IP stack and lead to connectivity issues. This is because Microsoft Windows stores most network information including the TCP/IP stack details in the registry and there are lots of ways for third party applications to modify this information.Luckily Microsoft also implemented a way to reset the TCP/IP stack back to defaults which can clear up a variety of issues. The command to clear and reset the TCP/IP stack (on Windows XP, 7, 8 and 10) is:netsh int ip reset c:\resetlog.txtThe command must be run in an elevated command prompt windows (WIN+X) and it can be destructive in terms of IPv4 info set on an adapter, so…like don’t run it remotely on a server with a static IP.But I digress. The issue I’m really getting to is related to Homegroup membership and the Windows 10 upgrade. I found that if you’re upgrading from Windows 7 to Windows 10 and the original system you’re upgrading was joined to a homegroup, then the upgraded system might have issues with the TCP/IP stack (I.e. obtaining an IP address via DHCP).[the problem]I spent hours troubleshooting this on several freshly upgraded systems running Windows 10 that couldn’t connect to the network because they couldn’t obtain an IP from the DHCP server. All machines exhibited the same issue and all machines were previously joined to a homegroup (not a domain). Here are the symptoms:The system is upgraded from Windows 7 to Windows 10 build 1511 and works as expected but cannot obtain an IP address via Ethernet or Wi-Fi.The system works normally if a static IP is assigned.Resetting the TCP/IP stack results in the following information:netsh int ipv4 resetResetting interface, OK!Resetting Unicast Address, OK!Resetting Neighbor, OK!Resetting Path, OK!Resetting , failed.Access is denied.Resetting , OK!Restart the computer to complete this action[the solution]In essence having had the systems joined to a homegroup somehow messed up the TCP/IP stack in windows 10 after the upgrade to the point that the system cannot obtain an IP address from DHCP. Here’s how to fix the issue:Open Regedit.Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nsi and expand that folder.Expand the subfolder named {eb004a00-9b1a-11d4-9123-0050047759bc} and right-click the subfolder named 26. Select Permissions… and ensure that for Everyone the Full Control box is checked.Press WIN+X to open a command prompt with elevated permissions. Type netsh int ip reset and hit enter. Now you should see the following results:Resetting , OK!Restart the computer to complete this actionReboot the system.That’s it maybeI founded one YoutTube video tutorial, maybe it helps youIf not, better solution than wasting ur time to "fix it" re-install your windows. Tell me if this helps you
This might or might not work, but I would like to suggest you to do two things and try.Restart your router/modem or whatever device is routing your internet.If the above doesn't work ^ try to use a VPN and check if your MTA detects internet and shows the list of the servers.
The best solution way is to reset your computer and do a clean installation for MTA. If you try to solve it by cmd or etc. you will put a lot of effort and you can't fix %90.
If you are using a network cable, try to use WI-FI. Else you can use a network cable
I already did that nothing happened