teamviewer account assignment failed due to an unknown error

• Home New Posts Forum List Trending New Threads New Media Spy
• WikiPost Latest summaries Watched WikiPosts
• Support FAQ and Rules Contact Us

TeamViewer Account Assignment Problem

• Thread starter JoelBC
• Start date Jan 18, 2017
• Sort by reaction score

macrumors 6502a

• Jan 18, 2017

I am running TeamViewer 12.0.72647 for macOS on macOS 10.12.2. I was successfully running TeamViewer without any problems until a few days ago when all of a sudden i) I could not initiate a connection from my one macOS to any of my Windows computers ii) I could not initiate a connection any of my Windows computers to my one macOS computer and iii) I could initiate a connection between my Window computers. The next step was to take a look at my macOS computer setup and I noticed the following: 1. The macOS computer DOES appear in the list of "My Computers". 2. The macOS computer HOWEVER IS NOT assigned to my account (noting that I do not know how this can possibly happen). I tried to BOTH assign the macOS computer to my account as well as assign the macOS computer to grant easy access but in both instances my attempt failed. 3. Worth also noting that I de-installed and reinstalled the TeamViewer but that did not solve the problem! Would really appreciate some help with this because my macOS is essentially useless at this point. TIA, Joel  

macrumors newbie

• Jan 21, 2017

JoelBC said: I am running TeamViewer 12.0.72647 for macOS on macOS 10.12.2. I was successfully running TeamViewer without any problems until a few days ago when all of a sudden i) I could not initiate a connection from my one macOS to any of my Windows computers ii) I could not initiate a connection any of my Windows computers to my one macOS computer and iii) I could initiate a connection between my Window computers. The next step was to take a look at my macOS computer setup and I noticed the following: 1. The macOS computer DOES appear in the list of "My Computers". 2. The macOS computer HOWEVER IS NOT assigned to my account (noting that I do not know how this can possibly happen). I tried to BOTH assign the macOS computer to my account as well as assign the macOS computer to grant easy access but in both instances my attempt failed. 3. Worth also noting that I de-installed and reinstalled the TeamViewer but that did not solve the problem! Would really appreciate some help with this because my macOS is essentially useless at this point. TIA, Joel Click to expand...

• Jan 22, 2017

mtrout said: [doublepost=1485033979][/doublepost]Looks like your either having an ipconflic on your mac Are you seeing your teamviewer ID on your mac side when you open it...or are you getting a local ip address instead. I would go into your network settings on your mac and Renew DHCP lease....see if that fixes it. I am assuming your using the free version of Teamviewer.....did you keep everything at default in teamviewer options? Just make sure in teamviewer on mac side in options/general/incoming lan...your incoming lan connection is set to accept.....It should be by defaut.....but I have been using teamviewer since 2009 and I only had one single issue all these years...and it was exactly what you were describing. And for some reason my incoming lan settings on my mac were set to deactived. Click to expand...

• Mar 10, 2017

JoelBC said: Appreciate the post but unfortunately the situation you described is not the situation I find myself in in that: 1. Correct, I am using the free version. 2. I am seeing my TeamViewer ID and NOT an ip address. 3. I tried all three possible settings for Incoming Lan Connection (i.e. Deactivated, Accept and Accept Exclusively) and none of them changed the situation or solved the problem (note: Accept Exclusively did show an IP Address rather than a TeamViewer ID). 4. The problem exists in three or four different locations / networks so it is not an IP address issues as I confirmed that the IP addresses (at least for the MBA) are changing when the location changes. Thanks for the suggestion they are much appreciated! Any other ideas? Click to expand...

macrumors 65816

• Mar 11, 2017

If you're in the UK it may have something to do with this http://www.ispreview.co.uk/index.ph...cks-teamviewer-vpn-service-scammer-fears.html  

TeamViewer Forum

Welcome to the Teamviewer forums, a group of Teamviewer users here to help each other.              We hope that you can contribute and help support this great tool !                        Start with a post in our forums and ask or answer a question.                                       Issues registering? Contact us: teamviewerforum(at)(g)mail(dot)com (NO technical support questions)

• TeamViewer Forum »
• General Category »
• Teamviewer for Mac/iPad/iPhone »
• Account Assignment Failure...

Author Topic: Account Assignment Failure...  (Read 4184 times)

• SMF 2.0.18 | SMF © 2014 , Simple Machines SMFAds for Free Forums

TeamViewer Account Assignment Windows V. 2004

Has anyone had any issues with loosing account assignment after upgrading a PC to version 2004? I’ve only started rolling it at my office, not to clients yet. Every one of the machines lost it’s account access. Some have the host module installed, some have the full version installed. All are running Windows 10 Business Edition and all are connected to AzureAD.

At the time of this writing, I found nothing on Google, TeamViewer forums, or here.

Interesting, I had that issue previously but it was hit and miss. However I use Bomgar and that does get upgraded regardless of the OS.

Team viewer one of the most problematic option especially when things comes to licensing and their ridiculous Eula. Go and find something better.

@TeamViewer

Are you losing account assignment or are the installations having their “Your ID” number being changed? I have seen glitches with TeamViewer having the “Your ID” change seemingly at random. Their “support” response was “when big hardware or software changes happen the ID also changes since the identifier is different.”

I had a Windows Server 2012 R2 system drop off because of it changing the ID just because of Microsoft updates and a reboot. It was a Hyper-V server, and the two guest virtual machines also running TV were online. I was able to reach one of the guests via TV and use RDP to connect to the now-TV-offline Hyper-V server, then assign it to my account with its new ID number.

Another computer changed its ID when I replaced the video card.

I now happily use Splashtop at much less cost and none of these issues.

100% for sure the account assignments. And to the other guy, say what you want, TeamViewer and Logmein are the bread and butter of what remote assistance is suppose to be, you just gotta pay the premium.

Related Topics

Stack Exchange Network

Stack Exchange network consists of 183 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

TeamViewer says "Unable to connect: A connection could not be established. Reason unknown." only on one machine

My girlfriend just got a new Lenovo 710, and wanted me to help set things up. As I am away at the moment, I got her to download TeamViewer, intending to log in and help her. I regularly (successfully) remote control her old laptop whenever it's needed, so I was looking forward to doing the same with this one as well. However, once she got TeamViewer set up with unattended access, and we were able to see each other as online, I tried logging in using the "unattended access" password, but I got the error mentioned in the title. These are the following things I tried next, all of which still led to me getting that error:

• Have her restart TeamViewer.
• Restart my own TeamViewer.
• Have her restart her computer.
• Try remote controlling in with her 9 digit TeamViewer ID and the random password.
• Have her re-enter/update the unattended access data (name and password), and try logging in again.

When all that failed, I tried logging into her old laptop, and I got in like I always do. So it wasn't that her network had suddenly decided to block TeamViewer's ports.

I then had her try and log onto my computer from her new laptop instead, and that worked too. She was able to move my cursor and click on things. So, somehow, incoming TeamViewer connections were being blocked.

I had her check Windows Firewall to see if TeamViewer was an allowed app, and it was. So it wasn't that.

I had her check Windows Defender, and it was apparently already turned off. That reminded me that she got the laptop with Webroot installed by Best Buy's Geek Squad as part of this 2 year protection package she opted for. So I had her temporarily disable Webroot's shields to see if that was what was blocking TVr but no. Still couldn't log in. Kept getting "Unable to connect: A connection could not be established. Reason unknown."

I then had her try to log into her new laptop from her old laptop, which worked. So maybe only computers on her LAN are able to log in? Based on that assumption, I had her check TeamViewer's Network Settings to see if incoming LAN connections were set to be accepted exclusively, but, alas, no. It was deactivated. Another theory down the drain.

I'm at my wit's end with this now. Does anybody have any idea what might be happening?

• remote-desktop

Sometime in April 2016 this started happening. New TV IDs can not be accessed. All IDs generated before April are working fine. Teamviewer have no solution to this so far.

• 1 Welcome to Super User. This isn't an answer to the question, so it is likely to be deleted. If you have a new question, please ask it by clicking the Ask Question button. If you have sufficient reputation, you may upvote the question. Alternatively, "star" it as a favorite and you can track any new answers on your user profile page. –  fixer1234 Commented Oct 12, 2016 at 3:03

You must log in to answer this question.

Not the answer you're looking for browse other questions tagged networking windows-10 remote-desktop teamviewer ..

• Featured on Meta
• Announcing a change to the data-dump process
• We've made changes to our Terms of Service & Privacy Policy - July 2024

Hot Network Questions

• ORCA 6 slower than ORCA 5?
• Estimate the core pressure of a star
• The 'correct' way to draw a diagram
• Newtonian vs General Relativistic light deflection angle
• Can I travel to Malaysia from Singapore?
• Movie identification 90s-ish on the Syfy channel sea creature
• Blocking access to `*.php` in `.well-known`
• Why would radio-capable transhumans still vocalise to each-other?
• How to play mono (or very unbalanced stereo) through both ears?
• What are the specific terms for breaking up English words into roots/components
• Could mage hand be used for surgery on another creature?
• How much does having competing offers benefit a job search?
• Why don't neutrons and protons have variable spin?
• Why do repeating 8's show up more often in these decimals of square roots?
• Is it bad to have similar themes between my novels?
• Lexicographically earliest permutation of the initial segment of nonnegative integers subject to divisibility constraints
• Is it possible for a flying superhuman to avoid detection in todays society?
• Inserting a 0 in Specific Strings
• 50s-60s novel likely written by a British author — ancient starship discovery unveils humanity's extraterrestrial roots
• When I use SSH tunneling, can I assume that the server does not need to be trusted?
• Understanding parallelStream and collector order
• Can you be resurrected while your soul is under the effect of Magic Jar?
• When Beatrix stops placing dominoes on a 5x5 board, what is the largest possible number of squares that may still be uncovered?
• How can Blowfish be resistant against differential cryptanalysis if it doesn't have S-boxes tuned for that?

Knowledge Base

We recommend using a specific script to deploy TeamViewer successfully on your devices.

In this article, we will show you our recommended script and explain the meaning of each parameter.

This article applies to  Corporate  and   Tensor  license holders who want to deploy TeamViewer (version 15 or newer) on their Windows devices.

Recommended scripts

Important note : Please make sure to  replace [your_xxx] with your own values.

This script processes the deployment in two steps:

• Installation of the package
• Account assignment

Script for the TeamViewer Host:

Script for the full client (64-bit):, script for the full client (32-bit):, main parameters.

We will explain here the parameters we used in our recommended scripts:

msiexec.exe /i

Installs the package.

Allows the silent installation.

“PATH_TO_MSI_FILE\TeamViewer_Host.msi”

Defines the installation path.

📌 Note:  It can also be on a network path.

CUSTOMCONFIGID=xxxxxx

Applies your module's customization.

📌 Note:  This only applies to the TeamViewer Host.

SETTINGSFILE=”YOURPATH\yourfilename.tvopt”

Imports TeamViewer options.

For more information, please read the following article:  Export settings for deployment

📌 Note:  The value must be a valid absolute local path or a path to a network share. 

⚠Don't use this parameter in combination with IMPORTREGFILE.

ENABLEOUTLOOKPLUGIN=true or false

Controls the de-/activation of the Outlook plugin

true:  The TeamViewer Outlook plugin is activated after installation (default)

false:  The TeamViewer Outlook plugin is deactivated after the installation

INSTALLSECURITYKEYREDIRECTION= 0 or 1

Installs a virtual device driver required for the security key redirection feature that allows the use of smart cards and fido-based devices through a TeamViewer session

0:  Does not install the driver (Default)

1:  Installs the driver

Optional command line options

There are additional options you can add to your command line:

For Windows:

Alias for the new device in the Device list. No alias will be applied if the device is already in the contact list. The property can take the following values:

• --alias (without value)alias of the computer will be the TeamViewer ID
• --alias helloalias of the computer will be "hello"
• Alias parameter not specifiedalias of this computer will be %computername%
• --alias %systemvariable%alias will be the used system variable e.g. %username%

💡  Hint : If you want to use spaces, you have to put everything in "..." like in the following example:

Desktop Shortcut

Will prevent the desktop shortcuts to be installed after a TeamViewer update.

📌Note : If you deployed the TeamViewer Host in the past using the MSI file with the option DESKTOPSHORTCUTS=0, please first uninstall it using:

The assignment is retried in case of temporary errors. Note that there is a waiting time of 1 second between each try.

Set the overall timeout in seconds used for  all  assignment tries.

Error codes

Access work laptop and gaming computer from PC/phone from anywhere for free

All-in-one secure remote work and support for teams, organizations, and enterprises

Access remote desktop at once

Access your computer from anywhere

Offer customer IT support remotely

Work remotely like in your office

• Download Login Account

Free, Secure, and Fast Remote Desktop Software

Available on Windows, iOS, and Android

• AnyViewer >
• How-to Articles >

5 Tested Ways to Fix TeamViewer Error Code WaitforConnectFailed

By Ellie / Updated on March 28, 2024

Solution 1. Disable IPV6 on both computers

Solution 2. check teamviewer version and update, solution 3. allow full access control to teamviewer, solution 4. flush the dns configuration, solution 5. restart the network, the bottom line, why does teamviewer say no connection to partner.

TeamViewer is a widely used tool for remote assistance, allowing users to connect to and control computers over the internet . However, sometimes it can run into problems. If you've ever been frustrated by seeing the TeamViewer "WaitForConnectFailed" error message when trying to use it, know that you're not alone.

Typically, this error pops up when users attempt to connect from a remote client to the server or computer. They'll see an error window in TeamViewer that says:

“No connection to partner!

Partner did not connect to router.

Error Code: WaitforConnectFailed”

Why is TeamViewer not connecting to partner?

“Error Code: WaitForConnectFailed” on TeamViewer typically occurs when there is a failure to establish a connection between the local and remote devices. This error can stem from various factors, including network issues, software conflicts, or configuration errors. Its occurrence often results in frustration for users attempting to initiate remote sessions or access their devices.

How to fix TeamViewer “Error Code: WaitforConnectFailed”

The reason behind the TeamViewer "Error Code: WaitforConnectFailed" may vary depending on the situation, but you can resolve it by trying one of the following solutions. Simply go through the list step by step.

To tackle the TeamViewer "No connection to partner" error, some users have found success by disabling IPv6. You can give it a shot by following these steps, ensuring you repeat the process on the client’s computer.

Step 1. Press the Windows key + S and type " control ".

Step 2. To open the Control Panel , simply click on it.

Step 3. In Control Panel, navigate to Network and Internet > Network and Sharing Center .

Step 4. From the left pane, click on Change adapter settings .

Step 5. To access the options for your currently active network adapter, right-click on it.

Step 6. Select Properties .

Step 7. Inside the Properties window, deselect the Internet Protocol Version 6 (TCP/IPv6) option .

Step 8. Click OK to apply the changes.

If you or your partner are using an outdated version of TeamViewer, you may encounter the "Error Code: WaitforConnectFailed". To resolve this, ensure that both computers have the latest version installed.

Step 1. Open TeamViewer on your computer.

Step 2. Click on Menu and select " Check for new version ".

Step 3. Click " Update " if a new version is found.

Moreover, to ensure that the TeamViewer client has the necessary privilege to establish connections between the involved computers, you must enable Full Access Control on both devices. Here's how to do it:

Step 1. Launch TeamViewer on your computer.

Step 2. Click on " Extras " and select " Options ".

Step 3. In the TeamViewer options window, go to the " Advanced " tab.

Step 4. Click on the " Show advanced options " button.

Step 5. Under the " Advanced settings for connections to this computer " section, click the drop-down menu and select " Full Access ".

Step 6. Click " OK " to save the changes.

Step 7. Restart TeamViewer and check for any improvements.

Corrupted DNS entries might contribute to the "Partner did not connect to router" error in TeamViewer. To address this, clearing the DNS cache could prove helpful in resolving the connection issue. Follow these steps:

Step 1. Press the Windows key + S and type " cmd ".

Step 2. To run Command Prompt as an administrator, right-click on it and choose " Run as Administrator ".

Step 3. In Command Prompt, input the following commands one by one, and hit Enter after each:

• ipconfig/release
• ipconfig/renew
• ipconfig/flushdns

Step 4. After completing the commands, close the Command Prompt and verify if the TeamViewer "Partner did not connect to router. Error Code: WaitForConnectFailed" error has been resolved.

The error message indicates that your partner did not connect to the router. This suggests a potential issue with the router and the network connection of both computers. Before attempting any technical solutions, try restarting the router to re-establish the network connection for both your computer and your partner's.

Step 1. Ensure the modem is turned on.

Step 2. Disconnect the cable from the back of your modem.

Step 3. Verify that all lights on the modem are off and let the modem remain idle for a minute.

Step 4. Reconnect the modem cable and power on the device.

Step 5. Wait until the lights on the modem stop blinking and turn green.

Step 6. Attempt to connect to TeamViewer and check for any improvements.

Bonus tip: TeamViewer alternative for remote desktop access

While TeamViewer is widely used for remote access, it's worth noting that there are alternative options available. If you're consistently facing connection errors or are interested in exploring other remote access tools , you might want to consider AnyViewer.

AnyViewer serves as an excellent substitute for TeamViewer when it comes to remote access and support solutions. Boasting robust features and a user-friendly interface, AnyViewer presents an appealing choice for both businesses and individuals seeking dependable remote connectivity. What sets AnyViewer apart is its provision of free services for any purpose. Whether for personal or commercial use, you can utilize AnyViewer's features without charge.

Here are the steps to use AnyViewer for unattended remote access :

Step 1. Download and install AnyViewer on both computers respectively.

Step 2. On the local computer, navigate to the " Log in " tab, and click on " Sign up ".

Step 3. Log in to the same account on other unattended remote computers beforehand.

Step 4. On the local computer, go to the " Device " tab. Select the PC you wish to control and click " One-click control " to establish unattended access with a single click.

In conclusion, encountering the TeamViewer "Error Code: WaitForConnectFailed" message can be frustrating, but there are tested solutions available to resolve this issue. Whether it's disabling IPv6, updating TeamViewer, enabling full access control, flushing the DNS configuration, or restarting the network, you have options to address the problem effectively.

Additionally, considering alternatives like AnyViewer for remote access provides flexibility and reliability, especially with its free services for personal and commercial use. By following the outlined steps and exploring suitable alternatives, you can overcome connectivity challenges and ensure seamless remote access experiences.

Free Remote Desktop Software

• Quick Remote Connection
• Control Multiple Computers
• High Quality Image
• Support Latest Windows OS

Still Need Help?

Have your problem been solved? If not, please input query in the search box below.

Get the Reddit app

A vast community of Microsoft Office365 users that are working together to support the product and others.

An error occurred while sending mail

I am getting this error when I try to send a pdf attachment directly to outlook. I've been trying different possible fix with no luck. The default email app is outlook. Ive reinstall adobe, and repair office, and the issue persist. All happened after an office update.

"There is no email program associated to perform this requested action. Please install a email program or, if one is already installed, create an association in the Default program in Control Panel "

By continuing, you agree to our User Agreement and acknowledge that you understand the Privacy Policy .

Enter the 6-digit code from your authenticator app

You’ve set up two-factor authentication for this account.

Enter a 6-digit backup code

Create your username and password.

Reddit is anonymous, so your username is what you’ll go by here. Choose wisely—because once you get a name, you can’t change it.

Reset your password

Enter your email address or username and we’ll send you a link to reset your password

Check your inbox

An email with a link to reset your password was sent to the email address associated with your account

Choose a Reddit account to continue