Redirects via "jupk.com"
 

For info only now.
I have just recovered from a couple of days where by calls to such innocent places as GoogleUK finished up at some porn site or other unwanted locales.
It turned out that this 'Bug' had altered the DNS setting in Network Connections
The cure was quite simple.
'Settings/Control panel/Network Connections/'Right click' Internet conection/ Properties/Networking/ Double click TCP/IP and ensure that "Obtain DNS Server Address Automatically" IS SELECTED
Hope his make sense to anyone who may need it.

TJ,

I assume that the DNS server address(es) had been altered to a specific IP address - I don't suppose you recorded it, by any chance?

This is what a ping reveals:

dns.jupk.com [209.85.51.47]

SD

Saab.
The exact numbers I cannot recall, but "who is" shows it as part of the RIPE Network in Amsterdam.
They were in the order of 85.xx.xx.xx
Terry.

Thank God for Pprune!

I've been getting this problem / am in the middle of trying to sort it out. Assuming it's the same thing - a pale blue screen with 'find something interesting' in the top left corner and a bunch of links, many adult, in nature. And a pic of of a pretty, clothed female.

The IP addresses in the TCP/IP boxes are 85 255 114 20 and 85 255 112 175. Is there a specific way to block these addresses then?

Both addresses resolve to

inetnum: 85.255.112.0 - 85.255.127.255
netname: inhoster
descr: Inhoster hosting company
descr: OOO Inhoster, Poltavskij Shliax 24, Kharkiv, 61000, Ukraine
remarks: -----------------------------------
remarks: Abuse notifications to: http://img.domaintools.com/email.pgi...1eebee6653ee5a
remarks: Network problems to: http://img.domaintools.com/email.pgi...dfc3e22d578916
remarks: Peering requests to: http://img.domaintools.com/email.pgi...9d994d8c1a3c17
remarks: -----------------------------------
country: UA
org: ORG-EST1-RIPE
admin-c: AK4026-RIPE
tech-c: AK4026-RIPE
tech-c: FWHS1-RIPE
status: ASSIGNED PI
mnt-by: RIPE-NCC-HM-PI-MNT
mnt-lower: RIPE-NCC-HM-PI-MNT
mnt-by: RECIT-MNT
mnt-routes: RECIT-MNT
mnt-domains: RECIT-MNT
mnt-by: DAV-MNT
mnt-routes: DAV-MNT
mnt-domains: DAV-MNT
source: RIPE # Filtered

organisation: ORG-EST1-RIPE
org-name: INHOSTER
org-type: NON-REGISTRY
remarks: *************************************
remarks: * Abuse contacts: http://img.domaintools.com/email.pgi...1eebee6653ee5a *
remarks: *************************************
address: OOO Inhoster
address: Poltavskij Shliax 24, Xarkov,
address: 61000, Ukraine
phone: +38 066 4633621
e-mail: http://img.domaintools.com/email.pgi...14580ae3b1f2a8
admin-c: AK4026-RIPE
tech-c: AK4026-RIPE
mnt-ref: DAV-MNT
mnt-by: DAV-MNT
source: RIPE # Filtered

person: Andrei Kislizin
address: OOO Inhoster,
address: ul.Antonova 5, Kiev,
address: 03186, Ukraine
phone: +38 044 2404332
nic-hdl: AK4026-RIPE
source: RIPE # Filtered

person: Fast Web Hosting Support
address: 01110, Ukraine, Kiev, 20 , Solomenskaya street. room 201.
address: UA
phone: +35 79 91 17 759
e-mail: http://img.domaintools.com/email.pgi...bba16cc8e3f162
nic-hdl: FWHS1-RIPE
source: RIPE # Filtered

Chocolate teapot territory!

Here's an interesting piece from Spyware Confidential.

SD

In Win XP, there is no obvious and easy way. Windows built-in firewall doesn't allow this sort of IP address filtering - nor does OneCare (say that over and over, you end up saying wa*ker!).

I digress.

Some other software firewalls may allow you to block a source / destination address or address range. I don't know.

Hardware firewalls may allow you to do it - my Netgear firewall doesn't allow IP address ranges (just domain names) to be blocked, but I simply set up a static route, so that the route to 85.255.112.0/20 (the /20 means a 20-bit subnet mask, i.e. 255.255.240.0) is directed by the firewall BACK to my own computer. Similarly for 69.50.160.0/19.

Crude, but effective!

SD

"In Win XP, there is no obvious and easy way."

Actually there is - That's what your HOSTS file is there for (not strictly speaking, but you can use it for that).

Rather than me explaining, pop over to http://accs-net.com/hosts/ and read all about it. It ain't difficult and doesn't cost anything.

Use your HOSTS file (which is built into Windows [and Linux]) in combination with eDexter and/or DNSKong and Hostsman from abelhadigital - http://pwp.netcabo.pt/0413933601/abe.../hostsman.html - and you're all set.

And it's all free :ok:

Mac,

You are answering the wrong question - the question was "How can I block access to this range of IP addresses", not how can I manage name resolution.

The HOSTS file manages translation of host names into IP addresses, NOTHING ELSE!

It cannot be used to block access to IP addresses BECAUSE IF YOU KNOW THE IP ADDRESS IT IS NOT EVEN CONSULTED!!

With a proper firewall it is simple to write rules to block traffic to / from specific addresses or whole blocks of addresses as in this case; however, Windows isn't a firewall (understatement of the century), and most of the home WAP/Switch/Firewalls don't allow this level of customisation. I'm sure that there are some that allow this - I'm also sure that some of the software firewalls that run on Windows can do this.

I believe that you could write static routes into Windows networking via the command line, and it would be simple to put this into a script that runs whenever you boot, but with more than one device on the network, it makes more sense (and is easier) to put it on the firewall.

SD

Oooops! You're right.

What'll teach me to engage brain before speaking :ouch:

As you say, the firewall is the place to block access to specific or ranges of IP addresses.

I use zone alarm which allows blocking of specific IP addresses and/or ranges of addresses. :)

Which version of ZA is that please?

It's the free version from www.zonelabs.com

info gives

ZoneAlarm version:6.5.737.000
TrueVector version:6.5.737.000
Driver version:6.5.737.000