1. Make sure windows network -component is enabled
Check that your Windows network component is enabled. See win_client_setup.pdf. Terra License Manager and Terra License Server uses Windows network pipes for communication. As an extra feature it provides a mechanism for transferring authentication contexes - which may be the major pain and causes problems. Best of all, it's beyond scope of Terrasolid support.
2. Try using IP
In theory, Windows network doesn't use tcp/ip but in practice it allways will. This brings a nice workaround for it legacy limitations, without needing to use WINS or other specialized windows servers. Get IP from server, by typing into command prompt (see get_ip.pdf):
ipconfig
Insert the IP then into License Manager (see manager_set_ip.pdf) as a server.
3. Test windows networking
If the windows networking doesn't work, License Server can't work. Extended guidance on how to get Windows network running is unfortunately beyond of Terrasolid support. But good way to test that windows networking works is to type in command promt (see testing_smb.pdf):
net view <server-ip>If command returns success, your windows network operates correctly, and most likely problems are related to windows authentication contexes. If command fails, then there are some problems in your network. In this case, try opening firewall for the single most dangerous port on the Internet, 139. And if this doesn't get you excited enought, add 445 as cream to top of a cake. All thou, cake may be a lie.
