• February 22, 2025, 03:25:43 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: ping from router to PC drops packets  (Read 11855 times)

mestar

  • Level 1 Member
  • *
  • Posts: 2
ping from router to PC drops packets
« on: February 21, 2014, 02:41:50 PM »
I have two pcs connected to the dir-657, one (A) can ping wan addresses, the other (B) can't.

When I ping from B to A, it works perfectly, when I ping A to B, I get something like this:

Reply from 192.168.0.201: bytes=32 time<1ms TTL=128
Request timed out.
Request timed out.
Reply from 192.168.0.201: bytes=32 time<1ms TTL=128
Reply from 192.168.0.201: bytes=32 time<1ms TTL=128
Reply from 192.168.0.201: bytes=32 time<1ms TTL=128
Request timed out.
Reply from 192.168.0.201: bytes=32 time<1ms TTL=128



The same happens when I ping directly from the router.  The A pings fine, B loses packets:

No response from host, retrying...
Response from 192.168.0.201 received in 1 milliseconds. TTL = 128
Response from 192.168.0.201 received in 1 milliseconds. TTL = 128
Response from 192.168.0.201 received in 2 milliseconds. TTL = 128
No response from host, retrying...
Response from 192.168.0.201 received in 1 milliseconds. TTL = 128
Response from 192.168.0.201 received in 1 milliseconds. TTL = 128


I tried switching the network cables, same thing.  I forced the speed from 1Gbps to 10 Mbps, same thing. 

Pinging from B to router works 100%, ping from router to B drops packets.  No idea how to solve this problem.

Everything worked fine yesterday, then I turned off "Enable DNS relay", that is the moment when pc B lost its internet connection.  I enabled it back, but it is still not connecting to the address.

Please help.
Logged

mestar

  • Level 1 Member
  • *
  • Posts: 2
Re: ping from router to PC drops packets
« Reply #1 on: February 21, 2014, 04:09:18 PM »

Some more information.  Both PCs use DHCP, and PC B seems to connect to the outside internet only when plugged directly into the cable modem, and does not work when DIR-657 is in between.  PC A works trough DIR657 fine, I did not try it directly into cable modem.

I did a reboot and adapter disable and enable after each change, and also ipconfig /release and /renew.



Trace results, when I plug the offending PC (B) directly into the cable modem:


-------------------------------------------------------------------------------------------------
C:\>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

  1     6 ms     9 ms     7 ms  172.25.72.1
  2     9 ms    11 ms    11 ms  dh121-189.xnet.hr [83.139.121.189]
  3     9 ms     7 ms    11 ms  dh121-189.xnet.hr [83.139.121.189]
  4    23 ms    22 ms    22 ms  dialup-212.162.26.105.frankfurt1.mik.net [212.16
2.26.105]
  5    36 ms    37 ms    39 ms  vl-3101-ve-127.ebr1.Budapest1.Level3.net [4.69.2
01.149]
  6    38 ms    40 ms    39 ms  ae-43-43.ebr3.Frankfurt1.Level3.net [4.69.201.11
0]
  7    37 ms    39 ms    40 ms  ae-73-73.csw2.Frankfurt1.Level3.net [4.69.163.6]

  8    37 ms    43 ms    80 ms  ae-2-70.edge3.Frankfurt1.Level3.net [4.69.154.71
]
  9    39 ms    37 ms    39 ms  4.68.70.186
 10    39 ms    51 ms    49 ms  209.85.241.110
 11    38 ms    39 ms    41 ms  72.14.234.235
 12    40 ms    46 ms    39 ms  209.85.254.112
 13     *        *        *     Request timed out.
 14    39 ms    40 ms    40 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.
------------------------------------------------------------------------------------------------


When I plug DIR-657 into the cable modem, and PC B into the DIR-657:


------------------------------------------------------------------------------------------------
C:\>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dlinkrouter [192.168.0.1]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5    39 ms     *        *     dialup-212.162.26.105.frankfurt1.mik.net [212.16
2.26.105]
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *       47 ms  ae-63-63.csw1.Frankfurt1.Level3.net [4.69.163.2]

  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *       43 ms  209.85.241.110
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *       43 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.
------------------------------------------------------------------------------------------------




And from PC A, also plugged into DIR-657:




------------------------------------------------------------------------------------------------
C:\>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dlinkrouter [192.168.0.1]
  2     7 ms     7 ms     7 ms  172.25.72.1
  3    10 ms    11 ms     7 ms  dh121-185.xnet.hr [83.139.121.185]
  4     7 ms     7 ms     7 ms  dh121-185.xnet.hr [83.139.121.185]
  5    22 ms    24 ms    21 ms  dialup-212.162.26.105.frankfurt1.mik.net [212.16
2.26.105]
  6    37 ms    37 ms    37 ms  vl-3101-ve-127.ebr1.Budapest1.Level3.net [4.69.2
01.149]
  7    37 ms    37 ms    37 ms  ae-43-43.ebr3.Frankfurt1.Level3.net [4.69.201.11
0]
  8    38 ms    38 ms    37 ms  ae-63-63.csw1.Frankfurt1.Level3.net [4.69.163.2]

  9     *       39 ms    38 ms  ae-1-60.edge3.Frankfurt1.Level3.net [4.69.154.7]

 10    48 ms    39 ms    44 ms  4.68.70.186
 11    37 ms    37 ms    37 ms  209.85.240.64
 12    39 ms    39 ms    46 ms  209.85.251.178
 13    41 ms    42 ms    40 ms  209.85.254.118
 14     *        *        *     Request timed out.
 15    39 ms    38 ms    39 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.
------------------------------------------------------------------------------------------------







Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: ping from router to PC drops packets
« Reply #2 on: February 22, 2014, 11:21:33 AM »
Link>Welcome!

  • What Hardware version is your router? Look at sticker under router.
  • Link>What Firmware version is currently loaded? Found on the routers web page under status.
  • What region are you located?
  • Has a Factory Reset been performed?


Internet Service Provider and Modem Configurations
  • What ISP Service do you have? Cable or DSL?
  • What ISP Modem Mfr. and model # do you have?
  • What ISP Modem service link speeds UP and Down do you have?
  • Check ISP MTU requirements, Cable is usually 1500, DSL is around 1492 down to 1472. Call the ISP and ask. Link>Checking MTU Values

Router and Wired Configurations
Some things to try: - Log into the routers web page at 192.168.0.1. Use IE, Opera or FF to manage the router. Besure to log into the Admin account on the router.
  • Turn off ALL QoS or Disable Traffic Shaping (DIR only) GameFuel (DGL only and if ON.) options, Advanced/QoS
  • Turn off Advanced DNS Services if you have this option under Setup/Internet/Manual or under Setup/PARENTAL CONTROL/Set to>None: Static IP or Obtain Automatically From ISP.
  • Enable Use Unicasting (compatibility for some ISP DHCP Servers) under Setup/Internet/Manual.
  • Turn on DNS Relay under Setup/Networking. Link>Finding Faster DNS Addresses using Name Bench and input new DNS addresses under Setup/Internet/Manual.
  • 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 and maintain consistency for applications that need to connect as well as mapped drives.
  • Ensure devices are set to auto obtain an IP address.
  • If IPv6 is an option on the router, select Local Connection Only or Disable IPv6 options under Setup/IPv6.
  • Set Firewall settings to Endpoint Independent for TCP and UDP under Advanced/Firewall. Enable or Disable SPI to test.
  • Enable uPnP and Multi-cast Streaming under Advanced/Networking. Disable uPnP for testing Port Forwarding rules. Enable IPv6 Multi-cast Streaming for routers that have a Media Server option. Disable IPv6 Multi-cast Streaming if IPv6 or Media Server is not being used.
  • Turn off WISH, and WPS under Advanced.
  • 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 current Time Zone, Date and Time. Use an NTP Server feature. Tools/Time.
  • Check cable between Modem and Router and PCs, swap out to be sure. Link> Cat6 is recommended.

Router Placement
Forum User - "Well I feel really dumb. After moving the router away from other electronic devices my speeds are back to normal. Just a heads up for anyone experiencing slow speeds, you might want to move it away from other electronics and see if that helps."
6" minimum safe distance between devices.

3rd Party Security Software Configurations
  • Turn off all anti virus and firewall programs on PC while testing. 3rd party firewalls are not generally needed when using routers as they are effective on blocking malicious inbound traffic.
  • Turn off all devices accept for one wired LAN PC while testing.
  • Disable any downloading client software managers, i.e. Torrents or similar.
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: ping from router to PC drops packets
« Reply #3 on: April 23, 2014, 07:38:13 AM »
Any status on this?

Quote from: mestar on February 21, 2014, 04:09:18 PM
Some more information.  Both PCs use DHCP, and PC B seems to connect to the outside internet only when plugged directly into the cable modem, and does not work when DIR-657 is in between.  PC A works trough DIR657 fine, I did not try it directly into cable modem.

I did a reboot and adapter disable and enable after each change, and also ipconfig /release and /renew.



Trace results, when I plug the offending PC (B) directly into the cable modem:


-------------------------------------------------------------------------------------------------
C:\>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

  1     6 ms     9 ms     7 ms  172.25.72.1
  2     9 ms    11 ms    11 ms  dh121-189.xnet.hr [83.139.121.189]
  3     9 ms     7 ms    11 ms  dh121-189.xnet.hr [83.139.121.189]
  4    23 ms    22 ms    22 ms  dialup-212.162.26.105.frankfurt1.mik.net [212.16
2.26.105]
  5    36 ms    37 ms    39 ms  vl-3101-ve-127.ebr1.Budapest1.Level3.net [4.69.2
01.149]
  6    38 ms    40 ms    39 ms  ae-43-43.ebr3.Frankfurt1.Level3.net [4.69.201.11
0]
  7    37 ms    39 ms    40 ms  ae-73-73.csw2.Frankfurt1.Level3.net [4.69.163.6]

  8    37 ms    43 ms    80 ms  ae-2-70.edge3.Frankfurt1.Level3.net [4.69.154.71
]
  9    39 ms    37 ms    39 ms  4.68.70.186
 10    39 ms    51 ms    49 ms  209.85.241.110
 11    38 ms    39 ms    41 ms  72.14.234.235
 12    40 ms    46 ms    39 ms  209.85.254.112
 13     *        *        *     Request timed out.
 14    39 ms    40 ms    40 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.
------------------------------------------------------------------------------------------------


When I plug DIR-657 into the cable modem, and PC B into the DIR-657:


------------------------------------------------------------------------------------------------
C:\>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dlinkrouter [192.168.0.1]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5    39 ms     *        *     dialup-212.162.26.105.frankfurt1.mik.net [212.16
2.26.105]
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *       47 ms  ae-63-63.csw1.Frankfurt1.Level3.net [4.69.163.2]

  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *       43 ms  209.85.241.110
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *       43 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.
------------------------------------------------------------------------------------------------




And from PC A, also plugged into DIR-657:




------------------------------------------------------------------------------------------------
C:\>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dlinkrouter [192.168.0.1]
  2     7 ms     7 ms     7 ms  172.25.72.1
  3    10 ms    11 ms     7 ms  dh121-185.xnet.hr [83.139.121.185]
  4     7 ms     7 ms     7 ms  dh121-185.xnet.hr [83.139.121.185]
  5    22 ms    24 ms    21 ms  dialup-212.162.26.105.frankfurt1.mik.net [212.16
2.26.105]
  6    37 ms    37 ms    37 ms  vl-3101-ve-127.ebr1.Budapest1.Level3.net [4.69.2
01.149]
  7    37 ms    37 ms    37 ms  ae-43-43.ebr3.Frankfurt1.Level3.net [4.69.201.11
0]
  8    38 ms    38 ms    37 ms  ae-63-63.csw1.Frankfurt1.Level3.net [4.69.163.2]

  9     *       39 ms    38 ms  ae-1-60.edge3.Frankfurt1.Level3.net [4.69.154.7]

 10    48 ms    39 ms    44 ms  4.68.70.186
 11    37 ms    37 ms    37 ms  209.85.240.64
 12    39 ms    39 ms    46 ms  209.85.251.178
 13    41 ms    42 ms    40 ms  209.85.254.118
 14     *        *        *     Request timed out.
 15    39 ms    38 ms    39 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.
------------------------------------------------------------------------------------------------








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.