WIBU Configure Network Client - Revision history

Pavlina Monhartova at 05:30, 18 April 2025

2025-04-18T05:30:11Z

← Older revision		Revision as of 15:30, 18 April 2025
Line 18:		Line 18:
	<br>		<br>
	<li>Adding "Automatic server search" is optional. This will configure to client computer to search every computer on a organisations network for a TUFLOW server. This is a slower to function option than the targeted configuration described in the previous step.		<li>Adding "Automatic server search" is optional. This will configure to client computer to search every computer on a organisations network for a TUFLOW server. This is a slower to function option than the targeted configuration described in the previous step.
	<li>The client machine should now be configured to access the network TUFLOW dongle. This can be tested on the server by double clicking the TUFLOW Executable (for example TUFLOW_iSP_w64.exe). A ~~DOS~~ window should open which lists the licence information (licence types and numbers will be different to the example shown below).<br>		<li>The client machine should now be configured to access the network TUFLOW dongle. This can be tested on the server by double clicking the TUFLOW Executable (for example TUFLOW_iSP_w64.exe). A console window should open which lists the licence information (licence types and numbers will be different to the example shown below).<br>
	[[File:TUFLOW_DOS_Test1.JPG\|800px]] </li>		[[File:TUFLOW_DOS_Test1.JPG\|800px]] </li>
	</ol>		</ol>
Line 24:		Line 24:

	=Troubleshooting=		=Troubleshooting=
	If your licences are not listed in the ~~DOS~~ window when you test whether the connection to the server has been successful, consider the following:		If your licences are not listed in the console window when you test whether the connection to the server has been successful, consider the following:
	== Check Server Licence ==		== Check Server Licence ==
	Before testing connection to a server, verifying the TUFLOW licence on the server is functioning is a useful first troubleshooting steps.		Before testing connection to a server, verifying the TUFLOW licence on the server is functioning is a useful first troubleshooting steps.
	<ol>		<ol>
	<li> Login to the Server.		<li> Login to the Server.
	<li> Double clicking the TUFLOW Executable (for example TUFLOW_iSP_w64.exe). A ~~DOS~~ window should open which states the TUFLOW licenses associated with the server. Check the licence types and numbers associated with your configuration (the licence types and numbers will be different to the example shown below).<br>		<li> Double clicking the TUFLOW Executable (for example TUFLOW_iSP_w64.exe). A console window should open which states the TUFLOW licenses associated with the server. Check the licence types and numbers associated with your configuration (the licence types and numbers will be different to the example shown below).<br>
	[[File:TUFLOW_DOS_Test1.JPG\|600px]] </li>		[[File:TUFLOW_DOS_Test1.JPG\|600px]] </li>
	<li> If your licences are not listed in the ~~DOS~~ window when you test whether the server configuration has been successful, refer to [[ WIBU_Configure_Network_Server#troubleshooting \| Network Server Issue]].		<li> If your licences are not listed in the console window when you test whether the server configuration has been successful, refer to [[ WIBU_Configure_Network_Server#troubleshooting \| Network Server Issue]].
	</ol>		</ol>

Emilie Nielsen: /* Other */

2025-02-20T06:26:04Z

Other

← Older revision		Revision as of 16:26, 20 February 2025
Line 53:		Line 53:

	=Other=		=Other=
	If you are unable to get TUFLOW connecting to a network licence server please contact <u>support@tuflow.com</u>. <br>		If you are unable to get TUFLOW connecting to a network licence server please contact <u>[mailto:support@tuflow.com support@tuflow.com]</u>. <br>
	<br>		<br>

Chris Huxley: /* Other */

2025-02-18T23:38:40Z

Other

← Older revision		Revision as of 09:38, 19 February 2025
Line 55:		Line 55:
	If you are unable to get TUFLOW connecting to a network licence server please contact <u>support@tuflow.com</u>. <br>		If you are unable to get TUFLOW connecting to a network licence server please contact <u>support@tuflow.com</u>. <br>
	<br>		<br>

	{{Tips Navigation
	\|uplink=[[Wibu_Dongles\| Return to WIBU Licensing Main Page]]
	}}

Chris Huxley: /* Method */

2024-12-03T06:05:01Z

Method

← Older revision		Revision as of 16:05, 3 December 2024
Line 13:		Line 13:
	[[File:CodeMeter_ControlCentre.png]]<br>		[[File:CodeMeter_ControlCentre.png]]<br>
	<br>		<br>
	<li>In CodeMeter WebAdmin navigate to the '''Configuration >> Basic >> Sever Search List''' tab and enter the server name or IP address in the '''Server Search''' list. Using the server name is typically a more problem free option, due to the fact restarting the ~~srver~~ may result in a change in IP address, which will break the connection to the server. Click Add to include the server to the list.</li>		<li>In CodeMeter WebAdmin navigate to the '''Configuration >> Basic >> Sever Search List''' tab and enter the server name or IP address in the '''Server Search''' list. Using the server name is typically a more problem free option, due to the fact restarting the server may result in a change in IP address, which will break the connection to the server. Click Add to include the server to the list. Click Apply to make the changes. </li>
	<br>		<br>
	[[File:CodeMeter_WebAdmin.png \| 1000px]]<br>		[[File:CodeMeter_WebAdmin.png \| 1000px]]<br>
	<br>		<br>
			<li>Adding "Automatic server search" is optional. This will configure to client computer to search every computer on a organisations network for a TUFLOW server. This is a slower to function option than the targeted configuration described in the previous step.
	Click Apply to make the changes.
	<li>The client machine should now be configured to access the network TUFLOW dongle. This can be tested on the server by double clicking the TUFLOW Executable (for example TUFLOW_iSP_w64.exe). A DOS window should open which lists the licence information (licence types and numbers will be different to the example shown below).<br>		<li>The client machine should now be configured to access the network TUFLOW dongle. This can be tested on the server by double clicking the TUFLOW Executable (for example TUFLOW_iSP_w64.exe). A DOS window should open which lists the licence information (licence types and numbers will be different to the example shown below).<br>
	[[File:TUFLOW_DOS_Test1.JPG\|800px]] </li>		[[File:TUFLOW_DOS_Test1.JPG\|800px]] </li>

Chris Huxley: /* Method */

2024-12-03T06:01:16Z

Method

← Older revision		Revision as of 16:01, 3 December 2024
Line 13:		Line 13:
	[[File:CodeMeter_ControlCentre.png]]<br>		[[File:CodeMeter_ControlCentre.png]]<br>
	<br>		<br>
	<li>In CodeMeter WebAdmin navigate to the '''Configuration >> Basic >> Sever Search List''' tab and enter the server name or IP address in the '''Server Search''' list. Using the server name is typically a more problem free option, due to the fact restarting the srver may result in a change in IP address, which will break the connection to the server. Click Add to include the server IP to the list.</li>		<li>In CodeMeter WebAdmin navigate to the '''Configuration >> Basic >> Sever Search List''' tab and enter the server name or IP address in the '''Server Search''' list. Using the server name is typically a more problem free option, due to the fact restarting the srver may result in a change in IP address, which will break the connection to the server. Click Add to include the server to the list.</li>
	<br>		<br>
	[[File:CodeMeter_WebAdmin.png \| 1000px]]<br>		[[File:CodeMeter_WebAdmin.png \| 1000px]]<br>

Chris Huxley: /* Method */

2024-12-03T05:59:55Z

Method

← Older revision		Revision as of 15:59, 3 December 2024
Line 13:		Line 13:
	[[File:CodeMeter_ControlCentre.png]]<br>		[[File:CodeMeter_ControlCentre.png]]<br>
	<br>		<br>
	<li>In CodeMeter WebAdmin navigate to the '''Configuration >> Basic >> Sever Search List''' tab and enter the server name or IP address in the '''Server Search''' list. Click Add to include the server IP to the list.</li>		<li>In CodeMeter WebAdmin navigate to the '''Configuration >> Basic >> Sever Search List''' tab and enter the server name or IP address in the '''Server Search''' list. Using the server name is typically a more problem free option, due to the fact restarting the srver may result in a change in IP address, which will break the connection to the server. Click Add to include the server IP to the list.</li>
	<br>		<br>
	[[File:CodeMeter_WebAdmin.png \| 1000px]]<br>		[[File:CodeMeter_WebAdmin.png \| 1000px]]<br>

Chris Huxley: /* Troubleshooting */

2024-12-02T02:55:41Z

Troubleshooting

← Older revision		Revision as of 12:55, 2 December 2024
Line 25:		Line 25:
	=Troubleshooting=		=Troubleshooting=
	If your licences are not listed in the DOS window when you test whether the connection to the server has been successful, consider the following:		If your licences are not listed in the DOS window when you test whether the connection to the server has been successful, consider the following:
			== Check Server Licence ==
			Before testing connection to a server, verifying the TUFLOW licence on the server is functioning is a useful first troubleshooting steps.
			<ol>
			<li> Login to the Server.
			<li> Double clicking the TUFLOW Executable (for example TUFLOW_iSP_w64.exe). A DOS window should open which states the TUFLOW licenses associated with the server. Check the licence types and numbers associated with your configuration (the licence types and numbers will be different to the example shown below).<br>
			[[File:TUFLOW_DOS_Test1.JPG\|600px]] </li>
			<li> If your licences are not listed in the DOS window when you test whether the server configuration has been successful, refer to [[ WIBU_Configure_Network_Server#troubleshooting \| Network Server Issue]].
			</ol>

	== Check Server Connectivity ==		== Check Server Connectivity ==
	A easy way to check for connectivity between the client computer and the licence server is to ping the server from the client machine. This can be done by:		A easy way to check for connectivity between the client computer and the licence server is to ping the server from the client machine. This can be done by:

Chris Huxley: /* Other */

2024-12-02T01:57:56Z

Other

← Older revision		Revision as of 11:57, 2 December 2024
Line 44:		Line 44:

	=Other=		=Other=
	If you are unable to get TUFLOW connecting to a network licence server please contact <u>support@tuflow.com</u>.		If you are unable to get TUFLOW connecting to a network licence server please contact <u>support@tuflow.com</u>. <br>
			<br>

	{{Tips Navigation		{{Tips Navigation

Chris Huxley: /* Other */

2024-12-02T01:57:06Z

Other

← Older revision		Revision as of 11:57, 2 December 2024
Line 44:		Line 44:

	=Other=		=Other=
	If you are unable to get TUFLOW connecting to a network licence please contact <u>support@tuflow.com</u>.		If you are unable to get TUFLOW connecting to a network licence server please contact <u>support@tuflow.com</u>.

	{{Tips Navigation		{{Tips Navigation

Chris Huxley: /* Check Server Connectivity */

2024-12-02T01:47:33Z

Check Server Connectivity

← Older revision		Revision as of 11:47, 2 December 2024
Line 32:		Line 32:
	<tt>ping 192.168.1.1</tt><br>		<tt>ping 192.168.1.1</tt><br>
	<tt>ping TUFLOW_server</tt><br>		<tt>ping TUFLOW_server</tt><br>
	If successful a the output will show that a reply is received as per the image below.<br>		If successful the output will show that a reply is received as per the image below.<br>
	[[File:CM ping server.jpg\|800px]]		[[File:CM ping server.jpg\|800px]]
	<br>		<br>
Line 39:		Line 39:
	</li>		</li>
	</ol>		</ol>

	== Check AV and Port Blocking ==		== Check AV and Port Blocking ==
	If the above steps have been performed and the client computer is still unable to access the network licence, the most likely reason is that there is anti-virus or a firewall blocking access. By default the Codemeter software uses port 22350 for communication. This can be changed in the '''Configuration >> Server''' tab in CodeMeter webadmin. Temporarily disabling any antivirus on the computers could be used to confirm if this is causing the communication issue, if so, an exception would need to be added to your AV software.		If the above steps have been performed and the client computer is still unable to access the network licence, the most likely reason is that there is anti-virus or a firewall blocking access. By default the Codemeter software uses port 22350 for communication. This can be changed in the '''Configuration >> Server''' tab in CodeMeter webadmin. Temporarily disabling any antivirus on the computers could be used to confirm if this is causing the communication issue, if so, an exception would need to be added to your AV software.