cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
433
Views
0
Helpful
2
Replies
Highlighted
Beginner

Cisco RV220W Router not pinging the wrong IP

I have an issue to where the ip of router should be 192.168.1.x, but when I ping it it shows 127.0.53.53 is there a setting that I might have missed? I have an RV220W Cisco router. Any ideas/suggestions would be great!

Thanks in Advance,
Travis

Everyone's tags (1)
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Beginner

Hi travis,I'm Ricardo My

Hi travis,

I'm Ricardo My recommendation is try to ping your router or to access it in an isolated network (with not wan cable on the RV to start).

I found multiple cases where the other customer a re getting this 127.0.53.53 loop address in response to a ping

I made a deeper investigation where I found  the ICANN today announced the approval of the Name Collision Occurrence Management Framework (https://www.icann.org/en/system/files/files/name-collision-framework-30jul14-en.pdf), basically A name collision occurs when a user unknowingly accesses a name that has been delegated in the public DNS when the user's intent is to access a resource identified by the same name in a private network.

finally there is a video that you may find useful:

https://www.icann.org/resources/pages/name-collision-2013-12-06-en

Please bear in mind that we will be happy to help at any time.

 

 

View solution in original post

2 REPLIES 2
Highlighted
Beginner

Hi travis,I'm Ricardo My

Hi travis,

I'm Ricardo My recommendation is try to ping your router or to access it in an isolated network (with not wan cable on the RV to start).

I found multiple cases where the other customer a re getting this 127.0.53.53 loop address in response to a ping

I made a deeper investigation where I found  the ICANN today announced the approval of the Name Collision Occurrence Management Framework (https://www.icann.org/en/system/files/files/name-collision-framework-30jul14-en.pdf), basically A name collision occurs when a user unknowingly accesses a name that has been delegated in the public DNS when the user's intent is to access a resource identified by the same name in a private network.

finally there is a video that you may find useful:

https://www.icann.org/resources/pages/name-collision-2013-12-06-en

Please bear in mind that we will be happy to help at any time.

 

 

View solution in original post

Highlighted
Beginner

Thank you Ricardo, that's

Thank you Ricardo, that's what I was looking for

CreatePlease to create content
Content for Community-Ad