telnet era_server 2222\n<\/code><\/pre>\nIf screen goes blank, it means the port is open and clients should be able to report their status to server. Do it from client machine - on WinXP telnet client is installed by default, but if it’s Win7, you have to install it first via Programs and Functions/Enable Windows Components (thanks Microsoft).<\/p>","upvoteCount":1,"datePublished":"2013-03-23T10:53:18.000Z","url":"https://community.spiceworks.com/t/eset-license-update-clients-no-longer-updating/202216/11","author":{"@type":"Person","name":"krzysztofradomski","url":"https://community.spiceworks.com/u/krzysztofradomski"}},"suggestedAnswer":[{"@type":"Answer","text":"
From what I know, the only thing that was changed with the license, which had already expired. The licence was updated, but none of the clients have gotten updates since. The server can update just fine and the mirror is properly configured (I’ve quadruple checked). I can ping the server computer from the client and vice versa. the ESET RA service has been restarted a couple times since this and I have been told that the computer it resides on has been restarted as well. I have checked the uniformity of the settings on both the server and client end to match properly. I have attempted to push an update to my computer from the server to just sit at the message ‘Waiting’ for over 2 hours. I am out of ideas.<\/p>\n
If you need more information, please do not hesitate to ask.<\/p>","upvoteCount":3,"datePublished":"2013-03-22T18:07:54.000Z","url":"https://community.spiceworks.com/t/eset-license-update-clients-no-longer-updating/202216/1","author":{"@type":"Person","name":"joereiber","url":"https://community.spiceworks.com/u/joereiber"}},{"@type":"Answer","text":"
The obvious question is, do your clients have the new license deployed? Can you see it in advanced setting/kernel/settings/license keys? If not, did you deployed the key in your default policy applied to network machines?<\/p>\n
If I remember well, uploading a license key to the server is not enough - you have to deploy it explicitly in the policy manager.<\/p>","upvoteCount":0,"datePublished":"2013-03-22T18:30:06.000Z","url":"https://community.spiceworks.com/t/eset-license-update-clients-no-longer-updating/202216/2","author":{"@type":"Person","name":"krzysztofradomski","url":"https://community.spiceworks.com/u/krzysztofradomski"}},{"@type":"Answer","text":"
That is infact something I noticed was completely blank. I could find no settings for pushing the license to the clients. What do I have to do to fix this?<\/p>","upvoteCount":0,"datePublished":"2013-03-22T18:31:14.000Z","url":"https://community.spiceworks.com/t/eset-license-update-clients-no-longer-updating/202216/3","author":{"@type":"Person","name":"joereiber","url":"https://community.spiceworks.com/u/joereiber"}},{"@type":"Answer","text":"
Sorry, I edited my first post. Use policy manager.<\/p>","upvoteCount":0,"datePublished":"2013-03-22T18:40:21.000Z","url":"https://community.spiceworks.com/t/eset-license-update-clients-no-longer-updating/202216/4","author":{"@type":"Person","name":"krzysztofradomski","url":"https://community.spiceworks.com/u/krzysztofradomski"}},{"@type":"Answer","text":"
I put the proper license where it needs to be in the policy manager and ensured that all of the client are attached to that policy. How long might that take to trickle down? I’m still getting “Could not connect to server” from the client.<\/p>","upvoteCount":0,"datePublished":"2013-03-22T18:55:55.000Z","url":"https://community.spiceworks.com/t/eset-license-update-clients-no-longer-updating/202216/5","author":{"@type":"Person","name":"joereiber","url":"https://community.spiceworks.com/u/joereiber"}},{"@type":"Answer","text":"
Uhm, so besides licenses not being deployed, you cannot get your clients to reach server… I misread your post. Can you verify the port of ERA server (2221 by default) is ok and listening? Can you try from client side to connect to this port using telnet?<\/p>","upvoteCount":0,"datePublished":"2013-03-22T19:41:32.000Z","url":"https://community.spiceworks.com/t/eset-license-update-clients-no-longer-updating/202216/6","author":{"@type":"Person","name":"krzysztofradomski","url":"https://community.spiceworks.com/u/krzysztofradomski"}},{"@type":"Answer","text":"
What can you see in Clients pane of ERAC? Do you see your machines ‘Last connected’ status equal to the time of new license update on ERA Server? I’m also wondering - is new license valid from current or past time, or is it valid starting with the future time? Perhaps you have removed your present license replacing it with the new one, clients got the change and now cannot connect because new license is not yet valid and old one is removed…<\/p>","upvoteCount":0,"datePublished":"2013-03-22T19:46:59.000Z","url":"https://community.spiceworks.com/t/eset-license-update-clients-no-longer-updating/202216/7","author":{"@type":"Person","name":"krzysztofradomski","url":"https://community.spiceworks.com/u/krzysztofradomski"}},{"@type":"Answer","text":"
Does ‘Event log’ pane say anything useful?<\/p>","upvoteCount":0,"datePublished":"2013-03-22T19:50:01.000Z","url":"https://community.spiceworks.com/t/eset-license-update-clients-no-longer-updating/202216/8","author":{"@type":"Person","name":"krzysztofradomski","url":"https://community.spiceworks.com/u/krzysztofradomski"}},{"@type":"Answer","text":"\n\n
<\/div>\n
Krizz:<\/div>\n
\nWhat can you see in Clients pane of ERAC? Do you see your machines ‘Last connected’ status equal to the time of new license update on ERA Server? I’m also wondering - is new license valid from current or past time, or is it valid starting with the future time? Perhaps you have removed your present license replacing it with the new one, clients got the change and now cannot connect because new license is not yet valid and old one is removed…<\/p>\n<\/blockquote>\n<\/aside>\n
In the Clients pane of ERAC it shows last connected right around the time of expiration/renewal. The license expired before we renewed it, if that affects it at all (Thanks, corporate…) As far as I can tell, the old one is completely gone, it was only showing one key in there when I got to it. It’s been down for three days and somehow has fallen on me to take care of. the default port is being used(2221)<\/p>\n
I apologize for such a late response, was at the end of the work day(I’m an hourly peon). I cannot give you more information until tomorrow morning, when I return to work. I will respond with more information as soon as I can get it to you.<\/p>","upvoteCount":0,"datePublished":"2013-03-23T00:31:35.000Z","url":"https://community.spiceworks.com/t/eset-license-update-clients-no-longer-updating/202216/9","author":{"@type":"Person","name":"joereiber","url":"https://community.spiceworks.com/u/joereiber"}},{"@type":"Answer","text":"
Event Log pane says nothing of any of this, except maybe that the last events happened around the same time we switched the license over. I cannot telnet into port 2221, though I’ve no experience with telnet and I’m going to assume its not setup (If you do set it up?) on the ESET server.<\/p>","upvoteCount":0,"datePublished":"2013-03-23T09:12:20.000Z","url":"https://community.spiceworks.com/t/eset-license-update-clients-no-longer-updating/202216/10","author":{"@type":"Person","name":"joereiber","url":"https://community.spiceworks.com/u/joereiber"}},{"@type":"Answer","text":"
I cannot telnet into any of the ports my ESET server uses (all of the defaults) I just get a connection failed.<\/p>","upvoteCount":0,"datePublished":"2013-03-23T10:59:30.000Z","url":"https://community.spiceworks.com/t/eset-license-update-clients-no-longer-updating/202216/12","author":{"@type":"Person","name":"joereiber","url":"https://community.spiceworks.com/u/joereiber"}},{"@type":"Answer","text":"
Punched a couple of holes in my firewall for now, just direct port exceptions, and everything seems to be working correctly. Is there a more correct way to fix this? I’m not sure what the setup was before but why would the firewall start doing this now instead of about three or four years ago who we purchased ESET?<\/p>","upvoteCount":0,"datePublished":"2013-03-23T11:11:33.000Z","url":"https://community.spiceworks.com/t/eset-license-update-clients-no-longer-updating/202216/13","author":{"@type":"Person","name":"joereiber","url":"https://community.spiceworks.com/u/joereiber"}},{"@type":"Answer","text":"\n\n
<\/div>\n
FiyaFly:<\/div>\n
\nPunched a couple of holes in my firewall for now, just direct port exceptions, and everything seems to be working correctly. Is there a more correct way to fix this?<\/p>\n<\/blockquote>\n<\/aside>\n
No, if the firewall was blocking the port, that’s the culprit.<\/p>\n
FiyaFly wrote:<\/p>\n
\nI’m not sure what the setup was before but why would the firewall start doing this now instead of about three or four years ago who we purchased ESET?<\/p>\n<\/blockquote>\n
Haven’t you been updating your ERA Server at the occasion of license update? Perhaps it was listening on different ports. But it’s an assumption hard to believe. Maybe someone else was toying around with firewall? I cannot tell.<\/p>","upvoteCount":0,"datePublished":"2013-03-23T11:17:08.000Z","url":"https://community.spiceworks.com/t/eset-license-update-clients-no-longer-updating/202216/14","author":{"@type":"Person","name":"krzysztofradomski","url":"https://community.spiceworks.com/u/krzysztofradomski"}},{"@type":"Answer","text":"
Well, then I guess that’s that. Thank you very much for the help! I am a novice when it comes to servers at all. I’m the general tech. The ESET server is not my responsibility, it’s not even in my building. But that’s another rant for another thread.<\/p>\n
Thanks again!<\/p>","upvoteCount":1,"datePublished":"2013-03-23T11:23:37.000Z","url":"https://community.spiceworks.com/t/eset-license-update-clients-no-longer-updating/202216/15","author":{"@type":"Person","name":"joereiber","url":"https://community.spiceworks.com/u/joereiber"}}]}}
From what I know, the only thing that was changed with the license, which had already expired. The licence was updated, but none of the clients have gotten updates since. The server can update just fine and the mirror is properly configured (I’ve quadruple checked). I can ping the server computer from the client and vice versa. the ESET RA service has been restarted a couple times since this and I have been told that the computer it resides on has been restarted as well. I have checked the uniformity of the settings on both the server and client end to match properly. I have attempted to push an update to my computer from the server to just sit at the message ‘Waiting’ for over 2 hours. I am out of ideas.
If you need more information, please do not hesitate to ask.
3 Spice ups
The obvious question is, do your clients have the new license deployed? Can you see it in advanced setting/kernel/settings/license keys? If not, did you deployed the key in your default policy applied to network machines?
If I remember well, uploading a license key to the server is not enough - you have to deploy it explicitly in the policy manager.
That is infact something I noticed was completely blank. I could find no settings for pushing the license to the clients. What do I have to do to fix this?
Sorry, I edited my first post. Use policy manager.
I put the proper license where it needs to be in the policy manager and ensured that all of the client are attached to that policy. How long might that take to trickle down? I’m still getting “Could not connect to server” from the client.
Uhm, so besides licenses not being deployed, you cannot get your clients to reach server… I misread your post. Can you verify the port of ERA server (2221 by default) is ok and listening? Can you try from client side to connect to this port using telnet?
What can you see in Clients pane of ERAC? Do you see your machines ‘Last connected’ status equal to the time of new license update on ERA Server? I’m also wondering - is new license valid from current or past time, or is it valid starting with the future time? Perhaps you have removed your present license replacing it with the new one, clients got the change and now cannot connect because new license is not yet valid and old one is removed…
Does ‘Event log’ pane say anything useful?
joereiber
March 23, 2013, 12:31am
9
Krizz:
What can you see in Clients pane of ERAC? Do you see your machines ‘Last connected’ status equal to the time of new license update on ERA Server? I’m also wondering - is new license valid from current or past time, or is it valid starting with the future time? Perhaps you have removed your present license replacing it with the new one, clients got the change and now cannot connect because new license is not yet valid and old one is removed…
In the Clients pane of ERAC it shows last connected right around the time of expiration/renewal. The license expired before we renewed it, if that affects it at all (Thanks, corporate…) As far as I can tell, the old one is completely gone, it was only showing one key in there when I got to it. It’s been down for three days and somehow has fallen on me to take care of. the default port is being used(2221)
I apologize for such a late response, was at the end of the work day(I’m an hourly peon). I cannot give you more information until tomorrow morning, when I return to work. I will respond with more information as soon as I can get it to you.
joereiber
March 23, 2013, 9:12am
10
Event Log pane says nothing of any of this, except maybe that the last events happened around the same time we switched the license over. I cannot telnet into port 2221, though I’ve no experience with telnet and I’m going to assume its not setup (If you do set it up?) on the ESET server.
Sorry for providing bad information - default port ERA Server is listening on is 2222 for clients reporting/synchronization. If you’re mirroring updates on your ERA Server, port 2221 also should be open for clients connections, but it’s not related to the problem. So instead of 2221, try telnetting to port 2222:
telnet era_server 2222
If screen goes blank, it means the port is open and clients should be able to report their status to server. Do it from client machine - on WinXP telnet client is installed by default, but if it’s Win7, you have to install it first via Programs and Functions/Enable Windows Components (thanks Microsoft).
1 Spice up
joereiber
March 23, 2013, 10:59am
12
I cannot telnet into any of the ports my ESET server uses (all of the defaults) I just get a connection failed.
joereiber
March 23, 2013, 11:11am
13
Punched a couple of holes in my firewall for now, just direct port exceptions, and everything seems to be working correctly. Is there a more correct way to fix this? I’m not sure what the setup was before but why would the firewall start doing this now instead of about three or four years ago who we purchased ESET?
No, if the firewall was blocking the port, that’s the culprit.
FiyaFly wrote:
I’m not sure what the setup was before but why would the firewall start doing this now instead of about three or four years ago who we purchased ESET?
Haven’t you been updating your ERA Server at the occasion of license update? Perhaps it was listening on different ports. But it’s an assumption hard to believe. Maybe someone else was toying around with firewall? I cannot tell.
joereiber
March 23, 2013, 11:23am
15
Well, then I guess that’s that. Thank you very much for the help! I am a novice when it comes to servers at all. I’m the general tech. The ESET server is not my responsibility, it’s not even in my building. But that’s another rant for another thread.
Thanks again!
1 Spice up
