cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3954
Views
5
Helpful
5
Replies

cannot download IOS from CCO

colpal
Level 1
Level 1

When I try to download an image from CCO using RME>software management>library>add images>CCO I get a message saying http://www.cisco.com:80 is not found. I do not have the proxy login/password set in my profile but I should not need this as I can open a TAC case and I can get to this forum so why can't I download an image? Thanks.

EDIT: I posted this message then clicked on the URL I listed and I got right to the cisco web site.

5 Replies 5

david.bradley
Level 1
Level 1

You must have your Cisco.com username/login set against you cisoworks username. Downloading the images is just the same as downloading the iamage direct from the software centre website, you can't download an image without a login

Thanks for the reply. FYI, The login I use for the Cisco2000 server is admin which has network admin priveliges which of course allows you to add images. I have my CCO login and password set in the admin profile. The error I get is " Internal Error : Can't connect to www.cisco.com:80 (Bad hostname 'www.cisco.com') . Check the network availablity to www.cisco.com. Check www.cisco.com exists in the DNS.If the access to the Internet is through a proxy, enter the correct proxy name and port in the configuration.. "

I have discovered that when using the browser on the server, it will go to other sites like http://www.ibm.com for example but not http://www.cisco.com. It says it cannot find that site. It is netscape and an older one at that, using java 1.1.5 (!!) However it will go to http://cisco.com. So where in the server is the file which shows the URL of cisco as www.cisco.com so I can change it? Thanks.

There are 2 places to configure the Proxy server in CiscoWorks:

1) RME > Administration > Proxy

2) Management Connection > Administration > Set HTTP Proxy

Make sure that you have your proxy configuration correct in RME as per point 1)

HTH

That was the answer; the proxy was unset in RME. It was set in Management Connection. Thanks for your help, marcjone. modules should talk to each other