We have a strange phenomenon in a total cisco environment:
Every few days various (NT 4.0) clients start to multicast on 184.108.40.206 (srvloc.mcast.net). This affects even completely unused switchports and causes a complete network overload until the clients disconnect and are rebootet.
Does anyone know how this could be caused or how this could be prevented
Multicast is multicast and until you resolve the root cause every port is going to receive the broadcasts. Apply access lists to the router to deny multicast packets passing through the router, however, on the switch there's little that you can do.
220.127.116.11 is per RFC 2165 and SRVLOC (Service Location General Multicast) is used to find directory services. If you have Novell or Windows Directory services the issue you're encountering indicates there's an issue with directory service operations (access), the directory service clients or directory service clients being installed without an active directory service.
Might want to sniff the network and figure out if someone has installed or change directory service configurations
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.