SOLUS 3 - Install failed - Access denied to the remote machine

[Bankesy]

Good evening,

 

Hoping somebody has experienced this issue before and can guide me in the right direction. SIMS helpdesk moved our installation of SOLUS onto a different server in order to fix an issue with downloading and installing patches etc.

 

But now we cannot deploy SIMS to new clients because we just get hit with an 'Access denied to the remote machine, check the username and password you supplied are valid for the remote machine'

 

Using credentials that we always used before the installation was moved. SIMS say it is the network, firewall, Windows Updates etc. and I will admit that the setup I inherited was unusual because the SOLUS3 Deployment Service didn't sit on the same server as the database (does now) and was using custom ports rather than SIMS suggested but I edited firewall rules to match SIMS suggested setup and was able to update SIMS on an existing client.

Any ideas welcome, thanks in advance.

[Steve21]

Have you deployed the normal Solus firewall exclusions previously? Did you have it limited to a certain IP/host etc that might have changed?

If it's the same domain/credentials etc it's unlikely to be much else I'd have said related to the access denied error

Steve

[Bankesy]

@Steve21 I'm not really sure if the normal firewall exclusions were deployed as I inherited the setup but I assume they were for anything to work in the first place. Your suggestion makes sense, as I say, the SOLUS3 Deployment Service has moved server.

 

The only obvious firewall rule I could see on clients was one allowing the ports required for SOLUS, will try adding the normal firewall rules to one client and see what that does.

 

In my mind, an error about credentials isn't the same as an error about ports\firewall, which we were getting initially after the move until I edited that one firewall rule that I could see.

 

Thanks

[TooOld4This]

On the workstation, run these from an elevated command prompt and then give it a reboot.

 

netsh advfirewall firewall add rule name="Solus 3 DS" dir=in action=allow protocol=TCP localport=52965

netsh advfirewall firewall add rule name="Solus 3 DS" dir=out action=allow protocol=TCP localport=52965

netsh advfirewall firewall add rule name="Solus 3 Agent" dir=in action=allow protocol=TCP localport=52966

netsh advfirewall firewall add rule name="Solus 3 Agent" dir=out action=allow protocol=TCP localport=52966

netsh advfirewall firewall add rule name="Solus 3 Agent UI" dir=in action=allow protocol=TCP localport=8739

netsh advfirewall firewall add rule name="Solus 3 Agent UI" dir=out action=allow protocol=TCP localport=8739

netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes

netsh advfirewall firewall set rule group="Windows Remote Management" new enable=yes

netsh advfirewall firewall set rule group="File and Printer Sharing" new ENABLE=Yes

 

Alternatively as a test, turn off the workstation firewall completely to see if it accepts the credentials. Normally you are right though as Solus will report that the Access Denied error is Firewall based.

Edited October 31, 2025 by TooOld4This

[Bankesy]

@TooOld4This

 

Thanks, those are the normal firewall rules that SIMS gave me, tried them on one client and issue is resolved. Have tried adding in to Windows Firewall GPO but not sure if the rule groups are inbound or outbound?

[Steve21]

Agent ones for clients are all inbound unless you have your firewalls set to block outbound for extra security 

 

Steve

[Bankesy]

@Steve21 @TooOld4This

 

Thanks both, all working now