Arlecho's ScreenConnect 6 releases

[justsomeguy1234]

I don't use Verizon for anything. Here's what the firewall is logging....



https://drive.google.com/file/d/1Itzum0E...sp=sharing

[Arlecho]

Looks like the Windows installer calls it and the firewall has attaches it to both (as the patcher spawns the SC installer which uses the Windows installer).
The patcher doesn't do anything except call the SC installer which has been patched in step 1.

I'll have a look into the installer why it calls to an external server.

-Edit- Could you try patching the installer with the "Remove License check" ticked and see if it still performs the call?

[rinkanrohitena]

checked with Remove Licence check , it works fine no external ip call checked logs too . Have not tried ssl installation yet once i get it installed will update here soon.

[justsomeguy1234]

checked with Remove Licence check , it works fine no external ip call checked logs too . Have not tried ssl installation yet once i get it installed will update here soon.

hmmm.... strange I just tried it again with "Remove License Check" but I still get an attempted connection to 72.21.91.29 as soon as I do step 3.

[rinkanrohitena]

checked with Remove Licence check , it works fine no external ip call checked logs too . Have not tried ssl installation yet once i get it installed will update here soon.

hmmm.... strange I just tried it again with "Remove License Check" but I still get an attempted connection to 72.21.91.29 as soon as I do step 3.

as i think you have some issues with your server buddy . the ip you have given when i try to connect to it its giving a file to download . please check your server if its the problem regarding your server. i have used burp suite to check but still i got nothing .

[justsomeguy1234]

I apologize for the false alarm.
I'm not sure why it was happening but I no longer can reproduce the behavior. I went back in the firewall logs and searched for that IP and found entries where the firewall software itself was blocked trying to make connections to the same IP. Maybe something weird with the firewall, it's WFC (Windows Firewall Control). I did half a dozen different scans on the system and it comes back clean. I don't know but I may just blow away the windows install and start fresh just in case.

[rinkanrohitena]

when ever i am changing domains i am loosing guests from access . Any solution please !!! and also can any body help with relay . i am leaving relay as default perhaps this is the reason why i am getting these kind of errors

[dontbug]

checked with Remove Licence check , it works fine no external ip call checked logs too . Have not tried ssl installation yet once i get it installed will update here soon.

hmmm.... strange I just tried it again with "Remove License Check" but I still get an attempted connection to 72.21.91.29 as soon as I do step 3.

Perhaps I can shed some light on this.  My firewall also triggers on this, however it does also give more detail.  "Remote Name: ocsp.digicert.com" / "Remote Address: 72.21.91.29".  The reason this triggers is because the Windows Installer service is trying to verify the digital certificate of the .msi installer file.  You can safely block the attempt with no harm, it will just attempt to do certificate validation using the system offline certificate store.  Regardless, it is NOT a phone-home mechanism.

[Arlecho]

Please do not change the domain name, the clients use that to talk to your screenconnect instance.
If you start hosting it elsewhere they simply do not know where to talk to anymore.
Also do not change the relay ports, that will cause the clients to be unable to connect too.

[Sinauth]

Hi all,

I'm wondering if anyone has tested with ScreenConnect_22.2.7294.8116_Release.msi?

Thanks!