RC2 with proxy issue

[Projectshifter]

Sadly the only way I can get around my university's firewall is through a private proxy that I setup. I'm running RC2 through sockscap but it gives errors when I try and launch it. First one is:
"Couldn't open shared file mapping Sc32Share.<mem address stuff>: The system cannot find the file specified. (errnum=2)"
then it just gives a "Launcher: empty command line" error. I have tried it on three different computers with the same results. Running the old RC works fine. Also since my Graal v4 updated again it says that my firewall is blocking it and to check my network connection (which is fine and valid). Any ideas?

[Admins]

RC2 is using the same ports like RC1 though, so I guess it is my some problem with the firewall rules or the sockscap configuration

[Projectshifter]

Originally Posted by Stefan

RC2 is using the same ports like RC1 though, so I guess it is my some problem with the firewall rules or the sockscap configuration

Like I said, it's got the same exact configuration on all three computers as RC1, except it is RemoteControl2.exe. It doesn't matter about the firewall because it's running through sockscap. I don't see why RC1 would work and RC2 wouldn't when they're being run in the exact same manner, on the exact same computer.

[ZeroTrack]

Could be that someone else in your university was connecting out a lot with remotecontrol2.exe and they blocked the application , or they could've blocked any application sending and receiving packets with the name remotecontrol or similar in it *remote* or so, i know i've done that on some personal company firewalls because most backdoors have the name remote in them =p

this is not likely , but possible

Originally Posted by Projectshifter

Like I said, it's got the same exact configuration on all three computers as RC1, except it is RemoteControl2.exe. It doesn't matter about the firewall because it's running through sockscap. I don't see why RC1 would work and RC2 wouldn't when they're being run in the exact same manner, on the exact same computer.

[ZeLpH_MyStiK]

Originally Posted by ZeroTrack

Could be that someone else in your university was connecting out a lot with remotecontrol2.exe and they blocked the application , or they could've blocked any application sending and receiving packets with the name remotecontrol or similar in it *remote* or so, i know i've done that on some personal company firewalls because most backdoors have the name remote in them =p

this is not likely , but possible

Very farfetched.