"View workgroup computers" Error

Ruben,

Last week Marcos e-mailed some of us a link to the .dat file. It was intended only to help ESET diagnose the workgroup problem. It has never been released to the public.

 

ok, thanks

Ruben

PS: kind of mixed info - does it help?

 

nope
.

 

It works til the other computer is turned off. It seems that turning off the other computer is what causes it to fail. If I turn the other computer back on it doesn't work. Then if I reboot this computer with the other one turned on already it starts working. I've done this a couple times now and both times it worked.

Ruben: I wasn't here when the new dat file was passed out. I sent an instant message to Marcos asking for it and he sent me an email with the link to it.

 

any chance to get that one too?

Ruben

 

If you have the desktop turned on already then reboot the laptop it will probably go back to working.

With my network as long as I turn on the computer that has ESS after the other computer is already running it works. Then as soon as I turn off the other computer it fails again. If I turn the other computer back on it still doesn't work.

Turning the ESS computer on second has worked every time I have tried it. It works just as long as I leave both computers on.

 

I've been in touch with stueycaster, but I wonder if someone else could confirm or deny that the problem goes away after disabling all IDS rules.

 

all ids rules disabled without patch = same problem
all ids ruled disabled with patch = same problems

nothing logged as being blocked

 

I was able to get mine to accept the changes in the IDS rules after downloading and installing a new copy of ESS. There was no change in the workgroup link with the intrusion detection rules disabled.

Again the link worked until I rebooted the other computer. After that it failed.

Then I rebooted this computer and it started working again. This time it worked without changing the .dat file I had changed before.

 

There are repeated copies of all these in my firewall log. It looks like it keeps trying different ports. I had checked "Allow UPNP in the trusted zone".

11/21/2007 8:50:26 PM Communication denied by rule 192.168.0.1:1679 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/21/2007 8:49:02 PM Communication denied by rule 192.168.0.1:1678 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/21/2007 8:47:49 PM Communication denied by rule 192.168.0.1:1675 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/21/2007 8:46:36 PM Communication denied by rule 192.168.0.1:1672 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/21/2007 8:45:13 PM Communication denied by rule 192.168.0.1:1671 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/21/2007 8:43:50 PM Communication denied by rule 192.168.0.1:1668 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/21/2007 8:39:29 PM Communication denied by rule 192.168.0.1:1663 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/21/2007 8:38:05 PM Communication denied by rule 192.168.0.1:1660 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/21/2007 8:36:52 PM Communication denied by rule 192.168.0.1:1657 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/21/2007 8:35:29 PM Communication denied by rule 192.168.0.1:1656 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/21/2007 8:23:36 PM Communication denied by rule 192.168.0.1:1653 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/21/2007 8:22:17 PM Communication denied by rule 192.168.0.1:1652 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/21/2007 8:20:55 PM Communication denied by rule 192.168.0.1:1651 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/21/2007 8:20:31 PM No usable rule found 192.168.0.100 224.0.0.22 IGMP
11/21/2007 8:14:08 PM Communication denied by rule 192.168.0.1:1642 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/21/2007 8:12:55 PM Communication denied by rule 192.168.0.1:1641 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/21/2007 8:11:42 PM Communication denied by rule 192.168.0.1:1640 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM

 

I deny that.

 

as a test ive just done a fresh instal of windows xp sp2 (oem) on the machine i been having the problem.

-installed XP
-installed drivers
-ran critical updates
-rebooted
-installed ESS 3.0.566
-rebooted

"view workgroup computers" is still functioning after 30mins or so.. will report back later

 

Thanks for the information.

When I had discovered that on my sister's laptop everything seemed to be OK with the discussed issue I also thought that maybe this had something in common with having the operating system installed for quite a long time now. For the past few years I've been adjusting and improving my network configuration and maybe that's why the problem occurs. Still I know it's not an issue for other security suites and that's why I would rather wait for a cure from ESET than reinstall my copy of Windows, at least for some time ahead.

I would really like to know how many of you view workgroup computers without any trouble (with ESS on board of course).

 

lookin good so far, been working for over 3 hours (the longest "view workgroup computers" has worked with ess installed on this machine)

 

This is definitely an ESS bug. If you read through the posts in this thread plus another thread there is a lot of detail.

https://www.wilderssecurity.com/showthread.php?t=185194

Marcos is working with us on it and I expect a fix for it soon. I have no definite idea when though.

Here is a little work around for workgroups with ESS on only one of the computers. I don't know if it works on multiple computers with ESS or not. I can see why it might not.

When the "View workgroup computers" link fails reboot the computer with ESS while the other computer(s) is/are already running. It works every time for me.

 

20hrs+ still perfect.
i can only guess something else that was installed/uninstalled in the past was causing a conflict.

that last installation of xp had seen nearly 4years use, seeing sygate/jetico/outpost/comodo come & go.

with this fresh instal its all good now!

 

Cool kC_. I'm glad things are working out for you. I'm surprised that you were able to run Windows four years without having to reinstall. I usually go about one year between re-installations. I'm always messing mine up and having to re-do it.

 

i use acronis true image, so any major problems and i just rolled back to a good known point.

24hrs+ and still going strong with ess now

 

48hrs+ and still perfect.
so obviously not a hardware or software problem, more likely a conflict with a bit of software thats been previously uninstalled i guess.

 

don't agree. made a clean xp install and still stuck with the thing.

 

Me too.
Also other threads are appearing showing slightly different problems with network sharing. Clearly this is a general problem with ESS .

 

I read a review that said ESS has a problem with the trusted zone. It looks that way to me. Marcos has been in touch and I'm sure they're working on it now.

I think there were more urgent problems to deal with during the beta testing. This one had to take a back seat. There were problems with installation, BSOD, updates and other scary things. I guess it's a lot harder to develop software than I realized. I'm just glad I never had a BSOD. That would really freak me out.

 

Good news that they are still working on it. Has he been touch since the testing of the alternative .date file?

 

Hi Folks,

I need some help with this issue. In order to view/access my workgroup, I was able to uncheck the "Eset Personal Firewall" option in Local Area Connection Properties > General.

Now that I have re-checked this option I have received a warning dialogue box asking me to install software for my hardware device which has not passed the windows logo testing for compatibility. I elected to NOT install the software.

The Eset Personal Firewall is checked, but I am worried now that the firewall is not fully functional as I can still access and view my workgroups, which I can't under normal circumstances because of this bug.

Please can someone help me with this issue?

Thanks,

Jacqui

 

I sent Marcos an instant message where I told him about the workgroup link working after I reboot the ESS computer with the other computer already turned on. Check out post #82 in this thread. He replied asking me about disabling the IDS rules. I thought this showed interest and assume they are working on it. That's all I know at this point. Sorry I can't be more definite.