Send Files without using File Transfer?

Wolffe

When I was using the free version of TeamViewer on Windows 10/11, sending files was a breeze -- right click on the file -> Send To -> TeamViewer -> Select the destination PC and the file was sent.

Now I'm using TeamViewer remote and it seems I can't send files via Send To anymore. First my computer didn't show up as an available computer. I had to manually add my computer a second time under "My Computers" for it to appear in this list.

Now when I try to send a file to myself, it seemingly tries to establish another connection and tells me I've exceeded my limit. I'm not sure why it doesn't realize I already have a connection from this PC?

So is there any way, from Windows File Explorer, to select a file and send transfer it to me? It's a bit of a pain opening File Transfer and then having to navigate back to that file I want to send.

.Carol.fg.

Hi @Wolffe ,

Thanks for posting in our Community, it's a pleasure to have you here!

TeamViewer Remote has a new system of groups called Managed Devices. Our recommendation is to keep using Managed device groups for your remote sessions; however, to use this feature ("right click on the file -> Send To -> TeamViewer -> Select the destination PC and the file was sent") you will need to have your devices also registered in the old list of Computers & Contacts.

In other words, you will have a Managed Devices group (migrated devices)...

and a regular group (devices not migrated)...

If during the migration you excluded the "duplicated" devices from the Computer & Contact list, you can add them again using the Management Console:

Go to Groups and select a group (create a group folder if necessary) ➜ Right click the group or click the Icon of a person with + and follow the instructions on the screen to add your device.

After having your devices registered in both Device groups and Groups, please restart TeamViewer services and try transfer files again, you should be able to see the device.

Let us know how it goes, and if we can help you any further.

Best, Carol

Wolffe

Thank you Carol. This allows me to see the device in the send files dialog (which I was already able to do).

However, once I try to send files from the remote PC to my local PC, it looks like Send Files tries to establish another connection and fails because Remote Access only allows one connection.

If Send Files truly needs a separate connection, it should just allow it since my one connection is already to the same machine. I can understand not being allowed to connect to more than one device but "one connection" doesn't seem right if basic functionality within the software uses multiple.

.Carol.fg.

Hi @Wolffe ,

Thanks for the additional information!

I would like to understand your case a little bit better... So you want to remotely connect to a partner device, and then send the file from the remote side to your PC using "right click on the file -> Send To -> TeamViewer -> Select the destination PC and the file was sent"?

If yes, I would just advise using the session toolbar for transfer files.

The Remote Access license allows you to have 3 devices in your device list. Is the device you use to start the remote session also listed as 1 of the 3 devices that you can remote connect to?

I'm looking forward to your feedback!

Best, Carol

Wolffe

Hi Carol,

Yes, both my local and remote system and included in my 3 managed PCs.

I’m connected Local -> Remote.

When I try to send files (Send To -> TeamViewer) then TeamViewer seems to be trying to establish another connection Remote -> Local and rejects it because it thinks I’m starting a 2nd connection and I’m only allowed 1. This really doesn’t make sense.

The reason i want to use Send To is that I’ve already found the file in Windows Explorer. If I use the TeamViewer Transfer Files dialog then I have to navigate to the file yet again.

.Carol.fg.

Hi @Wolffe ,

Thanks for the detailed description of your use case.

At the moment, the file transfer feature Send To -> TeamViewer is primarily meant to be used outside of a remote session. In the use case you described, it would be advised to use the session toolbar, Ctrl+V/Ctrl+C, or drag and drop.

The Remote access license has 1 channel that can open up to 3 remote concurrent sessions - in other words, 1 device ID that can open/start up to 3 remote sessions, but to be able to start a remote session from more than 1 device simultaneously you would need a license that offers more channels. If you are interested in how it would be to upgrade your license, you can message our sales team here.

We also would advise you to post in our Ideas Hub. We can't guarantee that improvements to this feature will come, but this is the best way to communicate with our development teams that you wish the Send To -> TeamViewer feature could be used from the channel already opened.

I hope this information can help you in some way. 🍀

Please let me know if we can clarify any further questions.

Best, Carol

Wolffe

Thank you Carol for taking the time to address my problem. I appreciate it even if the solution wasn't what I hoped!

.Carol.fg.

It's my pleasure to help @Wolffe !

If I hear of any better feature that can address your needs, I will come back here and share it with you. 🍀

Thanks for your understanding, and please don't hesitate to post again whenever you want.

Have a great day!

Best, Carol