Show Posts
I've noticed what appears to be a conflict between Awesome Miner and Teamviewer on Windows 10.
Whenever I remote in with Team Viewer, Awesome Miner stops mining and restarts itself.
Whenever I manually restart a mining process within Awesome Miner, Teamviewer times out for 30 seconds, before reconnecting.
Sometimes when my remote rig is mining, Teamviewer won't even connect at all.
How can I change the ports either Awesome Miner or Teamviewer use, to prevent this from happening?
Alternatively, does anyone have a guide on how to set up a remote rig within Awesome Miner? I cannot seem to get it working on my local network.
Others have noticed the same: https://www.reddit.com/r/gpumining/comments/7vchaj/awesome_miner_teamviewer_conflict/
Whenever I remote in with Team Viewer, Awesome Miner stops mining and restarts itself.
Whenever I manually restart a mining process within Awesome Miner, Teamviewer times out for 30 seconds, before reconnecting.
Sometimes when my remote rig is mining, Teamviewer won't even connect at all.
How can I change the ports either Awesome Miner or Teamviewer use, to prevent this from happening?
Alternatively, does anyone have a guide on how to set up a remote rig within Awesome Miner? I cannot seem to get it working on my local network.
Others have noticed the same: https://www.reddit.com/r/gpumining/comments/7vchaj/awesome_miner_teamviewer_conflict/
its not a TV and AM conflict, it's that TV is using the GPU. I noticed a 75-100 sol/s decrease on the card that is running the monitor. If I used the MB video that doesn't have a GPU, TV runs just fine and there is no sol/s decrease. Actually in my case, I can work with TV and AM, but it will depend on your GPU.
But I would fully expect that crashes can occur depending on lots of variables, if the main windows display that TV is replicating is also running on the GPU.
I don't use my GPUs for monitor usage - I use the onboard motherboard HDMI port.
