Skip to main content
Automatically detect settings

Downloading Proxy Script in Google Chrome

Downloading Proxy Script in Google Chrome

At time you may see “Downloading Proxy Script” in the lower left corner of chrome window in google chrome and the websites taking forever to load. This problem is faced when you are using a proxy server to access the internet. Companies use proxy server to control the internet access for their employees. While users put the proxy in their Internet Explorer Proxy options. Google chrome uses these proxy settings from internet explorer to reach the internet.

Solution:

The solution to “Downloading Proxy Script” problem is pretty simple. You just need to uncheck the “Automatically Detect Settings” in the proxy settings.

First of all, In Google Chrome go to settings and look for “Proxy settings”. Alternatively you can open the Internet Options in Internet Explorer. Because both open the same window.

Automatically detect settings

On the connections Tab, click “Land Settings” and UNCHECK “Automatically Detect Settings”, click OK.

Finally, close the chrome and open it again, now Google chrome will load the sites faster without showing the “Downloading Proxy Script”.

 

If you want to know more about Proxy settings in internet explorer you can read Technet article about “How to configure Internet explorer to use proxy server”

Get-ExchangeServer

Remove Exchange Server From Active Directory Domain

Remove Exchange Server From Active Directory Domain

At times you may have to remove exchange server from Active Directory domain because the Server is dead and there is no possibility to recover it. In such situations, we can use Adsiedit.msc to remove the dead server entries from active directory domain. The procedure is same for Exchange 2007, 2010 and 2013

I came across a situation where the exchange 2010 environment was running smoothly, except there was a dead Exchange 2007 Server that was still showing in the settings.

So to list all the Exchange servers we have in the environment, open the Exchange Powershell and run Get-ExchangeServer:

Get-ExchangeServer

As we can see, the dead server “Mail” is a standard edition server with version 8.3 (Exchange 2007 Sp3). While the other functioning servers are 14.3 (Exchange 2010 Sp3).

Before removing the dead Server, we need to remember the following:

  • Ideally we should remove the exchange server by uninstalling from Add/Remove Programs.
  • It should be our last method to remove the server, when we are 100% sure that the server is unrecoverable.
  • Send/Receive connectors or any other configuration may still have the server in the settings, you should remove them manually.
  • AdsiEdit is very sensitive thing, only make changes when you know what you are doing.
  • It is good practice to take System State backup before making changes in the Adsiedit.

If you confirm all the above points, you can proceed to the removal step, otherwise leave it and ask for help from some senior systems engineer.

Procedure:

To remove the dead server, open Adsiedit.msc and connect to Configuration:

ADSIEDIT Configuration

Then go to the following path:

Configuration, CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=<OrganizationName>, CN=Administrative Groups, CN=Exchange Administrative Group (FYDIBOH…, CN=Servers

Remove Exchange Server From Active Directory

Select the dead server from right pane, right click and delete.

ADSIEDIT Configuration exchange server delete

Finally, go again to Exchange Powershell and run the Get-ExchangeServer command to confirm the server is deleted from the list.

Get-ExchangeServer after

You may also like to check the Technet article “Remove the last legacy exchange Server”.

0x800706BA RPC server unavailable

0x800706BA RPC Server Unavailable

0x800706BA RPC Server Unavailable

0x800706BA RPC server unavailable is an error that you may face in multiple applications. When the “Remote Procedure Call” connectivity between two devices fails, this error may appear.

To confirm if we have the RPC between two devices, we can run the following command:

Get-WmiObject Win32_ComputerSystem –ComputerName DestinationServer

The successful RPC connectivity result look like this:

RPC Successful

If the RPC connectivity fails, the result will be as follows:

0x800706BA RPC server unavailable

Troubleshooting:

To troubleshoot the “0x800706BA RPC server unavailable” error, check the following:

  • First of all, make sure the remote/destination device is up and running.
  • Make sure the RPC service is running on remote/destination device.
  • Check if you have any firewall in between both devices and required ports are open.
  • Check If Windows Firewall is enable on either side, disable it and then try again.
  • Make sure the antivirus is not blocking any traffic.
  • Finally, Try to have connectivity by using the IP instead of the name to confirm it is not DNS issue.