Jump to content

WinMTR issue


Vindstot

Recommended Posts

  • Senior Member

Hello

 

Im having a strange (or as Smiley said weird) problem while getting info from winMTR. You can see it on the attached file.

Im not lagging on the servers more than Im supposed, having 125fps many times, so I dont know the effects of this issue.

If any question is needed to be answered to solve it, Ill try to answer them.

 

Thanks!

post-23197-0-86426800-1522348253_thumb.png

  • Like 1
Link to comment
Share on other sites

Run cmd, type ipconfig and type in your browser default gateway IP.

Then logon in router (admin/admin maybe? :)) and search firewall protect.

 

Second way, try turn off Windows Firewall: https://support.microsoft.com/en-us/help/4028544/windows-turn-windows-firewall-on-or-off

  • Like 1
Link to comment
Share on other sites

have you tryed just running the  ip 108.61.21.94:27960 try just using the ip  

 

reason is i us et starter pro to join servers  from and for some reason it just hates  the  jay3.clan-fa.com:27960 it always removes the 0 or some part of the  .com 

 

you can try it with just  the ip and remove the port or  try it with both

 

i just did it with the ip the  jay3.clan-fa.com with port and with out port would not work for me so try it with just the ip that should work for you 

  • Like 1
Link to comment
Share on other sites

Re-enable that Firewall. Basically your router and potentially your ISP is blocking ICMP (ping) requests. Not a big deal, and not necessarily related to your lag... as you can see, that last hop (the server) is still responding just fine, which means that your packets are getting to the destination as intended, albeit with 1 dropped packet.
Disabling firewall never solves the problem, just mitigates it (if it is the prob) and then all of your ports are open for everyone and anyone to exploit.

Port forwarding could possibly solve this issue, but would be good to know what brand/model of router you use and whether you have any third party antivirus/firewall software such as BitDefender, ZoneAlarm, Comodo, etc (...especially Comodo. That can be a PITA, it works too good. :P)

I am curious if tracert works (my guess is it won't). Open command prompt and type

tracert jay3.clan-fa.com

Your output should look something like this:

C:\Users\Xernicus>tracert -d jay3.clan-fa.com

Tracing route to jay3.clan-fa.com [178.63.72.170]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     7 ms     6 ms     7 ms  63.231.10.65
  3     8 ms     7 ms     7 ms  71.217.186.1
  4     7 ms     7 ms     9 ms  67.14.41.190
  5    48 ms    29 ms     7 ms  129.250.9.133
  6     7 ms     7 ms     8 ms  129.250.5.133
  7     8 ms    17 ms    32 ms  129.250.2.44
  8    83 ms    76 ms    76 ms  129.250.4.14
  9    87 ms    94 ms    75 ms  129.250.3.207
 10   186 ms   158 ms   197 ms  129.250.2.5
 11   185 ms   158 ms   158 ms  129.250.6.207
 12   160 ms   190 ms   161 ms  213.198.82.130
 13   168 ms   168 ms   167 ms  213.239.245.217
 14   167 ms   167 ms   169 ms  213.239.229.242
 15   162 ms   161 ms   162 ms  178.63.72.170

Trace complete.
  • Like 2
Link to comment
Share on other sites

  • Senior Member

@Kiba

Only the "108.61.21.94" worked and got different result. See first SS. Tried with 108.61.21.94:27960 and jay3.clan-fa.com:27960 as well, I get a message: Unable to resolve hostname

 

@Xernicus

I tried tha command prompt thingie, see 2nd SS. Those thing next to asterixes mean something like: no answer to request before deadline.

I only have Avast that could interfere. Avast had problems with different stuffs before.

And Firewall was immediately re-enabled.

 

By the way, thanks the answers

post-23197-0-71228300-1522366552_thumb.png

post-23197-0-66467200-1522366732_thumb.png

Link to comment
Share on other sites

Hostname can't be resolved because it's looking at the port. Ports would be used to connect to the server, for WinMTR you wouldn't use a port. And yes, looks like everything is timing out.
What make and model is your modem?

  • Like 2
Link to comment
Share on other sites

tp-link tl-r460

Alright! Think I found a good starting point.

-Log into your router's control panel

-Go to the Advanced Security Menu (under Security tab... Security -> Advanced Security)

-Make sure "Forbid ping packet from LAN port" is unchecked. If it's checked, uncheck it.

-Bump up default flood threshold (ICMP, SYN, etc) to 1000 packets / sec. Defaults are super low and would cause your router to drop packets. Though if they're higher, don't lower them.

-Click save.

 

See if that helps.

  • Like 2
Link to comment
Share on other sites

  • Senior Member

Forbid ping packet from LAN port was already unchecked. Set that 3 flood threshold to 1000 (defaults were indeed low).

Im getting same results in WinMTR

Link to comment
Share on other sites

Add a port exception to Operating System Firewall: UDP 27960

You could also go to Firewall Advanced Settings and config the port's in and out rules.
In Win 10, I lower User Activity Control all the way in Users.
I turn off App control in Defender.
WinMTR is an outgoing(and ingoing) application.
It helps to add computer's personal IP: 192.168.0.xx(DDNS) to Port triggering.
Forward the game's port in and out too.

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.