Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - keenoar

#1
Hi,

Check the permissions of the user in the user's management screen and the access control of the node
#2
General Support / Re: Connection timed out: connect
August 01, 2024, 04:41:51 PM
check the image for both server and console configuration:

2024-08-01_163308.png
#3
General Support / Re: Connection timed out: connect
August 01, 2024, 04:14:55 PM
Hi,

1. You can change the listening port from the server configuration screen - parameter Client.ListenerPort. To connect from the console to a different port, append the port to the end of the server address (for example 192.168.0.1:4701)
2. looks like you have a big database with lots of alarms, users, DCIs, etc that are loading on startup. check which activity is taking too long, then you can clean it (if you have lots of alarms, terminate them, etc)



#4
General Support / Re: Connection timed out: connect
July 31, 2024, 12:08:54 PM
Hello,

Not sure if I understood your issue correctly, but console connects to the server on port 4701. So you should be able to telnet from computer where you are using the console to the server on port 4701.

Thanks,
#5
General Support / Re: Client stops responding
July 30, 2024, 11:07:31 AM
Hi,

Is this a fresh installation on your desktop or an upgrade?
If it is an upgrade, maybe you need to delete the .nxmc folder under your user profile

#6
Hello,

Due to security reasons, from NXSL you can read the primary host name using $node->primaryHostName but cannot change or set it.

Can you explain what you are trying to do, maybe there is another way to do it.

Thanks,
Kanan

#7
General Support / Re: Telegram Issues
February 17, 2023, 12:22:41 PM
Hello,

Can you share with us the server version and the system / OS you are running the server on?
Also, it would be good to share the server log file section where it shows the driver initialization is failing.

Thank you
#8
Hi,

Currently, this is not available. It is still being worked on for the new UI Console.

Thank you,
#9
you can use a filtering script in the EPP and match for the names of the nodes you want to dismiss. something like this:

if($node->name match "^unwanted_node.+")
{
    return false;
}
return true;
#10
Can you share a screenshot of the access control window?
#11
Hello!

The screenshot permission should be set on the node level. You need to right-click the desired node, select properties -> access control and allow / deny the user/group "Take screenshot" permission.

Currently, taking screenshots are not registered in the audit log.

Thanks,
#12
A quick solution would be to exclude the child nodes from source objects in the EPP for that rule.