Firefox is unable to connect to the server. Sign In Failed - Failed to contact google servers: what to do

5 November 2011, 14:47 admin 66 343

An error with the system message "could not contact google servers, please try again later" often occurs when you try to either add a new Google account, or simply go to Google Play or Play Market.

The solution to most of these errors (for example, from the same “test”) is approximately the same, while the fact that the error lies in the device itself and is not related to Google servers remains unchanged.

What to do if unable to contact google server?

So, a little later we will look at the main ways that almost always help fix this error.

However, first it is necessary to mention the obvious, but at the same time important things:

1. 1. Yes, it’s funny and unlikely, but still there are cases when a user tries to add an account that is not related to Google services: for example, “mail” or “yandex”.
2. 2. Check if the Internet is working at all: open a browser and go to any site.
3. 3. Check if the date and time are set correctly.

If there are no such obvious problems, but the device persistently writes “could not contact google servers, try again later”, then in most cases an application called “Freedom” becomes the culprit for errors with Google services.

There are two possible options here:

1. 1. If the application was installed and subsequently uninstalled, try installing it again and check the operation of Google Play (if this helped to fix the error, it means that the application was previously removed incorrectly).
2. 2. If the application is already installed - remove it. However, a simple uninstallation will not help here: you need to completely clear your device of this “useful” application. For this:

• A. Run the application and click "Stop" in the pop-up menu.
• B. Close it using either "Device Manager" or "Task Manager".
• B. To remove, use one of the "killer utilities" (" Clean Master" or "History Eraser"): run the program and delete everything related to "Freedom";
• D. Reboot the device and check its operation again.

How else can I fix the "could not contact google servers" error?

1. 1. Using the same application, clear the cache, but not only of the Google Play service, but in a complex way - of the entire device. Perhaps this will help fix not only this error, but also prevent new ones from appearing.

1. 2. As with the “RH-01” error, the reason that a smartphone or tablet with Android OS could not contact Google servers often lies in the absence or incorrect operation of the “Google Services Framework”: either enable this service or install it again.

Also, check the "GoogleContactsSyncAdapter.apk" file: try updating it or deleting it and then reinstalling it (but, accordingly, using third-party devices).

1. 3. Your account may have "Two-Step Verification" installed. To check, you need to log in to “gmail.com” on the official website of “google”, go to the “Authorization of applications and sites” section and check what parameters are set.

1. 4. Perhaps a lock is set in the “host” file (located in the /system/etc/ directory). Using an application (for example, "Root Explorer") and using "root" rights, check what is indicated in the file after the line "127.0.0.1 localhost": ideally, if you did not install anything yourself, there should be nothing after this line .

1. 5. Remove "Permanent active mobile transmission" in the wireless network settings: this is especially true for older versions of the operating system.

1. 6. Before entering personal data in the account in the upper right corner, you can call up the context menu: here you will need to select "Login through the browser" or "Login in the browser" - respectively, you will be redirected to the browser to enter data.
2. 7. Reset the settings to factory settings and use the "Initial Setup Wizard".
3. 8. As a last method, you can use third party applications to create or add an account manually: for example, "Android /Add Account".

In this way, possible solutions there are a lot of "could not contact google servers" errors. In any case, we strongly recommend that you delete the Freedom application and do not use it in the future: sooner or later this application will “bring” various kinds of errors to your device. In addition, you should at least occasionally, but clear the cache of the device, since cached errors will make themselves felt.

This documentation has been archived and is no longer maintained.

This is a general error that occurs if the report server cannot open a connection to an external data source that contains report data. This error appears along with a second error message indicating the reason. The following additional errors may appear along with rsErrorOpeningConnection.

Login failed for user 'Username'

The user does not have permission to access the data source. If using a SQL Server database, make sure the user has a valid database login. For more information about creating a database user or SQL Server login, see and .

Unsuccessful login attempt for user 'NT AUTHORITY\ANONYMOUS LOGON'

This error appears when credentials go through multiple computer connections. If Windows authentication is used and Kerberos version 5 is not allowed, then this error occurs when the credentials pass through more than one computer connection. To avoid this error, consider using stored or prompted credentials. See the section for more information about resolving this issue.

An error occurred while connecting to the server. This error when connecting to SQL Server 2005 can be caused by default settings in SQL Server that do not allow remote connections. (provider: named pipes provider, error: 40 - Unable to open connection to SQL Server)

This error is returned by the instance of the Database Engine that hosts the report server database. In most cases, it occurs because the SQL Server service has stopped. Also, if you are using SQL Server Express with Advanced Services or a named instance, this error occurs if the report server URL or report server database connection string is incorrect. To solve these problems, you need to do the following.

Verify that the SQL Server (MSSQLSERVER) service is running. On the computer of the instance of the Database Engine, click the Start button, select Administration, Services, and navigate to the SQL Server (MSSQLSERVER ) service. If this service is not running, right-click it, select Properties, set Startup type to Automatic, and then click Apply, Start, and OK.

Check that the report server URL and report server database connection string are correct. If Reporting Services or the Database Engine was installed as a named instance, the default connection string that is generated during installation will include the name of the instance. For example, if the default edition instance of SQL Server Express with Advanced Services was installed on a server named DEVSRV01, the Report Manager URL would be DEVSRV01\Reports$SQLEXPRESS. The name of the report server database in the connection string will be something like DEVSRV01\SQLEXPRESS. For more information about URLs and data source connection strings for SQL Server Express, see . To verify the connection string to the report server database, run the Reporting Services Configuration utility and view the Database Setup page.

Unable to establish a connection. Make sure the server is running.

This error is returned by the ADOMD.NET provider. There are several possible causes for this error. If the server is listed as "localhost", try specifying the server name instead. This error can also occur if it is not possible to allocate memory for a new connection. For more information, see article 912017 in the Microsoft Knowledge Base.

If this error also contains "Unknown Host", it indicates that the Analysis Services server is unavailable or that the connection was refused. If the Analysis Services server is installed as a named instance on remote computer, you may need to start the SQL Server Browser service to get the port name used by the instance.

(Reporting Services SOAP Proxy Source)

If you receive this error message while creating a report model, and the additional information section contains the message "SQL Server does not exist or access is denied", it may be due to the following reasons.

The connection string for the data source includes the word localhost.

TCP/IP is disabled for the SQL Server service.

To resolve this error, you can change the connection string to include the server name, or you can enable TCP/IP for the service. Follow the steps below to enable the TCP/IP protocol.

Launch SQL Server Configuration Manager.

Expand Node SQL Server 2005 Network Configuration.

Select Protocols for MSSQLSERVER.

Right-click TCP/IP and select Enable .

Select SQL Server Services.

Right-click SQL Server (MSSQLSERVER) and select Restart.

Reporting Services Service Pack 1 (SP1) and earlier versions do not start on Windows Vista. When you try to start Report Server SP1 on Windows Vista, you receive the following errors.

These errors will not occur after you install SP2 or upgrade to SQL Server 2008 and configure the report server.

By default, Management Studio uses the Reporting Services Windows Management Instrumentation (WMI) to establish a connection to the report server. If the WMI provider is not set correctly, the following error will occur when trying to connect to the report server.

"Unable to connect to<имя_сервера>. The Reporting Services WMI provider is not installed or configured (Microsoft.SqlServer.Management.UI.RSClient)."

To fix this error, you need to reinstall software. In other cases, as a workaround, you can connect to the report server through a SOAP endpoint.

In the dialog box Server connection in Management Studio, in the Server name field, enter the URL of the report server. The default is http://<имя_сервера >/reportserver. Or, if using SQL Server 2008 Express with Advanced Services, this is http://<имя_сервера >/reportserver$sqlexpress.

To resolve this error (in order to later establish a connection through the WMI provider), run Setup to fix Reporting Services, or reinstall Reporting Services.

An error can occur if a domain account is used to connect the report server to the report server database, and the domain account password has been changed.

The full text of the error is: "The report server could not establish a connection to the report server database. Login failed ( rsReportServerDatabaseLogonFailed). Login failed: Unknown username or incorrect password."

If the password is changed, the connection must be updated. See the section for more information.

This error can also occur if the instance of the Database Engine that stores the report server database is not configured for remote connections. Remote connection is enabled by default in some editions of SQL Server. To check if it is enabled on an instance of the SQL Server Database Engine, run the SQL Server Services Configuration Manager. Both TCP/IP and named pipes must be enabled. The report server uses both of these protocols. For instructions on enabling remote connections, see the "Configuring Remote Connections to the Report Server Database" section of the topic.

If this error additionally contains the following text, the account used to run the instance of the Database Engine has expired password: “An error occurred while establishing a connection to the server. When connecting to SQL Server, this error can be caused by the fact that in the default configuration, SQL Server does not allow remote connections." (provider: SQL Server network interfaces, error: 26 - An error occurred while looking up the specified server/instance)". To resolve this error, reset the password.

This error message indicates a data source connection error. In this case, you need to check the connection string and make sure you have permission to access the data source. If you use Windows Authentication to access a data source, you must have permission to access the computer where the data source is located.

If you configure Reporting Services to integrate with a SharePoint product or technology on Windows Vista or Windows Server 2008, when you try to grant access on a page Granting access to the database You may receive the following error message in the SharePoint admin center: "Unable to connect to the computer."

This happens because the User Account Control (UAC) feature in Windows Vista and Windows Server 2008 requires the administrator to explicitly allow elevation and use the administrator token when performing tasks that require administrator permission. However, in this case, Windows SharePoint Services Administration cannot elevate the Reporting Services accounts to give them access to SharePoint configuration and content.

There are two possible solutions to this problem. In the first case, you can temporarily disable User Account Control and use the SharePoint Central Administration to grant access.

In the second case, you can manually grant database access to Reporting Services accounts. Complete the following procedures to grant access by adding the Reporting Services accounts to the correct group and database roles.

"Unable to install network connection in WOT. The server may not be available or you may need to check your network connection settings." Are you familiar with this message? Then you are right here. This message can appear for a hundred reasons. In this article, I will try to reveal the main ones.

At the very beginning, I would like you to clearly understand the decoding of this message. Although there is nothing special to understand here. Tanks swear that you either do not have the Internet, or the client for some reason cannot find a connection to the game server. That is, you launched the client, which, in turn, tries to go online and find its server at a pre-known IP address, but the server does not respond to it and an error message is displayed accordingly. Next, for clarity, let's analyze exactly how the procedure for connecting to the game server goes:

Now, I hope, everyone is clear on the scheme by which it is necessary to find a problem that prevents the client from connecting to the server. Let's go further...

How are we going to fight?
BUT, the very first step will be to enter the wargaming portal dedicated to tanks. Welcome! What if some work is going on on the servers now. The developers inform about this in advance and even describe the time during which the servers will not be available and they place all this on their website, so do not be shy and go.

Next, we go along the "scheme". After the game client, the first obstacle is the firewall. Disable it (instruction) and try to enter the game. Happened? Congratulations! Play with the firewall turned off or read the article below.

So we've identified the culprit. Now you need to open ports and create rules for this "mind" (windows firewall). But first, let's do the same only in automatic mode.

Let's go download .bat file from wargaming server:

It's not a virus, don't worry. You can open it with Notepad++ and see. Here is its content:

@ECHO OFF set Arg1="%~d0%~p0WorldOfTanks.exe" set Arg2="%~d0%~p0WoTLauncher.exe" IF NOT EXIST %Arg2% GOTO errorwotl netsh firewall add allowedprogram %Arg2% WoTLauncher enable all netsh firewall add portopening udp 20010-20020,32800-32900,12000-29999,5060,5062,3478,3479,3432,30443,53,6881-7881,1900 7881 wot-tcp enable IF NOT EXIST %Arg1% GOTO errorwot netsh firewall add allowedprogram %Arg1% WorldOfTanks enable all chcp 1251 >NUL set text_y="WorldOfTanks.exe" and "WoTLauncher.exe" successfully added to firewall exclusion list. chcp 866 >NUL echo %text_y% GOTO exit:errorwotl chcp 1251 >NUL set text=Could not find file "WoTLauncher". Make sure the file is located in the folder with the game client. chcp 866 >NUL echo %text% GOTO exit:errorwot chcp 1251 >NUL set text_l="WoTLauncher" successfully added to firewall exception list. Could not find file 'WorldOfTanks.exe'. Make sure the game client is updated to the latest version. chcp 866 >NUL echo %text_l% :exit PAUSE

Now start the game and try to connect to any server. Well, how? Works? HURRAH! Let's go play and don't bother with anything else! If it does not work, then we go to do everything manually.

In order for the message “Unable to establish a network connection in WoT” to no longer occur, it is necessary that some ports are opened for the launcher and the game client in the firewall, here they are:

For WorldOfTanks.exe:
- UDP ranges from 32800 to 32900, from 20010 to 20020 and UDP port 53;
- TCP ports 80, 443.

For voice chat to work, it is also necessary for WorldOfTanks.exe to open the UDP range from 12000 to 29999 and ports 5060, 5062, 3478, 3479, 3432, 30443.
For text chat to work, WorldOfTanks.exe needs to open TCP ports 5222 and 5223.

In addition, you can allow WorldOfTanks.exe UDP protocol and TCP protocol on any ports in both directions, thus allowing the firewall to pass any packets to any addresses for the game client.

For WOTLauncher.exe need to open:
-UDP ports 53, 6881, 1900.
-TCP ports 80, 443, 6881.

Well, how did it work? If yes, then happy for you. Well, if not, then do not despair and read on ...

The next obstacle to connecting to the server is the antivirus. If you do not have it, then skip this paragraph.
Try adding the game folder to the trusted zone of your antivirus. BUT before that, check your computer for viruses.
Everyone has different antiviruses, so the development team wrote a whole book with instructions for you and me, the link to which I give here. (Many thanks to them for the titanic work)