• March 28, 2024, 09:42:45 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: HELP Router constantly Blocks ICMP  (Read 11500 times)

Anikiri

  • Level 1 Member
  • *
  • Posts: 1
HELP Router constantly Blocks ICMP
« on: December 30, 2012, 09:47:56 AM »

Dear Knowledgeable Users,

I have one problem with my DGL-4500 and it is causing me severe headaches. I am attempting to play Counterstrike:GO on my desktop and sometimes it lags extremely hard. The one thing that stands out within the router log is the following:

Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.130 to 74.91.115.157

and recently i found it doing this:

[INFO]   Sun Dec 30 12:50:39 2012   Blocked incoming TCP packet from 74.125.142.188:5228 to 174.115.34.81:56275 as FIN:ACK received but there is no active connection
[INFO]   Sun Dec 30 12:50:38 2012   Blocked incoming TCP packet from 74.125.142.188:5228 to 174.115.34.81:57458 as FIN:ACK received but there is no active connection
[INFO]   Sun Dec 30 12:50:38 2012   Blocked incoming TCP packet from 74.125.142.188:5228 to 174.115.34.81:60242 as FIN:ACK received but there is no active connection
[INFO]   Sun Dec 30 12:50:36 2012   Blocked incoming TCP packet from 74.125.142.188:5228 to 174.115.34.81:40820 as FIN:ACK received but there is no active connection
[INFO]   Sun Dec 30 12:50:29 2012   Blocked incoming TCP packet from 74.125.142.188:5228 to 174.115.34.81:56275 as FIN:ACK received but there is no active connection
[INFO]   Sun Dec 30 12:50:29 2012   Blocked incoming TCP packet from 74.125.133.125:5222 to 174.115.34.81:50349 as PSH:ACK received but there is no active connection
[INFO]   Sun Dec 30 12:50:28 2012   Blocked incoming TCP packet from 74.125.142.188:5228 to 174.115.34.81:57458 as FIN:ACK received but there is no active connection
[INFO]   Sun Dec 30 12:50:28 2012   Blocked incoming TCP packet from 74.125.142.188:5228 to 174.115.34.81:60242 as FIN:ACK received but there is no active connection
[INFO]   Sun Dec 30 12:50:26 2012   Blocked incoming TCP packet from 74.125.142.188:5228 to 174.115.34.81:40820 as FIN:ACK received but there is no active connection
[INFO]   Sun Dec 30 12:50:23 2012   Blocked incoming TCP packet from 66.196.116.132:8996 to 174.115.34.81:41420 as FIN:ACK received but there is no active connection
[INFO]   Sun Dec 30 12:50:21 2012   Blocked incoming TCP packet from 74.125.133.125:5222 to 174.115.34.81:50349 as PSH:ACK received but there is no active connection
[INFO]   Sun Dec 30 12:50:18 2012   Above message repeated 1 times
[INFO]   Sun Dec 30 12:50:18 2012   Blocked incoming TCP packet from 74.125.142.188:5228 to 174.115.34.81:57458 as FIN:ACK received but there is no active connection
[INFO]   Sun Dec 30 12:50:16 2012   Blocked incoming TCP packet from 74.125.133.125:5222 to 174.115.34.81:50349 as PSH:ACK received but there is no active connection
[INFO]   Sun Dec 30 12:50:16 2012   Blocked incoming TCP packet from 74.125.142.188:5228 to 174.115.34.81:40820 as FIN:ACK received but there is no active connection
[INFO]   Sun Dec 30 12:50:15 2012   Blocked incoming TCP packet from 74.125.133.125:5222 to 174.115.34.81:50349 as PSH:ACK received but there is no active connection
[INFO]   Sun Dec 30 12:50:15 2012   Above message repeated 1 times

This happens to many machines but it is most noticeable when I play online games and lag severely.

If anyone has any idea of why this is persisting, please help me. I am thoroughly out of ideas.


Thank you.
« Last Edit: December 30, 2012, 09:52:05 AM by Anikiri »
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: HELP Router constantly Blocks ICMP
« Reply #1 on: December 31, 2012, 03:47:55 PM »

Link>Welcome!
What Hardware version is your router? Look at sticker under router.
Link>What Firmware version is currently loaded? Found on routers web page under status.
What region are you located?
Are you wired or wireless connected to the router?
Has a Factory Reset been performed?

What ISP Service do you have? Cable or DSL?
What ISP Modem do you have? Stand Alone or built in router?
What ISP Modem make and model do you have?
If this modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems.
Double NAT
To tell if the modem is bridged or not, look at the routers web page, Status/Device Info/Wan Section, if there is a 192.168.0.# address in the WAN IP address field, then the modem is not bridged.
If the modem can't be bridged then see if the modem has a DMZ option and input the IP address the router gets from the modem and put that into the modems DMZ.

Some things to try: - Log into the routers web page at 192.168.0.1. Use IE, Opera or FF to manage the router.
Turn off ALL QoS or Disable Traffic Shaping (DIR only) GameFuel (DGL only and if ON.) options. Advanced/QoS or Gamefuel.
Turn off Advanced DNS Services if you have this option under Setup/Internet/Manual.
Turn on DNS Relay under Setup/Networking.
Setup DHCP reserved IP addresses for all devices ON the router. Setup/Networking. This ensures each devices gets its own IP address when turned on and connected, eliminates IP address conflicts and helps in troubleshooting.
Ensure devices are set to auto obtain an IP address.
Set Firewall settings to Endpoint Independent for TCP and UDP under Advanced/Firewall.
Enable uPnP and Multi-cast Streaming under Advanced/Networking. Disable uPnP for testing Port Forwarding rules.
WAN Port Speed set to Auto or specific speed? Some newer ISP modems support 1000Mb so manually setting to Gb speeds can be supported by the router. Advanced/Advanced Networking/WAN Port Speed
Set Time and Time Zone under Tools/Time.

You might also need to set up Gamefuel to help out for gaming:
DGL-4500 Gaming and Gamefuel for XBL
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: HELP Router constantly Blocks ICMP
« Reply #2 on: February 12, 2013, 02:26:01 PM »

Any status on this?  ???
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

Hard Harry

  • Guest
Re: HELP Router constantly Blocks ICMP
« Reply #3 on: February 12, 2013, 03:13:42 PM »

Well first thing I notice is those logs don't directly show the problem. Lets break it down:

[INFO]   Sun Dec 30 12:50:39 2012   Blocked incoming TCP packet from 74.125.142.188(Google server):5228 (port used for Google Play) to 174.115.34.81(IP Rogers gave you):56275(random port set by UPnP) as FIN:ACK (waiting for final acknowledgment) but there is no active connection.

So your firewall blocked traffic coming from Google Play going to your router because the device that tried to establish the connection (probably a Android phone on your network) was no longer communicating. The way to keep this from happening is go to Advanced > Firewall and set TCP Endpoint Filtering to Address Restricted.

Now your first error is more relevant. Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.130 to 74.91.115.157. Your firewall blocked your computer playing CS from pinging your server.  But a blocked ping does hurt your connection. Probably your game is pinging the server to display some type of latency read out built in. And probably does it when you start getting latency. So I think that is more a symtom of the problem, and not the source.

What I would suggest is next time you get lag; Start > Run > CMD > tracert 74.91.115.157. Then post it back here. It will show where the lag is coming from.
Logged