LightNet Troubleshooting
Last updated
Was this helpful?
Last updated
Was this helpful?
If you have trouble transferring assets to the Secondary machines in LightNet, this will most likely be visible in the LightNet Transfer popup. If you hover your mouse over the progress bar of each non-transferable asset, you will see a more detailed description of what the error is.
Another way to figure out what is causing the error, is to look in the LightAct Logs window. Here, you can see the actual robocopy command that LightAct used when it tried to transfer the assets.
If you run it directly in the cmd window, you might get additional information.
For example, in the case of getting The user name or password incorrect message, you will most likely have to set up the sharing correctly.
For more info, please refer to .
LightAct servers come with a pre-configured LightNet setup. However, if you seem to be having trouble detecting other machines in LightNet, here are a few potential causes:
Machines are not in the same network.
Machines are running different versions of LightAct.
LightNet is not enabled on all of the machines.
If none of the above seems to be the reason for your issue, then you might have to consider taking a look at your Network and Windows Security settings.
First, the Network your machines are connected to should be set to Private. You can check or modify this in Network Status -> Properties -> Network profile.
Next, go to Windows security -> Firewall & Network protection -> Advanced settings. On the left-hand side of this window, you will notice two tabs called Inbound Rules and Outbound Rules.
All entries in these two tabs which are part of the group File and Printer Sharing or Network Discovery have to be Enabled for Private networks.
Upon changing these settings, restart the machines and try to Scan network in LightNet once again.
