Off topic but might be useful if you use Kaspersky Security

A moderator took your advice cowboy and locked the thread, but I'm a moderator as well and so have unlocked it. I agree the discussion has run it's course but I don't support locking threads that are active and only a few days old. I don't know which mod locked this thread but unless there was something nasty going on and there wasn't then their judgement was flawed. If people want to post to this it is up to them and not us to truncate the conversation. Like all threads it will die a natural death.

The IP she posted is a Private address. All 192.168.x.x addresses are in the Private domain and can't be reached from the internet. They are for home/office networks. The computer that I am posting this reply from has an IP of 192.168.1.100. My router is 192.168.1.1 and my Cable modem is 192.168.100.1.

The AT&T/Bellsouth modem/router combo box I use to use, when I was using Bellsouth/AT&T as an internet provider, used 192.168.1.254 as the router sections IP address.

What is a Private IP Address?

https://www.google.com/search?q=Private+IP+addresses&oq=Private+IP+addresses&aqs=chrome.0.69i59.6272j0j9&sourceid=chrome…

Hi,

No until recently I just used Windows Defender and didn't have any commercial anti virus software. I switched to Kaspersky a few months ago after I started moderating here on the Adobe forum. I don't know if you realise, but Adobe goes to lengths to protect the people who come to these forums. The boards JIVE software scans most of the incoming input but anything it is not sure about gets put into a queue for a human to moderate. If the moderator gets it right you don't see harmful links, spam, potential fraudsters, obscene language- that sort of thing. However, this does mean the moderator needs to check out links and maybe some check downloads-must admit I don't do the latter though. You therefore need sound antivirus software better than the free stuff that comes with the OS.

I discovered last week that I could not access my router through any browser to change its configuration. At first I thought the web server in the router had failed , but quickly realised Kaspersky was blocking access to it's IP address. I did the obvious and uninstalled Kaspersky and straight away my router was accessible. I then put Kaspersky back and the router was inaccessible. Knowing what was wrong I went to the Kaspersky Labs forum online and found just one reference to this from an OP-that OP had contacted the paid for Kaspersky technical support and been told it was a bug in the latest version of KIS2017 and there was no plan to fix it. In effect the fix will be to buy KIS2018 when it comes out in late Autumn. For now downgrading to KIS2016 will fix it, but unless you regularly need to access your router configuration that is hardly worth it. As this is an acknowledged problem I therefore decided to tell Amazon customers about it through a validated buyer review, but for some reason Amazon didn't want their customers to know. You can't talk to anyone at Amazon , it seems to be totally automated. So in order to make information on this problem searchable online I posted here. Google spiders the Adobe forums and so in a few days anyone else with this problem will now be able to find the solution. In some ways posting here is more effective than posting a review at Amazon as Amazon blocks Google bots indexing their reviews and so they are not easily searchable. The review I posted was fair and not particularly negative about Kaspersky , but took five or six minutes to write and I felt Amazon wasted my time maybe to prevent sales of the product being affected-Kaspersky is a best seller. It's nothing to me but I won't give feedback on anything I buy from them in the future or believe the reviews from others on their website.

Finally I disagree that Adobe would allow CC customers to wait a year over something that can be easily fixed. Sure Creative Cloud has bugs that aren't fixed, but most of those require a radical rewrite of some of the apps to fix them. Kaspersky could fix the issue I identified simply by telling it's software not to block access to IP: 192.168.1.254 through a 'rule' - a simple patch would do that but they don't want to spend any money it seems. Well it's their reputation that gets damaged!

Thanks for that. I do some moderation here at Adobe so am aware of the kind of thing that gets rejected, but for the life of me couldn't see anything wrong with those comments. I'm in England so maybe the policy at Amazon UK is different to the US, but I won't bother to review anything at Amazon again. I now can't but help think Amazon censors fact based adverse comments to avoid putting purchasers off. They have to let some through, but I wouldn't put it past them to write mildly adverse comments themselves just to avoid generating suspicion.

Anyhow they lost out in the end as I was going to buy 6 monitors for my group at work yesterday and placed the £3000 order with another company instead-Amazon is never the only game in town.