Skip to main content

HTTP 502 Proxy Error While accessing Cisco ASDM

Are you getting the following error while accessing ASDM from your Client machine that is behind your corporate Firewal (TMG-2010)?
Unable to Launch ASDM from 172.16.1.1 (IP Address)
Unable to tunnel through proxy. Proxy returns “HTTP/1.1 502 Proxy Erro (Forefron TMG denied the specified Uniform Resource Locator (URL).”
So the actual restriction is in TMG 2010 and the connection is denied to the ASDM by TMG Default Rule, if your TMG Firewall is not configured to to access internal/external IP at which that ASA/PIX ASDM resides.
Suppose if your ASA/PIX firewall is on internal/inside network and in TMG you have created Web Access Rules so that it only allows connections from Internal to External Networks than connection from your Internal Clients to ASA/PIX can be denied by Default Web Access Rule of TMG 2010.
Either you can allow from Internal to Internal+External or You need to put exception in Allow Web access rule so that the connection from your internal networks is allowed.
Allowing all connections from internal to all internal and external networks is simpler, here I tell you how to put exceptions if your company doesn’t wants allow all connections.
For putting exception, you need to create a URL Set and Put it in allowed Exception Ruel.
Right Click Allow Web Access Rule > Properties > Select tab TO > Click ADD > Click URL Set > Click New
In the New URL Set Windows create the URL set as shown in the snap Below and give it any name, I Named it ASDM, when finished Click OK.
Once the URL Set is Created, Click Add Button to add this URL Set into the allowed destinations box.
Click OK and Apply the Changes in TMG and and Play with ASDM error Free.
Please mention if this worked for you..

Comments

Popular posts from this blog

What is Cisco Supervisor Engine?

Supervisor Engine is a module that is installed in the Cisco Chassis-based Catalyst Switches or Routers. Supervisor engine contains nearly all the same components of a fixed Cisco Switches or Routers. These Supervisor engines come in a variety of different types with different functionalities and are installed in the Switches/Router Chassis as per requirements of the network types.

Benefits of Supervisor Engines
By installing Latest Supervisor Engines in your existing investments (Switches and Routers) you can scale system performance and integrate next-generation services into your Networks.
Within a single multilayer switch chassis, two supervisor modules with integrated route processors can be used to provide hardware redundancy. If an entire supervisor module fails, the other module can pick up the pieces and continue operating the switch.
The supervisor engine contains the following integrated daughter cards that perform forwarding and routing and provide the protocols supported …

GNS3 Docker Error while creating node: Docker has returned an error: Cannot connect to host docker:80

Error while creating node: Docker has returned an error: Cannot connect to host docker:80 ssl:False [No such file or directory]

After adding docker template for Alpine Linux in gns3, you get above mentioned message when you want to use alpine linux in GNS3.

To get rid of this message you have to install Docker by following below link
curl -fsSL https://get.docker.com/ | sh

If you do not have curl installed then instal curl first with below command.apt-get install curl
After installing Docker you need to add your user name in the docker group with the following command. $ sudo usermod -aG docker your_username

Verify if the docker service is started with following command$ service docker status
If docker is not started then start with following command $ sudo service docker start
Logout from GNS3 Virtual Machines and log back. Start gns3 and use alpine linux.

a file I/O error has occurred while accessing vmware converter

While converting physical Windows 7 machine to Virtual machine of infrastructure type, I got this error. The error seems it is unable to read/write source or destination datastore.

I have installed VMware-converter-en-6.2.0-8466193 on Windows 7 physical machine with option locally selected. (not at server/client option)

All of my ESXi servers are connected to the vCenter Server, so I had to use vCenter Server's IP address to send this physical machine to the virtual world.

The issue i found was with the dns resolution to the vCenter Server's hostname. Since I am not using the same dns server on the Windows 7 client machine. So I updated the host entries manually for the vCenter Server's hosname to it IP address.

After adding dns eteries to the hostfile of windows 7, I am not getting this "a file I/O error has occurred while accessing vmware converter" and the migration has started.