[sims] SIMS firewall and login issue

[365Steve]

I've trawled through plenty of posts about sims and it's issues with the firewall but this one has me baffled.

 

If we have the domain firewall turned off, users can login to sims with no issue.

Turn the firewall back on and login fails with error "Sims connection failed for login 'user', reason 0"

 

Any ideas what's needed to allow the login to proceed, would be hugely appreciated.

tia.

[mikemcsharry]

I've trawled through plenty of posts about sims and it's issues with the firewall but this one has me baffled.

 

If we have the domain firewall turned off, users can login to sims with no issue.

Turn the firewall back on and login fails with error "Sims connection failed for login 'user', reason 0"

 

Any ideas what's needed to allow the login to proceed, would be hugely appreciated.

tia.

 

Do you have the correct ports open in your firewall?

Also, Sims can be a bit poor at catching up with DNS. Can you ping the SIMS server by name from a PC and vice versa?

[password1234]

I've trawled through plenty of posts about sims and it's issues with the firewall but this one has me baffled.

 

If we have the domain firewall turned off, users can login to sims with no issue.

Turn the firewall back on and login fails with error "Sims connection failed for login 'user', reason 0"

 

Any ideas what's needed to allow the login to proceed, would be hugely appreciated.

tia.

 

You got the SOLUS Firewall Script to run?

[TwistedHelixis]

You got the SOLUS Firewall Script to run?

What is that????

[password1234]

What is that????

 

How are you installing SIMS? Is it Manually or are you pushing it out Via SOLUS?

 

We use the following Script you could try running this on a workstation that is having an issue (Copy and paste and save as a .bat file) and run as administrator or copy the below to Command prompt on the affected machine and see if that works

 

we had a similar problem to what you are describing

 

Reason 0 is due to SIMS not being able to see the Server where it is installed from so its a firewall issue for sure

 

Try that see how it goes!

 

 

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

 

 

[ITGURU]

Check SQL Services Configuration Manager for what ports SQL server is using and allow those through. If using Dynamic ports, allow the sqlservice

[365Steve]

Hi all, thanks for the useful replies.

I did get sent some info from capita support, which hopefully will help others, though the script above seems to be very comprehensive and time saving - cheers @password1234

The issue in this school was fixed when I added the SQL rules below. Still don't understand how it had worked for so long, then suddenly stopped - but such is life.

 

 

if the Windows Defender firewall is enabled on the SIMS server then program exception rules will need to be added for the following services:

 

SQL Server Browser

SQL Server (SIMS)

SIMS .net Document Server

SIMS Services Manager

 

For each of the above, first go to Windows services, right-click the service and select Properties. Make a note of the path to the executable, then in your firewall (e.g. Windows Defender Firewall) create a new inbound rule for that program.

 

More information on configuring the Windows Firewall to allow SQL access can be located here: http://msdn.microsoft.com/en-us/library/cc646023.aspx

 

For SOLUS3 to work you will also need to add the following port exceptions to the firewall:

TCP ports 52965, 52966, 8739, 139

UDP ports 137 and 138

 

When adding the exceptions make sure that they are added to domain, private and public profile - sometimes when the server reboots it connects to a different firewall profile (e.g. the public profile), if the rules haven't been added then you end up with being unable to access SIMS.