"Compilation Of Tutorials, Guides, Tips & Updates"

[thedeparted]

but when i use a proxy for download in IDM it discover that i use a fack srial, Except that all going fin

[dcs18]

@ mara-

A firewall has scant respect for humans' division of IPs into - update server, expiration, etc., etc.

Why I chose to block / allow an IP is a matter of trial-n-error - absolutely irrelevant, to others.

[rudrax]

@rudrax

http://myip.ms/info/whois/38.90.226.40

Cheers ;)

The only information that I can get from your link is the IP belongs to ESET which I already know, anyway. I could not find whether it's a update server or activation server.

[Cortana]

what about the following IPs ?

[Zarko]

@dcs18

You still didn't answer my question. If this loophole I mentioned is true, why did you choose to block um13.eset.com (38.90.226.40) which is update server, not expiration server?

@rudrax

http://myip.ms/info/whois/38.90.226.40

Cheers ;)

I guess he made mistake with that IP, and now tell us why you wanna know so much why he did that ?

Cheers ;)

[steven36]

IP Address : 38.90.226.40

But how this tells you that it's an update server not an activation server?

Why you keep asking this? Update ips are pubic knowledge :lol:

http://kb.eset.com/esetkb/index?page=content&id=SOLN332&locale=en_US

um11.eset.com - 91.228.166.88

um13.eset.com - 38.90.226.40

um12.eset.com - 91.228.167.170

To see the expiration date:

91.228.165.69

212.73.202.109

212.73.202.103

91.228.165.70

[rudrax]

IP Address : 38.90.226.40

But how this tells you that it's an update server not an activation server?

Why you keep asking this? Update ips are pubic knowledge :lol:

http://kb.eset.com/esetkb/index?page=content&id=SOLN332&locale=en_US

um11.eset.com - 91.228.166.88

um13.eset.com - 38.90.226.40

um12.eset.com - 91.228.167.170

Oops, sounds like I recently shaved 'em. :tehe:

And, why the hell ESET would expose their internal classified information to the public? When they say that those IPs are required for receiving updates, among them there exists one or more IPs of the activation servers too. It may be 38.90.226.40.

[steven36]

When they say that those IPs are required for receiving updates, among them there exists one or more IPs of the activation servers too. It may be 38.90.226.40.

regardless of what ips they use to check they could be required you remember when eset servers got overloaded not long ago right?

the more update ips you block the less chance of getting and update if they ever get overloaded again .

[dcs18]

@ one and all

Kindly do not try to allow the IP (38.90.226.40) that mara- keeps on inquiring about.

I have quite rightly designated that IP (38.90.226.40) to be blocked - you can kiss your activation good-bye if that IP is not blocked.

[steven36]

@ one and all

Kindly do not try to allow the IP (38.90.226.40) that mara- keeps on inquiring about.

I have quite rightly designated that IP (38.90.226.40) to be blocked - you can kiss your activation good-bye if that IP is not blocked.

Funny i don't have it blocked and mine is still activated , yesterday after fooling with rudrax telling me to block this and block that i thought i had broke it I ended up having to clear update catch to get updates again so i put it back the way i had it and left it alone with the 2 org block ips and the allow ips . If stops working ill just use a new key. :lol:

[dcs18]

@ one and all

Kindly do not try to allow the IP (38.90.226.40) that mara- keeps on inquiring about.

I have quite rightly designated that IP (38.90.226.40) to be blocked - you can kiss your activation good-bye if that IP is not blocked.

Funny i don't have it blocked and mine is still activated , yesterday after fooling with rudrax telling me to block this and block that i though i had broke it I ended up having to clear update catch to get updates again so i put it back the way i had it and left it alone with the 2 org block ips and the allow ips . If stops working ill just use a new key. :lol:

Try allowing that IP - you won't find it funny, any more.

[rudrax]

what about the following IPs ?

These IPs will be blocked if you follow the implementation provided at post #1492. This implementation blocks (almost) all ESET IPs including those 5 block IPs provided by dcs18 excluding those 12 allow IPs provided by dcs18.

[dcs18]

Guys, please follow the guide, word-for-word - don't try to fool around with cheap theories.

We are dealing with ESET - it isn't monkey-business.

[steven36]

@ one and all

Kindly do not try to allow the IP (38.90.226.40) that mara- keeps on inquiring about.

I have quite rightly designated that IP (38.90.226.40) to be blocked - you can kiss your activation good-bye if that IP is not blocked.

Funny i don't have it blocked and mine is still activated , yesterday after fooling with rudrax telling me to block this and block that i though i had broke it I ended up having to clear update catch to get updates again so i put it back the way i had it and left it alone with the 2 org block ips and the allow ips . If stops working ill just use a new key. :lol:

Try allowing that IP - you won't find it funny, any more.

well Im not going to do that lol I guess not having it in allow must be doing its job . mine is updating with a diffrent ip than that.

[dcs18]

Please also understand that the firewall method uses the very latest update servers and rewards Users with priority updates - what this means is that in times of servers over-loads on ESET's side, Users of the firewall trick shall not be made to wait for their Virus signature database updates.

[mara-]

Trial and error, dcs18? So basically, you don't know why you blocked this IP. This whole theory is based on that Eset can't contact expiration server, but you blocked update server and you don't know to explain why.

Cheers ;)

[steven36]

I don't understand it ether, did it call out to someone you know and expire there key or did it expire yours? so far you told everyone to block 3 update servers.

You started out with just blocking with blocking the 2 activation ips . If those 3 update ips can expire my keys it means at anytime they could expire me on the update server Im using. Witch this is not the case so far . :)

[dcs18]

Trial and error, dcs18?

Yes, mara- you are right, trial-n-error also known commonly as beta-testing - the very same trial-n-error with which I beta-tested the box, mara- fix . . . . . . . . . for you.

So basically, you don't know why you blocked this IP. This whole theory is based on that Eset can't contact expiration server, but you blocked update server and you don't know to explain why.

Cheers ;)

Yes, I know why I blocked that IP - but, do not see the reason for disclosing it . . . . . . . . . did you divulge the underlying code of your fix? Did I ever ask you for the same?

[mara-]

Trial and error is not the same as beta testing. Also, divulging code and method is not the same. Everyone knows how box, mara- fix works, but you feel like you need to keep a secret why you blocked an IP. And sharing is the point of this forum. Also, please don't insult me by posting image of a post by that poor soul.

Cheers ;)

[BALTAGY]

with my respect for you both this link have update servers ips

http://kb.eset.com/esetkb/index?page=content&id=SOLN332

for me i think update servers are responsible about username expiration check and also mara-fix i tried it and it didn't update modules to last version and i think it's not mara-fix problem, i think trial servers don't update modules fast as normal servers so for me i use Tnod for years now :)

[dcs18]

@ mara-

What you are preaching on this thread - that must be beta-testing, right?

If you don't relish being insulted, just stop behaving like my mother-in-law - I am not accountable to you or to anyone else. Don't allow yourself to feel so shafted simply because someone has chosen not to disclose what you are so anxious to know (everybody has their own valid reasons.)

As for sharing, all that is required is always available in updated form, at the tutorial - those who feel like floating their own theories are free to allow that IP (38.90.226.40) to find out the difference between trial-n-error and beta-testing.

[steven36]

I just allowed 38.90.226.40 and rolled back updates 2 times and it updated with this IP 38.90.226.40 2 times and nothing happen :unsure: Only thing that happens when I don't allow it forces it to use another update server . still works so far with or without . ;)

[steven36]

The thing is if your firewall was working right to began with by allowing only the ips on that list.. it should never called out 38.90.226.40 to began with even though didn't expire my key .. If it called that out and its not on your list of allowed ips your firewall is leaking and you need to find out why . Me just using windows firewall I'm not having this problem .

[dcs18]

Already one update server had to be blocked (or maybe it shouldn't, author does not know what he is doing, since he actually didn't figure this out), I wonder how long before all have to be blocked.

Cheers ;)

but now I'm sure you don't have a clue what are you doing here.

You seem to know everything - don't you?

In which program do you create the rules?

BTW, how to discover IP's if they ever change?

Cheers ;)

you feel like you need to keep a secret why you blocked an IP

You don't like my secrets?

Unfortunately, I won't share it here for the moment, to prevent stealing of my idea.

[Mr Orus]

Note Warning!

Prohibited offensive language:

- It is not allowed foul language, or face discussions or writing offensive phrases, controversy, defamatory, against any party member the forum.

- The activity of moderation relies on the rules set out in paragraphs. Community Guidelines

* Member of moderate to persistent behavior contrary to the rules of this forum will be warned or banned on the first instance.