Sophos

Online support

Product maintenance

Contact support

Support services

Sophos NAC Advanced: how to access Web interface when a page not found error is received

This article describes how to access the Web interface after a NAC installation when a 404 Page Not Found error is received.

What to do

This error occurs because Microsoft .NET Framework 2.0 is not registered correctly with IIS. This condition can happen if the IIS Windows component and/or ASP .NET is installed after the .NET Framework 2.0 on the server. The Sophos NAC installation attempts to correctly configure .NET Framework 2.0 with IIS during the NAC application installation. However, some scenarios exist where this process does not work and this causes the 404 Page Not Found error.

To confirm that .NET Framework 2.0 is registered correctly:

  1. Open the Internet Information Services (IIS) Manager.
  2. Right-click the Web Sites folder and select Properties. 
  3. Click the ISAPI Filters tab. This tab should contain an entry for ASP .NET 2.0. If the entry does not exist, you need to re-register .NET Framework 2.0 with IIS. Proceed to the To register .NET Framework 2.0 with IIS section below.
  4. Navigate to the Sophos NAC virtual directory.
  5. Right-click Sophos NAC and select Properties.
  6. Click the Documents tab.
  7. Verify that default.aspx or Default.aspx is listed. If there is another case variation of default.aspx in the list, note the case variation and provide it to technical support if you cannot resolve the issue with these instructions.
  8. If default.aspx or Default.aspx is not listed, click Add, type default.aspx or Default.aspx, and click OK.
  9. Click the ASP.NET tab.
  10. Verify that the ASP.NET version is 2.0.50727.
  11. If the version is not set correctly, select the 2.0.50727 version from the list box and click OK. If the version is not available, you need to re-register .NET Framework 2.0 with IIS. Proceed to the To register .NET Framework 2.0 with IIS section below.
  12. If the version is set correctly, click Cancel.
  13. Locate and click the Web Service Extensions folder.
  14. Verify that ASP.NET version 2.0.50727 is listed and the extension status is set to Allowed. If the extension status is set to Prohibited, change it to Allowed. If the extension is set to Prohibited, note this information and provide it to technical support if you cannot resolve the issue with these instructions. If the version is not available, you need to re-register .NET Framework 2.0 with IIS. Proceed to the To register .NET Framework 2.0 with IIS section below.

To register .NET Framework 2.0 with IIS:

  1. Open a command prompt.
  2. Change the directory to %SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727. If this directory does not exist, you need to install .NET Framework 2.0.
  3. Type "aspnet_regiis.exe -r". This process takes a few minutes to complete.
  4. Restart the server. If the problem persists after this registration, consider repairing Microsoft .NET Framework 2.0 or downloading Microsoft .NET Framework 2.0 Service Pack 1.

If you need more information or guidance, then please contact technical support.