RDP does not simulate an other machine with an other ip adress, it just allows you to have an other session on the same. Hence regarding CCP you have the same ip adress for each desktop, then for each Eve process. => issue with alpha accounts.
I also tried with multiple IP addresses through a vpn and I could not get an alpha and omega account to reliably connect. I believe I did have both on at same time once but canât remember what I did to make that happen.
I think it might have been a Virtual machine and your regular windows account.
But Bitenbois is correct RDP doesnât work with alpha and omega accounts.
Maniac
Hi,
All this does is allow you to run several separate EVE instances that each has their own mouse/keyboard input for automation.
This does indeed not hide or mask your IP, if you are worried about your accounts donât bot 
pointed to this topic by one of members hereâŚ
reading thru this is semi interesting⌠some of you guys are trying to wave red flad in front of ccp and wondering why uâve been caught
freaking never combine alphas and omegas! ccp does have checks for alpha accounts being connected at same time from same computer since very very begining. why someone even trying this?
use omegas only and there is literally NOTHING against having multiple omega clients on same ip/mac address!
sanderling is NOT broadcasting same commands to all clients at same time and even if you are stupid enough to have botted accouns botting in same system eventho there is almost non probability it will give same command at very same millisecond in case of neuts jump in.
and indeed if you are âplayingâ 5accounts 20hours a day everyday⌠just dont
rdpwrapper + registry hack works flawlessly even on creators update btw.
I dont manage to run Remote. RDP is installed and Config running fine.
But with Remote he dont let me connect
if Iâm not mistake, you have to enter in the second account ( normal bot) and " let others to connect" -or something similar( add first account to list )
and there it was somthing with the password also
1 Like
I do not have experience with this issue.
Just as a reminder, for anybody who runs into issues I recommend to check out the RDP Wrapper issues list at Issues ¡ stascorp/rdpwrap ¡ GitHub
There are many people over there sharing what they did to make RDP Wrapper work in their case, for example this explanation just two days ago:
Looking for 10.0.17763.168 support ¡ Issue #606 ¡ stascorp/rdpwrap ¡ GitHub
But of course the starting point should be the project readme at GitHub - stascorp/rdpwrap: RDP Wrapper Library
Maybe we will get a more stable option with Windows Sandbox, that does not need to be adapted so often. Not sure though when it is ready for production.
1 Like
I am no expert but i assume that the user you want to connect with can not âgive permissionâ because so far he is not logged in
try without users permission. if you have security concerns you can try âview onlyâ first.
Running two or three mining bots on the same PC is no problem.
The bots can use input focus scheduling to avoid interfering with each otherâs inputs. How many you can run in parallel this way depends on the saturation per bot, meaning how many percent of the time it needs to send input. (You can check this for any of your app sessions in devtools)
Starting with the version from December 2020, the engine does this automatically. You only need to switch your app to use the new interface to the host.
You can read more about input focus scheduling in the guide at https://to.botengine.org/guide/input-focus-scheduling-for-multiple-bot-instances