Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

"The specified module could not be found"

Unanswered Question
Jun 20th, 2006
User Badges:

Hi all.

I have a problem with the streaming cachs - WCCP 2

My SW6500, config with WCCP v2 like that:

Interface vlan 100 connect to internet.

Interface vlan 103 connect to CE7305.

Interface vlan 105 connect to clients.


ip wccp web-cache

ip wccp 81

ip wccp 82

interface Vlan101

ip address

ip wccp web-cache redirect out

ip wccp 81 redirect out

ip wccp 82 redirect out


interface Vlan103

ip address


interface Vlan105

ip address

And the CE 's config:


ip wccp version 2

wccp router-list 1

wccp web-cach router-list-num 1

wccp wmt router-list-num 1

ip default-gateway

interface gi 1/0

ip address

My PC has ip:

This CE7305 work perfectly with HTTP caching.

I 's enabled and registered WMT licences.

But when I watch films in some internet website ( MMS over HTTP: http://phimanh.net ), my Window Media Player appears. But It doesn't connect to internet, and has error: " The specified module could not be found "

I don't know why it has this error.

I usual saw fiml in this website before using CE7305.

Help me, plz

Tran Chung

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
songokudt5 Tue, 06/20/2006 - 17:17
User Badges:

Dear all.

Have you ever had this problem?

Help me, plz.


Tran Chung

songokudt5 Thu, 06/22/2006 - 00:10
User Badges:

Do you know how to fix it ?

Help me.

If I turn-on Windows Media Player before click this web-site. It word ok.

But if i click "Watch button" ( don't open Window Media Player before), the internet exployer will open Window Media Player, the error appear: "the specified modul could not be foung".

Help me,


Gilles Dufour Thu, 06/22/2006 - 02:55
User Badges:
  • Cisco Employee,

this is a mediaplayer error message and I have no idea what this is.

If this is a network issue [or if you believe this is a network issue], then capture a sniffer trace for all traffic going in and out of the cache [the cache !!! not the client] and compare the working scenario with the non-working scenario.

If this is not network related, than this is an application/windows problem and there is not much we can do.



This Discussion