logo

The ConnectWise Control forum has moved to ConnectWise University! This forum has been locked and is in read-only mode. Click here for instructions on how to access the new forum.

Welcome Guest! You can not login or register.

Notification

Icon
Error

Options
Go to last post Go to first unread
evputten  
#1 Posted : Tuesday, January 22, 2019 7:01:18 PM(UTC)
evputten


Rank: Member

Medals: ScreenConnect Advisor: Focus Group MemberLevel 1: Random Act of Kindness! Received One Thanks!

Joined: 7/25/2015(UTC)
Posts: 98
Netherlands
Location: Moerkapelle

Thanks: 3 times
Was thanked: 6 time(s) in 6 post(s)
Hi,

I had my Screenconnect webservice running on port 80 and the relay on port 443

To changed that i made the following construction.
(IP addresses are fictional)

One server with 2 ip address :
support.company.name ip address 123.123.123.1
remote.company.name ip address 123.123.123.2

My site was on support.company.name
changed the ip address of the Screenserver to 123.123.123.2
changed the web.config WebserverListenURI from support.company.name:80 to remote.company.name:443
Changed the web.config RelayListenURI from : relay://+:443/ to relay://+:80/

After that i could reach the Screenconnect webservice on https://remote.company.name (installed the SSL certificate earlier)

Now offcourse none of the already installed clients could longer login, a new installed agent works fine.

I tried to do a netsh netproxy on the Screenconnect machine but found out Screenconnect kept changing the ports.
So I remove the ip address 123.123.123.1 from the Screenconnect Machine.
On a server next to it i added 123.123.123.1 as a secondary IP address.
Here i ran

netsh interface netproxy add v4tov4 listenport=80 listenaddress=123.123.123.1 connectport=443 connectaddress=123.123.123.2 protocol=tcp
netsh interface netproxy add v4tov4 listenport=443 listenaddress=123.123.123.1 connectport=80 connectaddress=123.123.123.2 protocol=tcp
(be sure to have ip v6 protocol installed for this to work)


Now all machine where polling the old IP address being forward to the new port on the newaddress.
And voila all machines checked back into screenconnect.

I update to the newest screenconnect version, and could see the red version number for all machines not updated yet.
I told all machines to reinstall.

I figured the App.config and Web.config would update on all machines this way, and soon all machine should connect through remote.company.name instead of support.company.name.

I saw all the machines update, but when i turned off the 123.123.123.1 machine to check something all the clients went back offline.
So the web.config is NOT applied to all the agents after a reinstall.

I could verify that because all machine that had a new agent installed after the above job connect correct to the right machine without going through the proxy machine.

What can i do the make all the already installed agents use the correct hostname and port ?


Kind regards,
Erik.











evputten  
#2 Posted : Tuesday, January 29, 2019 12:25:11 PM(UTC)
evputten


Rank: Member

Medals: ScreenConnect Advisor: Focus Group MemberLevel 1: Random Act of Kindness! Received One Thanks!

Joined: 7/25/2015(UTC)
Posts: 98
Netherlands
Location: Moerkapelle

Thanks: 3 times
Was thanked: 6 time(s) in 6 post(s)
Anybody ?
(I'll bet Scott knows if there's a way Smile )

Otherwise i'll probably have to make a program to rewrite the registry settings for the Windows customers.
No clue where i can find those settings on a Mac.....
Scott  
#3 Posted : Tuesday, January 29, 2019 12:28:25 PM(UTC)
Scott


Rank: Administration

Medals: Level 4: Wise Old Owl! Received 100 Thanks!

Joined: 3/28/2014(UTC)
Posts: 2,862
United States

Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
Do you have the web.config setting RelayAddressableUri configured to anything? Is it present?
ScreenConnect Team
evputten  
#4 Posted : Tuesday, January 29, 2019 12:54:46 PM(UTC)
evputten


Rank: Member

Medals: ScreenConnect Advisor: Focus Group MemberLevel 1: Random Act of Kindness! Received One Thanks!

Joined: 7/25/2015(UTC)
Posts: 98
Netherlands
Location: Moerkapelle

Thanks: 3 times
Was thanked: 6 time(s) in 6 post(s)
Hi Scott,

I did not have the RelayAddressableUri filled in.
I have set it to relay://remote.company.name:80/ now.

After that did an update client parameters and did a client reinstall.

I don't see a change in the registry after that, HKLM\SYSTEM\Setup\FirstBoot\Services\(unique-id)\Path still points to the old URL and port.
Also i still see communications going out for the updated client to the old URL and port.

Regards,
Erik.
evputten  
#5 Posted : Tuesday, February 5, 2019 12:18:11 PM(UTC)
evputten


Rank: Member

Medals: ScreenConnect Advisor: Focus Group MemberLevel 1: Random Act of Kindness! Received One Thanks!

Joined: 7/25/2015(UTC)
Posts: 98
Netherlands
Location: Moerkapelle

Thanks: 3 times
Was thanked: 6 time(s) in 6 post(s)
I stand corrected, i did not work, but it took a longer period for all the agents to switch.
(Maybe after a reboot ?)

Kind regards,
Erik.


TO make it clear, it did not work at first, the agent has to reboot after the reinstall for it to work.
Everything is fine now.

Edited by user Wednesday, February 20, 2019 3:37:07 PM(UTC)  | Reason: Not specified

Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.