Jump to content

"Compilation Of Tutorials, Guides, Tips & Updates"


dcs18

Recommended Posts

  • Replies 7.3k
  • Views 1.1m
  • Created
  • Last Reply
21 hours ago, dcs18 said:

Undertaker,

 

Your RocketMan avatar is waiting, for you. 6HUIPBa.gif

Done, thanx ;)

 

BTW I suggest the babaji avatar for you, goes with the personality.  :P

Link to comment
Share on other sites


On 6/6/2017 at 2:10 PM, Undertaker said:

IPSec, Hosts, IP Block not working :(

Preliminary test result shows I was wrong about the above. IPSec and hosts do work provided you configure them correctly(which I was missing earlier).Testing in progress... :thumbsup:

Link to comment
Share on other sites


wsa.png At first glance I suddenly thought @dcs18 has changed his name :P,  later the COLOR & Member Title corrected me :lol::D . . 

Link to comment
Share on other sites


23 minutes ago, Undertaker said:

Preliminary test result shows I was wrong about the above. IPSec and hosts do work provided you configure them correctly(which I was missing earlier).Testing in progress... :thumbsup:

Want to test my new implementation?

Link to comment
Share on other sites


yes , it still works ( FWB/IPSEC blocking method.) till now.

 

All you have to do after doing the blocking method is do some checking/pinging idm sites if it works. Here are some few examples, 

Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserv

PS C:\WINDOWS\system32> PING INTERNETDOWNLOADMANAGER.COM

Pinging INTERNETDOWNLOADMANAGER.COM [169.55.40.5] with 32 b
General failure.
General failure.
General failure.
General failure.

Ping statistics for 169.55.40.5:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
PS C:\WINDOWS\system32> PING TONEC.COM

Pinging TONEC.COM [50.22.78.28] with 32 bytes of data:
General failure.
General failure.
General failure.
General failure.

Ping statistics for 50.22.78.28:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
PS C:\WINDOWS\system32> PING REGISTERIDM.COM

Pinging REGISTERIDM.COM [169.55.40.5] with 32 bytes of data
General failure.
General failure.
General failure.
General failure.

Ping statistics for 169.55.40.5:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
PS C:\WINDOWS\system32> PING TELEMETRY.INTERNETDOWNLOADMANA

Pinging TELEMETRY.INTERNETDOWNLOADMANAGER.COM [169.55.0.224
General failure.
General failure.
General failure.
General failure.

Ping statistics for 169.55.0.224:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

then you can do a clean-up - register idm as usual.

the key/license checking idm url i posted years back.  dcs18 has it also.

 

if using random keys based on idm algorithm, you will be redirected to errorneous site.

if using valid retail keys , you get the latest update automatically downloaded

if you use retail blocklisted keys, you get access denied.

 

if you have a random keygen or better a valid retail key ,you can register it easily but true make sure you already block the idm license servers sites so you cn reused it .

 

Mdata  is vpkey 3.5+ protected in retail keys vs trial,  you can see the difference when using reg thrash finder, i find this very useful even detecting thrash fake clsid during testing of using fake keys which i just deleted. 

 

my thoughts.

 

 

 

 

Link to comment
Share on other sites


"Blocking IDM With The (IP + DNS) Combination"

(The tutorial is being tested, please do not use it right now — shall announce on my Status Update, once it's fully ready)

 

Link to comment
Share on other sites


2 hours ago, dcs18 said:

Want to test my new implementation?

I'm always up for Beta-Testing :P

 

1 hour ago, dcs18 said:

"Blocking IDM With The (IP + DNS) Combination"

After following the steps to the letter, my WFC is still being bypassed. It was able to check for registration as well as update.

Tell me what info you need from my side. :rolleyes:

Link to comment
Share on other sites


8 minutes ago, dcs18 said:

Yes . . . . . . now, it will check for updates — why do feel it bypasses WFC? yXZVmpE.gif

It's in the allowed log rather than blocked connection logs and once it's able to successfully bypass WFC, it is able to ping from cmd also.

Link to comment
Share on other sites


You might want to disable any other protection such as Adguard and retry — deactivation is no longer fatal (thanks to this.)

Link to comment
Share on other sites


1 minute ago, dcs18 said:

You might want to disable any other protection such as Adguard and retry — deactivation is no longer fatal (thanks to this.)

Will try that but Adguard only acts when all other things -IPSec, hosts, WFC have allowed it, it is but the last stage of protection. Also, Adguard is limited to monitoring IDM only, and hence should have no effect on CMD as such. But will try and reply.

Link to comment
Share on other sites


Nah, nah — just disregard the logs (there's a reverse DNS in play . . . . . . now.) ;)

Link to comment
Share on other sites


Results after disabling Adguard:-

 

Spoiler

https://i.imgur.com/YHBp4sp.png

 

1) The IPSec rules are in place

2) Confirmation that IPSec rules are working fine.

3) Opened IDM and checked for update.

4) WFC log shows the update connection has been allowed though updated block rule was in place

5) After WFC bypass, I checked the ping for same domain and the result is in front of you.

 

Spoiler

https://i.imgur.com/CB1DDxm.png

 

After IDM restart, fake serial popup comes up.

 

Link to comment
Share on other sites


Close IDM and switch-off internet connection (disable just the IDM block rule in WFC) and run IDM to re-register with a different serial — if registration accepted, enable the disabled IDM rule and then switch-on the internet connection.

Link to comment
Share on other sites


4 minutes ago, dcs18 said:

Close IDM and switch-off internet connection (disable just the IDM block rule in WFC) and run IDM to re-register with a different serial — if registration accepted, enable the disabled IDM rule and then switch-on the internet connection.

Did exactly as instructed, changed the serial as well but after enabling rule and then the net connection, opened IDM and found it again managed to bypass WFC, checks for update and registration and when restarted, gives fake serial.

Link to comment
Share on other sites


Close IDM and post a full-screen screenshot of your RTKF, after switching to 32-bit Mode.

Link to comment
Share on other sites


29 minutes ago, dcs18 said:

Wanna TeamView? B)

I don't have Teamviewer now, but I could get it up in 5-10 mins, if you can wait?

 

 

Edit: Done

Link to comment
Share on other sites


Sure, first just follow these instructions:—

  1. Backup [HKEY_CURRENT_USER\Software\DownloadManager]
  2. Ensure you have the latest IDM installer ready
  3. Uninstall your blacklisted copy
  4. Reboot
  5. Clean up the debris
  6. Reboot
  7. Do NOT install IDM
  8. Set WFC with the Block rule for the 31 IDM IPs (and Allow rule, as well)

 

Mark me a PM with your TeamViewer User ID and Password and let me know once you're ready for the session.

Link to comment
Share on other sites


7 hours ago, IamBidyuT said:

wsa.png At first glance I suddenly thought @dcs18 has changed his name :P,  later the COLOR & Member Title corrected me :lol::D . . 

 

Off Topic:

What capture tool did you use to get teared borders like that?

Or simple phostoshoped it?

Thx

 

Link to comment
Share on other sites


On 6/10/2017 at 2:08 AM, A.lemane said:

i think i found a solution but ill wait until i test it more ^^ 

guys this worked for me until now as it continue to 

 

anyway i thought that its worth mentioning now that it lasted all this time 

 

and this is what i did (require a 3rd party application to be installed & always running one that most of us already have & like)

 

 

Spoiler

tUB7tPtAQ-Oo4VEGQODr6w.png

 

Spoiler

50.22.78.28 - 50.22.78.28
50.22.78.29 - 50.22.78.29
50.22.78.31 - 50.22.78.31
50.97.41.98 - 50.97.41.98
50.97.82.44 - 50.97.82.44
69.41.163.49 - 69.41.163.49
69.41.163.149 - 69.41.163.149
75.125.34.148 - 75.125.34.148
75.125.34.157 - 75.125.34.157
169.55.0.224 - 169.55.0.224
169.55.40.5 - 169.55.40.5
173.255.137.80 - 173.255.137.80
173.255.134.84 - 173.255.134.84
174.127.73.80 - 174.127.73.80
174.127.73.85 - 174.127.73.85
174.133.70.98 - 174.133.70.98
174.133.70.101 - 174.133.70.101
184.173.149.184 - 184.173.149.184
184.173.188.104 - 184.173.188.104
184.173.188.106 - 184.173.188.106
184.173.188.107 - 184.173.188.107
185.80.220.22 - 185.80.220.22
185.80.221.18 - 185.80.221.18
202.134.64.74 - 202.134.64.74
207.44.199.16 - 207.44.199.16
207.44.199.159 - 207.44.199.159
207.44.199.165 - 207.44.199.165

 

 

and voila ^^

please test it guys and share & confirm the results ^^

 

edit : this is the full tuto 

 

 

 

Link to comment
Share on other sites


  • Matrix locked this topic

Archived

This topic is now archived and is closed to further replies.

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...