Jump to content

megentry1

Members
  • Posts

    10
  • Joined

  • Last visited

Everything posted by megentry1

  1. Well--I think I fixed it. It wasn't just having to get rid of the homenet.dat file--it was also getting rid of the other 2 (basically the same 3 files I identified in the original post). Doing that cleared the field AND allowed a new network scan to be conducted. And doing that gave me objects that reflect reality. So, in summary, all 3 homenet-related files need to be removed or renamed while in Safe Mode. Thanks for the assistance. Regards, Mike Gentry
  2. Thanks, Marcos.... Looks like I need to contact support and raise a ticket. Removing the file as you suggested while in Safe Mode, wiped the field slick, alright, BUT, now the "Scan Your Network" button is greyed out, now, so the ability to generate a new scan result appears to be non-existent.
  3. It's been a long while since I've posted to this forum (last time was 2014), as I've not really had many issues, however, I am having one now, so here I am. So, the Connected Home Monitor is sort of cool, but it has been around now for several releases, and I still see some quirks with it--and this time, I am finding I cannot do something, specific and it is annoying the out of me. What started this was the procurement of a new router. I upgraded from a Netgear WNDR4500 to a Nighthawk AC2300 (which appears as R7000P in the Monitor). And my first attempt at the cut-over did not go as well as expected (i.e., it flat-out failed, and it was my fault), and I didn't have the time to futz with it, so I re-cabled my old router for the evening. The next night, however, I successfully swapped out the routers. Yea! However, when I ran the Connected Home Monitor, I was dismayed to see multiple R7000P entries, as well as the old WNDR4500 entry. Worse, I cannot get rid of the bogus, phantom R700P entries to correct the (Sonar) "field". In other words, selecting some of the R7000P entries just causes the page to blink, as opposed to being taken to the details frame. All of the other objects can be selected (but only when in the Sonar view) and get necessary details. Selecting the List view allows no further drill down or actions. And I consider that to be a problem. I should be able to do stuff in List view. Why else have it? Additionally, I also had a beef with the Editable name fields in the Details view for the longest time, too, because I stupidly was clicking on the little pencil "icon", which isn't a functional region to select. I accidentally discovered the text next to the pencil was, indeed, editable, so I finally was able to name some of the objects to something more meaningful to me. I just didn't know the name itself was the editable field. The reason for this is simple: Many applications provide a pencil icon to indicate something's editable, but in all cases, you actually click that icon (or so-equipped button) to make a change. So conditioned was I (I think they call it web style standards), that for the longest time I managed not to place my mouse over the actual object name and "discover" that's how you actually edit the object name. I guess I was dense.... And while I am no less dense, now, it would still behoove ESET to adhere to some semblance of web page design standards, here. As annoying as not being able to perform editing or deleting (or really perform any action while in List View), the bigger problem is why can't I remove the bogus phantom objects (all of which are "routers")? Especially when I only have one router in the network. And why does one of the bogus R7000P objects show up in List View as being affiliated with Xerox as a vendor? I have zero Xerox products in my possession, so this object is wrong for multiple reasons. And I want the field to reflect reality, and no amount of re-scanning is changing this. So, I set about trying to figure out where the objects are stored, as I reasoned, perhaps, I can move/rename the file that houses the objects, perform a new scan and force ESET to generate a completely new result, and maybe, just maybe, the bogus objects would be gone. I went sleuthing and found, under ProgramData, the following files that are most probably Connected Home Monitor-related: homenet.dat homenet_cloud_cache.dat homenethash.dat Of course, these files are not in any sort of human-readable format, but homenet.dat looks like the main object I might have wanted to hide so as to force a clean, (and actual) result set. It would be nice if the files were xml as opposed to dat, and even though xml files aren't all that pretty to look at, either, they're easier than what I see inside of the dat files.... When I tried to move/rename these files, I was prevented from doing so, of course, as ESET was protecting them; I tried to temporarily shutdown ESET via msconfig so that it wouldn't start at boot, and then I would probably be able to do something with the 3 files above, but, again, ESET was preventing that action, also. Don't get me wrong, I am not bemoaning that aspect, as I recognize preventing ESET from running would be a pretty sizable vulnerability.... What I want to do--and what should be readily available to the user, is the means of being able to wipe the field slick and let the Connected Monitor Scan "re-discover" from scratch, the actual, available network devices. In the absence of that ability, I would like to know how I can achieve what I want by temporary manipulation of ESET. I believe several improvements with this Tool are warranted, but for now, I'd settle for simply being able to wipe out what is currently presented and let a new result be generated. Hoping someone can tell me how best to accomplish. Best Regards, Mike Gentry
  4. I had this exact same problem back in May. I opened a Customer Case (1177427), but no solution was really found. I "solved" (or so I thought) the problem by adding my subnet to the Trusted Zone. This solved the problem for close to a month, but an unrelated issue caused me to have to execute an "In-Place Upgrade" of Windows 7 to restore functionality lost by the manual removal of (alleged) End-of-Life of msxml3.dll (this according to Secunia PSI). The In-Place Upgrade solved my loss of functionality of Windows, BUT, it also caused my Eset blocking Internet problem to return--and this time, having my subnet in the Trusted Zone changed nothing. I am currently operating ESS with the firewall driver file renamed so the firewall aspect is inactive. Your description of this problem is identical (in all respects) of exactly what I experienced--down to having the same problem in version 6.X of Eset Smart Security. I didn't try to go back to version 5.X, though. I sent an email to the ESET Customer Care technician (on Saturday, 7/19) who had handled my earlier case and posed the question to him as to whether the additional elapsed time (since my case got closed) has yielded any new "discoveries". Googling it is how I stumbled across your entry, so more and more people are seemingly experiencing it. In one of the last emails I got from Customer Care, they happened to mention more than one client had reported this issue. They also mentioned all of them seemed to have Realtek as their NIC device. Rolling all of my Realtek device drivers completely off of my system, though, had no effect. At-the-time, the only solution that worked for me was to add my subnet to the Trusted Zone. Unfortunately, that "solution" no longer yields positive results--so my Windows In-Place upgrade has probably moved my system closer in appearance to that of what most other folks (who have experienced this problem) must have.... My original thread on this same problem can be found at https://forum.eset.com/topic/2514-new-smart-security-works-too-well/ (viewers may have to Google for this, as for whatever reason, while I can still find my original thread on the forum, when I key in the URL for it, one gets taken to some link talking about an Expiring License and has NOTHING to do with what is being talked about here. Don't know why one cannot simply copy and paste the URL into this forum, either). The Customer Care representative won't be in the office until Monday, so I don't expect I'll hear from him until sometime tomorrow evening. In addition to having had Realtek network drivers (like other people with this problem), I rolled all of those back--removing the software as I went, until I had nothing but the native Windows device driver. I still have the problem. Am beginning to wonder about something else, and that is whether folks with this problem ever had Vista installed on their respective systems, and instead of performing a clean install of Windows 7, maybe ran the upgrade and migrated, instead.... Only reason I ask this, is that whole msxml3 business.... Microsoft provides a KB article that sports the various versions of msxml, but that KB doesn't identify which version of msxml "comes" natively with each version of OS. When Secunia told me msxml3 was EOL, the recommended "update" was msxml6--which I dutifully installed.... Problem is, msxml3 was not automatically uninstalled as a consequence. Seeing the presence of an EOL component as a bad thing, I set about to remove it. Which I did. Only I broke stuff in doing so.... I couldn't open the System option from Control Panel. Couldn't view the Event Viewer. Couldn't do a System Restore.... Stuff like that. So I had to do the In-Place Upgrade in order to "fix" my Windows installation. I wonder if msxml3 was native with Vista, while msxml6 is native with Windows 7--and for reasons unknown, when I performed my upgrade from Vista to Windows 7 (a couple of years ago), perhaps msxml3 was "retained"? And now, it's EOL, but is, somehow, entrenched--and installing msxml6 does nothing to remove the aged msxml3 components.... This may be nothing, or it might be something.... I throw it out there for consideration. Another data point as it were. I will try those steps this thread mentions--just to see if I am able to get Internet connectivity restored (when the firewall driver is enabled), but I concur this matter is definitely Eset-related, as it only manifests when it is installed--and, oddly, only after the system is restarted after being installed. Outside of Eset Customer Care responding to the (closed) ticket email I sent on Saturday, I may have to open another formal case and get them to link the two--or maybe they can just re-open my old case. I will definitely inform them about this (recent) thread on the Forum, and how the problem is "real" as it sounds as though there's a goodly number of folks being affected. Will let any interested parties of this thread know of any results I get. Regards, Mike Gentry
  5. //Final Update Customer Care wound up having a few other clients with the same reported problem. One thing in common was we all had Realtek as our NIC provider. And Customer Care tried to solve the problem by having those clients add their respective subnets to the Trusted Zone--just as I had done, but, unfortunately, their problem was not solved. Don't know if this is noteworthy or not, but Realtek did release two NIC drivers very close to one another in early June (which is uncharacteristic for them in terms of release cycle--usually they may go several months between releases). Don't know if this is a coincidence or not. Just throwing it out there for consideration. If I feel particularly adventurous, now that I have updated NIC drivers yet again, it would be nice to see what happens if I (temporarily) remove my subnet from the Trusted Zone--to see if the symptom comes back, -OR- if normal behavior is maintained without having my subnet listed. Presumably, the issue must be something else, as I systematically removed all of my Realtek drivers I've installed over the years--removing the software as I marched backward until all my system could find was the Microsoft driver. There was no change in symptom until I added my subnet to the Trusted Zone. I simply don't know what it is about my machine that suddenly seems to require this. As my problem was 'solved' by adding my subnet to the Trusted Zone, Customer Care rather unceremoniously closed my ticket. Even so, George L. from Customer Care was great to work with.... We may never know what the real culprit was, but I guess am going to mark this thread as Solved, (even though we never really found the smoking gun). Regards, Mike Gentry
  6. //Update Many log files and various attempts have been analyzed and suggested--without finding a specific cause of the problem. Customer Care floated the notion perhaps I should consider operating without the firewall and just continue using AV. Not wanting it to come to that, and not accepting that as the final answer, I did some more poking around on the Internet. In so doing, I stumbled across an older Wilder's Security forum item which sounded a lot like my problem.... In the old case (see hxxp://www/wildersecurity.com/threads/lost-access-to-home-network-after-installing-eset-smart-security.269608/ ), someone's suggestion was to add 192.168.0.0/255.255.255.0 (presumably their own subnet) to the Trusted Zone. This looked like something I could check, and so I did. Interestingly enough, my subnet existed with the DnsIp...DhcpIp information, BUT was conspicuously absent from the Trusted Zone. So I added it (although I decided to narrow the scope a bit.... I added 192.168.1.0/255.255.255.0, instead). Instantaneously, my Internet connection was restored. I could use browsers; various applications that required connectivity all sprang to life, etc. And better still, this behavior persisted following subsequent reboots. While I don't know whether my private home subnet should have been automatically added to the Trusted Zone during installation, the fact remains, this was not happening, and was the cause of my problems. I have relayed all of this to Customer Care and I hope to ascertain whether this should have been automatic behavior during installation, and if so, what could have impeded such from occurring. If nothing else, perhaps this thread can serve to help someone else out should they encounter the loss of Internet connectivity following installation of Eset Smart Security.... Simply stated, check to see whether your network appears in the Trusted Zone. For now, my ticket is still open as Customer Care is closed. I won't hear anything more from them until next week. Best Regards, Mike Gentry
  7. //Update Connected with George L. w/ESET Customer Care, 5/30 Friday evening. We tried several actions to no avail, but did capture some more logs (PCAP as well as the previous evening's Procmon logs)--all of which were ftp'd back to Eset (for eventual transfer to Home Office). Heard from George again, today, Monday 6/2, with something else he wanted me to try in the meantime--namely, re-enabling the Eset fw driver (it's currently disabled so only Antivirus protection is running). One of his colleagues suggested I try running the firewall in Learning mode, so I re-enabled the driver, and rebooted. Learning Mode created a slew of new rules, but once it settled down, I still had no Internet connectivity. I've communicated this back to George via separate correspondence associated with the actual trouble ticket. I reverted back to disabled driver operation. George also mentioned, perhaps, the next thing to try is disabling all of the non-Microsoft elements in msconfig, and start the process of enabling items one-by-one until I find the "winner". At least, I think I interpreted his intent correctly.... Such an evolution will require several hours of uninterrupted activity and I'm not certain when I'll manage to get to that. In the meantime, we're awaiting analysis by the Third Level folks. Maybe they'll see something interesting before I am able to attempt hours of selective enabling. Just wanted to provide "status" as this continues to evolve. Regards, Mike Gentry
  8. //Update The previous evening's missed appointment seemed to have stemmed from First Tier support entering my phone number into the appointment system incorrectly--resulting in last night's missed window. However, this evening I was finally able to connect with George L. from Customer Care. He witnessed first-hand the problem I reported, and he captured some data via SysInternal's Procmon application, but his work day concluded before we could ftp the results for further analysis. I have something going on Thursday, so we're getting back together on Friday to upload the captured information. Hard to tell how long the resulting analysis will take, but it's definitely an odd problem. After re-installing 7.0.317.4, and then rebooting, that's when the issue manifests. Until the reboot occurs, everything is fine. We've ruled out the Windows firewall remaining engaged. Also, we found we can ping an IP or Domain successfully, but all other Internet connectivity is essentially blocked until I uninstall ESS (again). Hopefully, Procmon will reveal what is causing this issue. Searching the forum leading up to this evening's session, revealed a similar problem back in 2008 under the former forum. In that case, another customer had the same sort of issue (i.e., no connectivity after reboot following installation of Eset). That person's problem was slightly different from mine in that he also was running a product called "Hide My IP". By contrast, I'm NOT running that product or anything remotely similar. That thread is found here: hxxp://www.wilderssecurity.com/threads/eset-smart-security-and-hide-my-ip.220741/ Unfortunately, I did not see a "resolution" specified in that particular thread. Since it involved an application I am not using, even if a solution had been determined, such might not have any bearing in my case. Just wanted to provide an update. BTW, for the record, George was very friendly and helpful. Am hopeful a resolution will be forthcoming. Will continue to provide status as it evolves--for posterity--just in case anyone else should encounter something similar (although, hopefully, this particular problem (whatever it is) is rare). Regards, Mike Gentry
  9. Peter, Thanks for responding. I do have an open case with Customer Care, but as of this writing, they're not responding. I raised the case Friday evening, and spoke First Tier support, but was told it was too near closing time to resolve with Second Tier--and I had to wait until Tuesday due to the holiday weekend. So waited I have.... On Tuesday, I began "camping" by my telephone waiting for the promised Customer Care return call starting at 7PM Local (Eastern) (the agreed upon time 7:30 local--4:30 Pacific)), only to receive an email message at 7:31 PM (local) from Customer Care stating "they tried to reach me, but could not".... Odd. I was right next to the phone and it never rang. I am now on hold trying to get through, but am up against the clock again, as their work day will be ending soon.... Congrats on getting to download an older version, but the link on that knowledgebase article to download older ESET Smart Security for (Windows 7 32-bit) only downloaded the latest version.... For me, anyhow. I did find an offline installer version elsewhere on ESET, but it wasn't the previous v7.xxx version, but in fact, was a 6.xxx version--and, unfortunately, this exhibited the same problem the latest version did. I should have just left well-enough alone and kept my previous v7 installed instead of moving to the latest version, as now I have an issue I can't seem to resolve on my own. I've never encountered this kind of problem before.... And getting hold of someone at Customer Care is trying my patience. It looks like I am going to have to miss work tomorrow morning in order to schedule another appointment. This assumes I can even get hold of someone to set another appointment. Not very happy in Virginia right now. Mike Gentry
  10. Long time user of ESET, but am a bit aggravated at the moment.... There are several matters contained within this post--I've detailed them and summarized them at the end.... I installed the latest version of Smart Security. Beyond the usual problem of having to use the Eset Uninstaller (in safe mode), and the fact one is told you can install safely over top here in the forum (right within the thread that announces the new version), but on the download page it is RECOMMENDED you uninstall first.... For me, the last several years, it's not a matter of "recommendation"--I have to do it. Some file under the "Charon" directory always prevents me installing over top. I find I MUST remove Smart Security first.... It wasn't always like this, but has been for several years, now--at least for me. But, I digress.... The latest version installed just fine. No problems there. I ran for hours, but it got late, so I shutdown my system. In fact, no problems were observed at all, that is, until the first time turning the computer back on after securing it the night before.... My first indication of problems were my WeatherBug and Secunia PSI Internet connections were failing.... I then launched my browser( s ). Same thing. Basically, anything that required an Internet connection was failing. I tried temporarily turning off Protection and the Firewall. This did not change the status quo. So, I uninstalled ESET Smart Security, and instantly, I had connectivity again (no protection, now), but connectivity. I went through Registry and manually removed any remaining ESET entries, rebooted again, and then re-installed ESET (I had downloaded the offline installer, so that's how I re-installed it). Once again, ESET installed just fine, everything seemed fine. Until I powered off and powered back on later on in the day.... Once again, no Internet connectivity. Smart Security works "too well". Once again, I had to uninstall it. So, it seems something about the latest version of ESET and my system do not like one another. I wanted to go back to the previous version, but this is where things get really aggravating (almost as bad as not being able to copy & paste inside this narrative).... I navigated my way to hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN2885 as this page supposedly provides previous versions of your product. ONLY, IT DOESN'T.... The version that was downloaded (which is also aggravating as the filename doesn't possess the version number, and msi cannot be run as administrator like exe files can) is the same NEW version of your product. Of course, I don't know this until I start that install process and Eset takes stock of my system, and finally displays the version number in the lower left portion of the installer dialog box. Even though I selected the Windows 7, 32-bit version from the KB page dealing with "How do I download and install older versions of ESET products", the version presented and downloaded is still the newest version: 7.0.317.4--NOT THE PREVIOUS VERSION Unfortunately, I no longer have my former version's offline installer. The problems I am reporting are many and varied (the main ones are bolded): To summarize: 1. Latest version allows zero Internet traffic, but only AFTER rebooting following an install 2. The fact I have to resort to uninstalling your product using an ESET uninstaller expressly built for the purpose in Safe Mode continues to be an onerous issue--one I reported years ago, but have gotten no relief. I have lived with it, but because I am here again reporting a more serious problem, decided I'd let this one bubble to the top and mention it yet again. 3. Cannot seemingly use copy and paste within the narrative box when writing something on this forum 4. ESET's use of msi files rather than exe (exe's can be run as administrator; msi files cannot), AND the lack of embedding version info in the filename so it is obvious at a glance makes for not knowing what you've downloaded until after you try to install. 5. Your KB page devoted to providing previous versions of ESET products, DOESN'T 6. I have a paid license for a product that is not working, and no way to get back an older version that was working....
×
×
  • Create New...