| Error |
Probable Problem |
Solution |
| After I login to MagNOS, it just throws me back to the login screen without any error message or this happens when I select one of my workstations in the selector if I have more than one workstation |
When it throws you back to the login screen, it is the VDI client that terminates when trying to connect. Most often this happens with the Horizon client if there is no working network path to the workstation. This is most often caused by routing problems which cause the client to give up before even trying. |
Check your network path.
Try tcpdump or Wireshark in your routers to check if traffic is coming there.
Check your client gateway IP in the SSC-server.
|
| After I login to MagNOS, it takes a long time and then the Horizon client or VNC client shows a timeout or connection error. |
Some firewall is blocking your traffic or the Horizon/VNC server host is rejecting the connection. |
Check your firewalls and check your connection parameters in Horizon. |
| I am using a smartcard or other token to login to MagNOS but keeps getting an error message "Error in authentication system" |
You do not have the CA and a CRL for the PKI used on you card installed in the SSC-server or you have not rebooted the MagNOS-client after installing these. If you have NOT checked the "Skip user mapping" in Domain Data on the SSC-server, this can also be due to the fact that you have NOT added the user in the SSC-server User Management GUI. |
Install your CA/CRL for the smartcard PKI in the SSC-server and either use "Skip user mapping" or define the user in the SSC-server. |
| I am using the MagNOS password image but cannot login. It just flashes a red message that is too fast to read. |
You have NOT added the user in the SSC-server User Management GUI or if using a remote LDAP-server, the user is not there OR
You are entering the wrong password.
|
Define the user in the SSC-server or remote LDAP and remember the password. |
| When using VNC towards a Linux machine configured according to the manual, I often get a connection error. |
Timing in the VNC-server and the session handling mechanism built for this resets the connection. |
Try again in the error box that is shown. |
| My MagNOS client is booted and I see the login screen but it shows "Degraded" in the upper right corner and I cannot login |
The configuration for the client has not been fetched correctly. |
In the SSC server, check that the client is shown in the "Provisioned clients" view and that it has been given a certificate. If this is done, try to reboot the client. Sometimes it fails to fetch the config due to intermittent network problems. |
| My MagNOS will not boot. It just shows that it is trying to get a network address. |
The SSC-server is not reachable on the network OR
The client is not provisioned and DHCP-policy in the SSC-server is set to "DHCP reserved" and not only "DHCP".
|
Check the SSC-server DHCP-policy in Domain Data and the "Provisioned clients" view so that the client is provisioned. If that is ok, check your network connectivity between SSC-server and MagNOS client. |
| My MagNOS will not boot. It shows some text and then blanks the screen and shows the same text again. |
The SSC-server does not have an installed client ISO image OR
The client has not been staged and provisioned properly OR
The client is staged on another SSC-server and that data has not been synchronized to the serving SSC-server OR
You have several DHCP-servers on the network that are not redundant SSC-servers.
|
In the SSC-server:
Check installed client image.
Check that the client is visible in the "Provisioned clients" view
Check the text about NVRAM certificates shown early during boot. All certificates and keys shall be present.
Check your network
Re-stage the client by removing it in the SSC-server, clearing the TPM and attaching it to staging network again and perform all steps for provisioning it.
|
