Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Yatti420]

D-Link DIR-655 B2 2.11NA - Ping Issues

Hello everybody,

Sad that I have to come on the forums to get a second opinion on this.. I think I have a routing issues between to rogers IP blocks.. 99x to 173x .. Doesn't seem to be functioning when I attempt to ping my secondary household both with Rogers packages..
 
There seems to be either a server blocking my requests (one way only) or a big routing issue on this block..
 
House 1 - Cisco DPC3825 Bridged to D-Link DIR-655 (rogers DNS for testing) {WAN Ping Allowed}
House 2 - Hitron CGN2-ROG Gateway/Router (rogers DNS for testing) {WAN Ping Allowed}
 
Pings to google/hitron from house 2..
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 2ms, Average = 1ms

ping google.ca

Pinging google.ca [64.71.249.49] with 32 bytes of data:
Reply from 64.71.249.49: bytes=32 time=13ms TTL=57
Reply from 64.71.249.49: bytes=32 time=16ms TTL=57
Reply from 64.71.249.49: bytes=32 time=18ms TTL=57
Reply from 64.71.249.49: bytes=32 time=15ms TTL=57

Ping statistics for 64.71.249.49:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 13ms, Maximum = 18ms, Average = 15ms
 
Tracert from House 1 to google..
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

tracert google.ca

Tracing route to google.ca [64.71.249.49]
over a maximum of 30 hops:

  1     1 ms     2 ms     1 ms  vlan1.phub.net.cable.rogers.com [192.168.0.1]
  2    10 ms    10 ms     9 ms  7.8.0.1
  3    17 ms    13 ms    10 ms  69.63.254.229
  4    15 ms    13 ms    15 ms  24.156.157.86
  5    15 ms    18 ms    15 ms  69.63.249.205
  6    13 ms    18 ms    18 ms  69.63.249.61
  7    14 ms    14 ms    17 ms  69.63.248.170
  8    16 ms    12 ms    17 ms  64.71.249.49

Trace complete.
 
Now I can ping from House1 to House 2 without issues.. However attempting to go from House 2 (non bridge) to House 1 (bridged) results in destination host unreachable or requests time out.. This is not the case the other way around..
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

tracert 173.32.75.8

Tracing route to CPE1caff7df5aba-CMbcc8101002de.cpe.net.cable.rogers.com [173.32
.75.8]
over a maximum of 30 hops:

  1     1 ms     1 ms     2 ms  vlan1.phub.net.cable.rogers.com [192.168.0.1]
  2     9 ms     8 ms    13 ms  7.8.0.1
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *     69.63.254.229  reports: Destination net unreachable.

Trace complete.

tracert 173.32.75.8

Tracing route to CPE1caff7df5aba-CMbcc8101002de.cpe.net.cable.rogers.com [173.32
.75.8]
over a maximum of 30 hops:

  1     1 ms     2 ms     1 ms  vlan1.phub.net.cable.rogers.com [192.168.0.1]
  2    11 ms    10 ms    10 ms  7.8.0.1
  3     *     69.63.254.229  reports: Destination net unreachable.

Trace complete.

 This is driving me nuts not being able to ping or connect to my secondary household.. Oddly I can access the router (dlink) at house #1 via webgui on a different port..

Any help would be greatly appreciated as my connection works one way.. But not the other.. Dissapointed to say the least.. It's been a week like this.. The only thing I could consider on my end (house 1) is debridge the cisco and try again.. 69.63.254.229 what is this? Why is is it blocking my connection to the 173x block? Yet from 173x I can ping and router 99x no issues..
 
Thanks in advance,
Yatti420
 

[FurryNutz]

Link>Welcome!

• Was a Factory Reset performed before and after any firmware updates?
• Was the router working before any firmware updates?

Please review and post your findings and answers from here:
Router Troubleshooting Suggestions and Tips: Router Troubleshooting Suggestions and Tips

Are you sharing something at on house that your trying to gain access remotely?

Are you configuring any port forwarding or Virtual Server options?

[Yatti420]

Hi FurryNutz,

Yes the router was factory reset after the firmware upgrade to 2.11NA.. I may try reflashing it and see if that will fix it.. I usually follow all the rules for doing this type stuff... Based on the tracert it appears 69.63.254.229 keeps blocking my connection oddly.. Gives me destination host unreachable most times..

[FurryNutz]

Test with Traffic Shaping and QoS disabled as well.