Print

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

[FurryNutz]

AH Ha...OpenDNS. I might switch back to ISP DNS and see if that exhibits the same thing, test with DNS relay ON and OFF.

[DeeLinkz]

Why Ah-Ha...? 

Can't even begin to describe how much time (months) and effort was expended in trouble-shooting the previous connection problem a few years ago - which was 'magically' solved by switching to OpenDNS servers. So, we'll see how it goes before switching back to ISP DNS (not even sure what that is for CenturyLink)... 

Will not discount that as something to try though...

So, should the DNS Relay still be in the 'off' position, or back 'on'...?

Are there any other settings we changed that can/should be changed back, since they did not make any difference? Or are those changes good anyway?

[FurryNutz]

Try testing DNS both OFF and ON and see how it goes. I don't use OpenDNS and use ISP DNS. I have left this all ways on. However since your ISP is DSL and the modem isn't bridged and we can't find a way to use DMZ on the modem, the DNS being sent to the modem is being translated from the ISP address to the private IP address of 192.168 so the modem is handling the DNS. It's preferred to either have the modem set up with DMZ or put the modem into bridged mode and let modem pass everything to the 4500 router and so it gets full DNS addresses. Then DNS relay would more effective.

[DeeLinkz]

Before coming to this forum for help, we had run the ipconfig /flushdns command, but did not know about the additional /release and /reset commands. Since running those yesterday we have not gone to 'local only' on the wired PC... 

Will make a note to try those first in the future, if this issue crops up again.

Do you recommend leaving the other router settings we changed as is, for instance multi-cast? Why would we have 3 IP addresses listed under the header 'IGMP Multicast Memberships' on the router Device Information page? Not familiar with this... 

Thanks again for taking the time to help with this problem! Will see how it goes through the day today, and hope we have this resolved. Will not be able to test the system with wireless until the weekend, when the laptop gets back from the road...

[FurryNutz]

Yes I would leave the settings as is. Do a save configuration to file so you have them saved in case you have to factory reset the router. I would also investigate getting the DSL Modem bridged.

Enjoy the router man. 

[DeeLinkz]

Things are still going well - no dropped connections - thanks again... 

But, noticed that we are getting dozens of these logs in the router:

Blocked outgoing ICMP packet (ICMP type 3) from (Our DirecTV DVR Receiver) to (Our OpenDNS servers)

No other devices on our network are showing up in these entries.

What might be causing this - and is it a problem, or just ignore... ?

[FurryNutz]

Put the DVR in to the DMZ?
What NAT settings are you using ? Endpoint Independent?

[fraggboy]

For me, I have a HR24 hooked up, and I don't see that message when I have turned on logging for everything.

All this means is that the ICMP destination unreachable message is generated by a router to inform the source host that the destination unicast address is unreachable.

The new firmware that the DVR downloaded has a 'power saver' mode (Under Menu -> Settings & Help -> Settings -> Power Saving).  I'm sure your OpenDNS server is reporting to the 4500 that the DVR is not reachable at times.

You can safely ignore this message.

[DeeLinkz]

OK - Thanks for the explanation!

[DeeLinkz]

DMZ is not enabled, endpoint independent is checked both places...

I will try putting DVR in DMZ and see what happens... 

[FurryNutz]

Any status on this?

[DeeLinkz]

Thanks FN - Will have to wait a few days to test things and get back...