How to Troubleshoot the System if the xPortalNet Server PC is Able to Ping All IP Controllers in Command Prompt, but All Controller Statuses are Shown as Down in xPortalNet Software

Problem (Issue) Statement:

How to troubleshoot if all IP controllers are able to ping in command prompt but unable to UP in xPortalNet software

Description:

During the process of Servicing and Maintenance at site, or attending to ad-hoc troubleshooting for Card Access System breakdown calls, System Integrator will mostly face issues on how to troubleshoot the system when the controller statuses are shown as Down at xPortal software, but the controller IP address is able to be pinged from the xPortalNet Server PC. 

Related Software:

  • xPortalNet Lite v1.5
  • xPortalNet Standard v1.5
  • xPortalNet PS v1.5
  • xPortalNet HS

Related Hardware:

All IP connection based controller models

  • XP- SNETv2/ XP-SNET-GAC/XP-SNET-LID
  • XP- M Series Controller
  • XP- M4L Controller
  • XP- GT3500 Controller
  • XP- GTR1500 Controller

System Application:

  • Door Access System
  • Lift Masking System
  • Vehicle Access System
  • Turnstile Access System

Symptom and Finding:

After ensuring that the model for the controller was correctly selected, the controller status is still shown as Down in xPortalNet software.
Controller Status Shown as Down in Controller Tab 
Figure 1: Controller Status Shown as Down in Controller Tab

.

User then used the Command Prompt to ping the controller, and the Command Prompt is able to receive response from the controller's iP address.
Command Prompt Receiving Response from Controller IP Address 
Figure 2: Command Prompt Receiving Response from Controller IP Address

Cause:

  • Blocked by Windows Firewall
  • Software and hardware configuration error
  • xPortalNet Server PC was not assigned with static IP address
  • Controller IP address not configured correctly

Solution:

Warning!

  • Users are not recommended to run any xPortal software in Windows XP operating system as the system is unstable

  • Users are also advised to stop the xPortal Services before shutting down the Server PC to prevent any missing transaction issues.

.

.

Summary:

.

Step-by-step Guide:

  • To check Windows Firewall settings and to allow xPortalNet software in the antivirus exception list on Server PC:

Step 1: Users have to check and ensure that Window Firewall has enable the software for communication.

Knowledge Base Link

Users may refer to How to Allow Software to Communicate Through Windows Firewall to complete the process.

.

.

Step 2: Check that xPortalNet software has properly been added into the antivirus software's exception list.

Knowledge Base Link

Users may refer to How to Add a Software into Antivirus Exception List to complete the process.

.

.

Step 3: If all configurations are all checked and set properly but controllers still unable to show UP status in xPortalNet software, user may to refer next section: To cross check the configuration settings between xPortalNet software and controller's Web Diagnostic.

.

.

  • To cross check the configuration settings between xPortalNet software and controller's Web Diagnostic:

Step 1: Cross check and ensure that the configuration settings between xPortalNet software and controller's Web Diagnostic is the same.

.

Step 2: If the settings are the same between xPortalNet software and controller's Web Diagnostic, users should proceed to the next section: To check the xPortalNet Server PC IP Address.

..

.

  • To check the xPortalNet Server PC IP Address:

Step 1: Launch the Command Prompt using search bar on the xPortalNet Server PC.

Knowledge Base Link

Users may refer to How to Launch the Command Prompt in Windows Operating System to launch the Command Prompt.

.

.

Step 2: Type ipconfig and press Enter to display the networking information on the xPortalNet Server PC.
Command Prompt Window Showing the Ethernet Adapter Settings 
Figure 3: Command Prompt Window Showing the Ethernet Adapter Settings

.

Step 2: Under the Ethernet Adapter Ethernet section, the IP address, subnet mask and default gateway for the network adaptor is shown. Users can also check the static IP address assigned to xPortalNet Server's PC.
Ethernet Adapter Ethernet Section 
Figure 4: Ethernet Adapter Ethernet Section

.

Step 3: If the static IP Address configured in the software is incorrect, users will have to correct the configuration settings.

Knowledge Base Link

Users may refer to How to Pre-configure Network Connection for IP Controllers to complete the process.

.

Step 4: If the controller's status still remained as Down, proceed to the next section: To check the Device Communication IP Address configured on xPortalNet Services.

.

.

  • To check the Device Communication IP Address configured on xPortalNet Services:

Step 1: Go to Taskbar on desktop > select xPortalNet Services.
xPortalNet Services Icon 
Figure 5: xPortalNet Services Icon 

.

Step 2: Right click the xPortalNet Service and select Configure Device Communication IP Address.
Configure Device Communication IP Address in the Right-click Menu 
Figure 6: Configure Device Communication IP Address in the Right-click Menu

.

Step 3: The Set IP Address window will be shown as below and will indicate the current IP Address (xPortalNet Server PC current IP Address).
Select IP Address Window 
Figure 7: Select IP Address Window

.

Step 4: If the IP Address is wrong, click on the drop-down arrow and select the correct IP address. Click OK to save the changes.
Selecting the Correct IP Address for xPortalNet Server PC 
Figure 8: Selecting the Correct IP Address for xPortalNet Server PC

.

Step 5: The following message will be shown to indicate that the Setting has been saved successfully. Click OK to continue.
Setting has been Saved Successfully Window 
Figure 9: Setting has been Saved Successfully Window

.

Step 6: Next, the software will prompt the message to indicate that The IP Address for device communication has been changed. Click Yes to restart the communication.
The IP Address for Device Communication has been Changed Window 
Figure 10: The IP Address for Device Communication has been Changed Window

.

Step 7: Last message will be shown and indicate that the request to restart communication has been submitted successfully. Click OK to complete the process.
The Request to Restart Communication has been Submitted Successfully Window
Figure 11: The Request to Restart Communication has been Submitted Successfully Window

Common Issue

NIL

Date Documentation:

27/3/2020 (Rev 1.0)

PROOF-READ

.

Related Articles.

Containing the label "controller-down"

Filter by label

There are no items with the selected labels at this time.

.


.

© MicroEngine Technology Sdn Bhd (535550-U). All rights reserved.