Enterprise Console and Sophos Protection

Question

I built two Windows Server 2016 servers (one for Enterprise Console the other to test Sophos Protection to pull from Enterprise Console for definitions). ( For name sake the servers names are: Anti-virus01 and Test01 ) On Anti-virus01, I installed SEC successfully and after installation, I installed Sophos Protection successfully by manually installing from the setup.exe in the SAVSCFXP folder (could not push Protect Computers from SEC). When I right-click the Sophos icon in the notification bar and click on 'Update Now' it contacts server just fine and checks for new packages. 
 Now I completed the Sophos Protection installation the same exact way on the second Windows Server (Test01), while initially, it contacts the server for updates and grabs the latest definitions, after a few minutes it cannot contact server after an 'Update Now'. 
 Other Information: 
 - Running SEC 5.5.0 
 - Running version 10.8 Sophos Protection 
 - Running servers in an isolated envrionment 
 - In SEC, I get the following error: ERROR: Could not find a source for updated packages [0x0000071] for the server Test01. 
 Which in return, I viewed the log on Test01 located in C:\ProgramDataSophos\AutoUpdate\logs\alc.log, that states it cannot contact server and to check if computer is connected to network with a Windows Error 1909, which keeps locking the local account it is attached to that is on Anti-virus01. 
 - The 'Primary Location Details' in Sophos Protection are the same on Test01 compared to Anti-virus01, but the password field is blank (not sure why). Anti-virus01 can still contact SEC, but not Test01. 
 - Test01 is connected to network and is able to send and receive data. 
 - I've tried testing it with and without firewall settings with no avail 
 - Username and Password is correct for 'Source Details' in SEC on Anti-virus01 
 
 Am I missing a step or is there something I am doing wrong and how do I fix so the password field in 'Primary Location Details' section of Sophos Protection pulls the correct password? Thank you. 
 
 - Jeremy

Jeremy Reyes · Accepted Answer

Thanks for the reply. I figured it out. I had to input the password and username in the Default Policy in the Enterprise Console. That's what kept locking out the service account.