"View workgroup computers" Error

[stueycaster]

I was writing about this on another post but it looks like it's a different issue so I wrote my own post.

When I'm in "My Network Places" I can access all the shares that show up there. If I click on the "View workgroup computers" link I get this error message:

"Mshome is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
The list of servers for this workgroup is not currently available."

When using the betas this problem would progress to a state where the network would fail a little bit later on. Now it seems that the network problem has been fixed. :D:thumb: I would think that the view workgroup thing must be a separate issue. I'm sure ESET will fix this at some point. It seems that there are other, more urgent problems out there.

I was thinking that if a person knew which .exe (or whatever. Hey I'm just a geek wannabe) operates the view workgroup thing then maybe they could write a rule to allow it. Maybe? I made a half hearted attempt to find out if this thing exists but couldn't. I was hoping someone out there might already know or know how to find out about this. I'm probably going to do some more research on this if nobody knows already.

Also there was something about Netbios and TCP that was getting blocked by firewalls. I have no clue what that's all about. However this is something the firewall log in the betas said was being blocked.

[Palombaro]

-{ Quote: "I was writing about this on another post but it looks like it's a different issue so I wrote my own post.

When I'm in "My Network Places" I can access all the shares that show up there. If I click on the "View workgroup computers" link I get this error message:

"Mshome is not accessible. " }-

I have exactly the same problem

[stueycaster]

Are there others who have this problem? ESET is more likely to take it seriously if there are more than just two of us. Please post something here to let them know if you're having it too.

[kC_]

http://www.wilderssecurity.com/showthread.php?t=190305

[Palombaro]

-{ Quote: "http://www.wilderssecurity.com/showthread.php?t=190305" }-
I I think this is slightly different to your problem KC. Both stueycaster and I can access my network places and have total access to shared files on the network. It is access to 'view network computers' that we don't have. Your's seems a more serious problem

[kC_]

guess i titled it wrong i can see my network places, but yeh its when i view "view workgroup computers" the error appears

filesharing/printersharing/premade shortcuts & mapped drives work fine..

[stueycaster]

Glad you got that network thing straightened out kC. I just wish they'd fix this thing. I can't believe there are only three of us with this problem. Makes me wonder if I'm doing something wrong.

[kwg]

-{ Quote: "I can't believe there are only three of us with this problem. Makes me wonder if I'm doing something wrong." }-

You are not alone; I have the same problem. Until ESET fixes this problem, my home network is useless. Consequently, I am unable to share data between computers or perform network backups of the data on my computers.

[Marcos]

Please confirm or deny:
- Is the Trusted zone configured properly and all computers in your LAN are members of it?
- Does the problem perist no matter whether interactive or automatic mode is selected?
- Does disabling the firewall completely make a difference?
- Have you enabled logging of all blocked connections and no blocked connection appeared in the firewall log?
- Do you have another firewall installed?

[Palombaro]

-{ Quote: "Please confirm or deny:
- Is the Trusted zone configured properly and all computers in your LAN are members of it?
- Does the problem perist no matter whether interactive or automatic mode is selected?
- Does disabling the firewall completely make a difference?
- Have you enabled logging of all blocked connections and no blocked connection appeared in the firewall log?
- Do you have another firewall installed?" }-

1) yes
2) yes but on original install for a blissful two hours or so the network worked exactly as it should have done. In this period I used the default installation , i.e automatic mode and then switched to interactive filtering and there were initially no problems in either but then later after making no system changes at all the problems started and continued whatever I did with filtering.
3) yes
4) No
5) No

I would add that as I am running the trial version (v 563) and not yet committed myself to ESS I have just uninstalled ESS (temporarily I hope) and reinstalled my original firewall and the network works without any problems. Clearly there is something in ESS that is causing this problem.

[soulstace]

First, check the firewall logs as Marcos suggested.

If all else fails try to allow ping (ICMP).

Windows filesharing or workgroups seems to have a fit if ICMP gets blocked.

[Jeff Bellune]

Hi,

I had the same problem after my initial install of the trial version. I could access specific folders on my network, but I could not view the workgroup computers.

The good news is that after a thorough uninstall and then a reinstall, the issue has not reappeared.

So what's the difference now?

There was a lot of tinkering with advanced settings between installation and discovering this issue, so I can't say if any one particular setting change triggered it. There have been some, but fewer settings changes after the reinstall, and the issue has not reappeared. I've checked after each setting was modified.

Answering Marcos' questions about the first installation:

1. Yes
2. Yes
3. No
4. Yes
5. Yes. Windows and an inactive/disabled ZoneAlarm Security Suite.

System specs:
Windows XP SP2 32-bit
P4 3.0 GHz w/HT
2.0 GB RAM
ATI Radeon 9800 Pro 128 MB

[Jeff Bellune]

Question for Marcos:

Are there any of the ESS prorgam files that shouldn't be moved from their original, physical location on the hard disk?

For example:Acronis' TrueImage program doesn't like having its files moved around by defrag programs, so I had to exclude some of those from being defragmented.

A defrag pass by PerferctDisk 8 was run overnight between installation and the appearance of the issue the first time.

-Jeff

[Palombaro]

-{ Quote: "Hi,

I had the same problem after my initial install of the trial version. I could access specific folders on my network, but I could not view the workgroup computers.

The good news is that after a thorough uninstall and then a reinstall, the issue has not reappeared.
" }-
I tried the thorough uninstall removing all residual ESS folders and through regedit removed all registry keys associated with ESS , rebooted and reinstalled. In fact I did it when going from v551 to v 560 and then again to v 563 . On each occasion it appeared that the problem was solved but a short time later it always reappeared. Once ESS is removed so is the problem even with another firewall. I have tried it now with my old Sygate Pro firewall and the latest Comodo firewall and there are no problems with the network at all.

[Jeff Bellune]

-{ Quote: "I tried the thorough uninstall removing all residual ESS folders and through regedit removed all registry keys associated with ESS , rebooted and reinstalled. In fact I did it when going from v551 to v 560 and then again to v 563 . On each occasion it appeared that the problem was solved but a short time later it always reappeared." }-
Hmmm. Then I guess I may be posting back in a few hours. :D

[Marcos]

Some more questions:
- what OS are you running? (32 or 64-bit?)
- has someone observed this problem also with EAV?

If someone is able to replicate this problem easily at any time, please PM me.

[Palombaro]

-{ Quote: "Some more questions:
- what OS are you running? (32 or 64-bit?)
- has someone observed this problem also with EAV?

If someone is able to replicate this problem easily at any time, please PM me." }-
I am running XP Home SP2 on one PC and XP Pro SP2 on the other computers connected to the network(32 bit obviously)

[Palombaro]

-{ Quote: "Hmmm. Then I guess I may be posting back in a few hours. :D" }-

I hope not. Hopefully you have resolved the problem. If we only we could work out what it was in the 'tinkering with advanced settings between installation and discovering this issue' that did the trick.

[kwg]

Marcos,

I am using 32-bit Windows XP Professional.

It makes no difference whether the ESS firewall is in automatic or interactive mode.

When I attempt to view "workgroup computers," I don't even see the computer I am using.

I had no such problem when using Agnitum Outpost.

[KFBeaker]

-{ Quote: " I can't believe there are only three of us with this problem. Makes me wonder if I'm doing something wrong." }-

You can add me to the list. There are many people with different manifestations of this networking bug. And there are a lot of people who are not on a LAN that don't have the chance to see this bug.

But from what I have seen, this is one big universal bug ALL ESS owners have, some just don't realize it yet.

Let's hope ESET realizes it soon.

[KFBeaker]

-{ Quote: "Some more questions:
- what OS are you running? (32 or 64-bit?)
- has someone observed this problem also with EAV?

If someone is able to replicate this problem easily at any time, please PM me." }-

1. Vista 32
2. No. On a box running NOD32 v3 and Windows firewall.

-{ Quote: "
Please confirm or deny:
- Is the Trusted zone configured properly and all computers in your LAN are members of it?
- Does the problem perist no matter whether interactive or automatic mode is selected?
- Does disabling the firewall completely make a difference?
- Have you enabled logging of all blocked connections and no blocked connection appeared in the firewall log?
- Do you have another firewall installed?." }-

1. Yes
2. Yes
3. Yes
4. Logs seem to suggest ESS believes it is under an ARP attack from devices in the trusted zone. Might all this be as simple as an IDS issue. Maybe have ESET look into disabling IDS from within the Trusted Zone?
5. No.


Marcos, if you look around the forum there are a number of different threads but all seem to point to ESS not allowing completel free flow of traffic on the LAN / "Trusted Zone." From people with network printers to my XBOX media sharing thread they all seem to come back to the same thing. Free flow of discovery and traffic within the "Trusted Zone."

I really hope you and ESET can get this solved, and I hope they take a look at the big picture here.

Because simply addressing the different manifestations of this bug on a 'case by case' basis seems a bit like having an elephant in your room, then slicing off its trunk and running around the room with Lysol prclaiming part of the problem has been solved.

[kC_]

-{ Quote: "Please confirm or deny:
- Is the Trusted zone configured properly and all computers in your LAN are members of it?
- Does the problem perist no matter whether interactive or automatic mode is selected?
- Does disabling the firewall completely make a difference?
- Have you enabled logging of all blocked connections and no blocked connection appeared in the firewall log?
- Do you have another firewall installed?" }-

- YES
- YES (although if i switch to automatic & then reboot, it works for 1-2hrs)
- NO
- YES,NOTHING BLOCKED
- NO other firewall

i can fix it by forcing my netgear ga311 NIC to connect at 100mps, if switch to AUTO(connects at 1gps) then the problem occurs

specs -
xp pro oem SP2 (32bit)
p4 3.0ghz
2gb DDR
netgear ga311 gigabit lan (v6.0 driver)

[Marcos]

Do all of you use a 1GB NIC and switching it to 100mps mode helps?

[kringles]

Add me to the list of those having networking problems with ESS. See thread ;

http://www.wilderssecurity.com/showthread.php?t=190934

for more information on similar problems.

My answers to the questions are;

- YES
- YES
- NO
- YES,NOTHING BLOCKED
- NO other firewall

regards

do not use a 1 GB NIC here

[kwg]

-{ Quote: "Do all of you use a 1GB NIC and switching it to 100mps mode helps?" }-
No, the NICs on both computers (and the router itself) run at 100 Mbps.

[kC_]

update: bug persists in 3.0.566.0

[kC_]

those who are suffering and have 100mbit cards, as a test you could possibly try to force the nic card to connect at 10mbps.

[Jeff Bellune]

-{ Quote: "those who are suffering and have 100mbit cards, as a test you could possibly try to force the nic card to connect at 10mbps." }-
Brilliant!

Reducing the Link speed from 100 Mbps to 10 Mbps and rebooting allowed me to see my workgroup computers again.

I was away from my workstation for a couple of hours, no activity and no changed settings in ESS. Upon my return, trying to view the workgroup computers resulted in the network-is-not-available message.

I switched back to 100 Mbps (after the 10 Mbps fix) and I could still see the workgroup computers. If the problem occurs again, I may just leave the NIC set to 10 Mbps, since my NIC only connects to my wireless router, and all other computers on the network connect via wireless.

[kC_]

nope switching back to your original speed will only work for a few hours at most .
if you want your workgroup working 24/7 you would have to leave it at 10mbps
(at least thats my expierience) except im going down too 100mb from 1000mb

i also dont require a reboot when switching link speeds for the fix to work.

-instal ess... "view workgroup computers" works fine for maybe 2 hours... then the error comes up "you dont have permissions"
- switch my nic link mode from 1000mb to 100mb = "view workgroup computers" immediately works again, and has worked perfectly for 4-5days uptime+
- switch nic back to 1000mb and "view workgroup computers" still works but for only 2 hours, then its problem returns..

so only way i have it working here now all day everyday is if i leave it forced at the lower rate.. hoping eset can fix this, has been reported since beta1 !!!!!

[stueycaster]

Cool! I was beginning to think there were only three of us with this problem.

I'm using XP x64 edition. I have an onboard Gigabit lan that has allways been set to 100 Mbps.

1. Yes. Each time the betas would cause this problem I switched back to Version 2.7 and the problem went away.

2. I'm not really sure. I tried Automatic for a short time but there was no way of unblocking my lan messenger so I went back to Interactive. Besides this is the reason why I bought this. I really want control of what goes out and I want to be alerted if anything tries to get out.

3. No difference.

4. Here is a small part of what is in my firewall log. I tried to give an example of the different entries. There seems to be over a thousand of them.

11/15/2007 1:45:13 PM Communication denied by rule 192.168.0.1:1482 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/15/2007 1:41:47 PM No usable rule found 192.168.0.100 224.0.0.22 IGMP
11/15/2007 1:32:27 PM Communication denied by rule 192.168.0.1:1479 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/15/2007 1:29:00 PM Communication denied by rule 192.168.0.1:1900 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests
11/14/2007 9:21:42 PM Communication denied by rule 192.168.0.1:1464 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/14/2007 9:18:18 PM No usable rule found 192.168.0.100 224.0.0.22 IGMP
11/14/2007 9:18:17 PM Communication denied by rule 192.168.0.1:1900 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests
11/14/2007 8:50:29 PM Communication denied by rule 192.168.0.1:1461 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/14/2007 8:47:01 PM Communication denied by rule 192.168.0.1:1900 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests
11/14/2007 6:13:22 PM Communication denied by rule 192.168.0.1:1458 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/14/2007 9:15:19 AM Communication denied by rule 192.168.0.100:137 207.46.232.182:137 UDP Block outgoing NETBIOS requests system NT AUTHORITY\SYSTEM
11/14/2007 4:48:33 AM Communication denied by rule 192.168.0.1:1449 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/14/2007 4:37:43 AM No usable rule found 192.168.0.100 224.0.0.22 IGMP
11/14/2007 4:37:43 AM Communication denied by rule 192.168.0.1:1900 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests
11/11/2007 7:22:45 PM No usable rule found 192.168.0.106:1033 255.255.255.255:19771 UDP
11/10/2007 11:51:02 PM Communication denied by rule 192.168.0.1:1412 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/10/2007 11:50:12 PM Communication denied by rule 192.168.0.1:1411 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/10/2007 11:48:58 PM Communication denied by rule 192.168.0.1:1410 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/10/2007 11:47:31 PM No usable rule found 192.168.0.1:67 255.255.255.255:68 UDP
11/10/2007 9:36:25 PM No usable rule found 192.168.0.100 224.0.0.22 IGMP
11/10/2007 4:03:41 PM Communication denied by rule 192.168.0.100:137 12.129.31.7:137 UDP Block outgoing NETBIOS requests system NT AUTHORITY\SYSTEM
11/10/2007 9:37:33 AM Communication denied by rule 192.168.0.1:1389 192.168.0.100:2869 TCP Block incoming ICSLAP (UPNP) requests system NT AUTHORITY\SYSTEM
11/10/2007 9:33:58 AM Communication denied by rule 192.168.0.1:1900 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests d:\windows\system32\svchost.exe NT AUTHORITY\LOCAL SERVICE

5. No other firewall.

Something I failed to mention is that the other computer on the network doesn't list this one when I try to view the workgroup computers.

[Jeff Bellune]

Update:

The error occurred again with my NIC set to 10 Mbps. I changed the speed back to 100 Mbps and then I could view my workgroup computers again. After the usual few hours, I had to switch back to 10 Mbps to view them again.

So maybe it is a change of speed that temporarily fixes the issue, rather than simply a lowering of the speed of the NIC.

[kC_]

i have found with 3.0.566.0 its actually worse. now i get same symptoms as yourself, no matter which mode i switch to it gets blocked after 2 hours.

ive uninstalled ESS and reverted to nod32 2.7 and my routers firewall for now.

eset uk support im in touch with just keep telling me "try the new version it might fix it"
not very happy at all

[Jeff Bellune]

-{ Quote: "not very happy at all" }-
I really want to like ESS, but I need it to work. Right now, it doesn't, as noted in my ESS+Vista32=Network OK, Internet not OK (http://www.wilderssecurity.com/showthread.php?t=191615) thread. I want a security suite that I can manage across all of my XP computers and my one Vista computer.

I have several months left on my ZoneAlarm Security Suite subscription. But it can't update its signatures on Vista, and on XP I am sick of its (unmodifiable) hourly updates that steal focus from whatever app I am working on.

AVG's suite installs and works on Vista, but its scanners have too many false positives on my XP boxes, and I have almost no confidence in its virus and spyware abilities.

ESS has problems on all my boxes, and I have contributed to forum topics discussing those. Its best-of-breed AV, small footprint and great UI are really attractive, but in its current state it is unusable for me.

I was going to try Kaspersky's new suite, but the reviews I've read seem to indicate that it has lousy protection out-of-the-box. It apparently takes quite a bit of tweaking to get it to "bullet-proof" levels of security.

I apologize for the off-topic stuff. You can probably tell that getting my Vista laptop properly protected and integrated into my (mostly) XP network has been a complete exercise in frustration.

I'll keep working on this with ESET as long as I can.

[stueycaster]

Eset was able to produce an antivirus that in my opinion is the best on the market. I love the way it always allowed my system to run free and easy while it kept it safe from viruses. I've used some other products and found they weren't as good as Nod32.

However it's also been my experience that there is no such thing as a perfect computer application. Microsucks is the largest software manufacturer in the world and there are so many problems with Windows that just learning to use it takes years. The average computer user surfs the net, uses email, plays with photographs and plays video games on it. Then when it develops problems due to malware they take it to the shop and pay someone to fix it. I can't believe how many applications I've tried and discarded because there was no way of getting them to work right. I'm really surprised I like still like computers as much as I do. I guess it's the challenge.

What I am trying to say is don't get disheartened. Eset will turn this thing into something that is at least as good as if not better than the other products on the market. Go spend some time in the forums of the other anti-malware companies. People have a ton of problems with their mature products. Probably every computer in the world has a different software configuration and there has to be conflicts. Just keep working on it and have faith. Be nice to the folks at ESET. They're doing their best and I'd say they've done a good job.

Sorry but I needed to rant a little. It just bothers me the way some people have treated the ESET crew.

[Jeff Bellune]

Well said, stueycaster.

I hope my "rant" didn't come across as bashing ESET. I'm only using the trial version of ESS and already I've gotten great support from ESET both here and privately. I do not question ESET's commitment to excellence at all.

It is the overall experience that has frustrated me. Think about it - Vista has been RTM for a year, and yet ZoneAlarm still doesn't have a functionally reliable Vista version released. How silly is that? I know the developers at CheckPoint must be equally frustrated, so I don't want to bash them, either.

TBH, if I could have purchased a laptop for my son that *didn't* have Vista on it, I would have. But requesting that an upgrade :) to XP be preinstalled would have cost me even more money (if it was even possible).

I seem to be wandering off-topic again, so I'll just take my seat and be quiet now.

[stueycaster]

No you didn't come across that way Jeff. I've read some of the most horrible things directed at ESET over this.

I can empathise with you totally on your problems. I've had to reinstall Windows more than once because of problems I had with third party applications. Besides, Vista wasn't designed with the users in mind. It was designed for Digital Rights Management and controlling what people are allowed to do with it. I'll never use Vista and that's a promise. Within the last four weeks I have started learning to use Ubuntu Linux. By the time M$ stops supporting XP I won't be using Windows at all any more.

[kC_]

i was told by beta support that the problem was fixed , so i bought a license, then 3 builds later its actually worse.
ive requested a refund.. may come back when/if it gets fixed, its an ideal suite for me, but unusable

[stueycaster]

-{ Quote: "i was told by beta support that the problem was fixed , so i bought a license, then 3 builds later its actually worse.
ive requested a refund.. may come back when/if it gets fixed, its an ideal suite for me, but unusable" }-

I bought ESS because of what they told you too kC. I think they were probably talking about the blocked network part. My network hasn't failed since I installed it. I'm sure they'll fix this thing.

[Palombaro]

-{ Quote: "i was told by beta support that the problem was fixed , so i bought a license, then 3 builds later its actually worse.
ive requested a refund.. may come back when/if it gets fixed, its an ideal suite for me, but unusable" }-

They are on the case KC

[stueycaster]

-{ Quote: "They are on the case KC" }-

Yes they are. Marcos has been in here collecting information on it. It won't be long now. :D :thumb:

[kC_]

asked for a refund.. will give the trial a go and see if it gets fixed

cheers

[Palombaro]

I have tried ESS v 566 plus the alternate em008_32.dat file developed to solve this problem. Initially when it was installed on one PC it appeared to have solved the problem. However when I put ESS v 566 plus alternate em008_32.dat file the old problems returned.
Has anybody else tried this patch? If so what were the results when installed on more than one computer on your LAN?

[kC_]

exactly the same problems, didnt fix a thing

(ess only on one pc)

[Jeff Bellune]

-{ Quote: "I have tried ESS v 566 plus the alternate em008_32.dat file developed to solve this problem. Initially when it was installed on one PC it appeared to have solved the problem. However when I put ESS v 566 plus alternate em008_32.dat file the old problems returned." }-
The same results here, only with build 563 instead of 566.

There was hope for a few hours, wasn't there? :)

[Palombaro]

-{ Quote: "The same results here, only with build 563 instead of 566.

There was hope for a few hours, wasn't there? :)" }-

Yes there was hope. Still think there is;they are clearly working on it.
To coin a phrase,' Where there's Marcos, there's hope':)

[stueycaster]

The instructions I got from Marcos said:

1, rename the original file "C:\Program Files\ESET\ESET Smart
Security\em008_32.dat"
2, copy the new module instead
3, restart the computer

I'm using 64 bit XP so I used the 64 bit link and got em008_64.dat. I was a little confused but i decided to rename the original file /em008_64.dat instead. I don't know if I did the right thing or not. There is an em008_32.dat file in mine too. Anyway, it didn't work.

[Palombaro]

-{ Quote: "The instructions I got from Marcos said:

1, rename the original file "C:\Program Files\ESET\ESET Smart
Security\em008_32.dat"
2, copy the new module instead
3, restart the computer

I'm using 64 bit XP so I used the 64 bit link and got em008_64.dat. I was a little confused but i decided to rename the original file /em008_64.dat instead. I don't know if I did the right thing or not. There is an em008_32.dat file in mine too. Anyway, it didn't work." }-
Might be worth giving it another try after uninstalling ESS and clearing all ESS folders. Then renaming the original em008_64.dat file em008_64.datold and then copying in the new em008_64.dat from Marcos and then rebooting.

[stueycaster]

-{ Quote: "Might be worth giving it another try after uninstalling ESS and clearing all ESS folders. Then renaming the original em008_64.dat file em008_64.datold and then copying in the new em008_64.dat from Marcos and then rebooting." }-
Thanks Palombaro. Your suggestion worked. :D:thumb: I didn't know about the datold thing. I had originally renamed it "em008_64-1.dat". That's why I come to forums, so I can learn stuff. Now we'll see if it stays fixed. Thanks again.

[Palombaro]

-{ Quote: "Thanks Palombaro. Your suggestion worked. :D:thumb: I didn't know about the datold thing. That's why I come to forums, so I can learn stuff. Now we'll see if it stays fixed. Thanks again." }-

Let us know if it stays fixed, mine didn't - hope yours does. Have you put it on more than one of the computers on your network?

[Marcin_K]

Where can I obtain the .dat file you're talking about? I would really like to test it myself.

/EDIT: I replaced the file. Everything was OK for a while, but eventually the modification didn't help. What's interesting is that my sister's XP-Home-based laptop doesn't need any file replacements -- ESS doesn't block listing network neighbourhood there. Weird./

[stueycaster]

-{ Quote: "Let us know if it stays fixed, mine didn't - hope yours does. Have you put it on more than one of the computers on your network?" }-

The other computer still has version 2.7. I can't put this thing on my wife's laptop til I know it's 95% perfect at least. She can't stand for anything to not work right and she hates changes. She does love playing with her computer though.

It's been about five hours now and all's well.

[stueycaster]

It's been about 10 hours now and all's well.

[kwg]

I have also installed the .dat file supplied by Marcus, and then rebooted. I am using the latest version, ESS 3.0.566.

After rebooting, my computer is still unable to see other computers in my workgroup. My computer is also unable to see itself in the workgroup. In Windows Explorer I receive the error message that the workgroup is not accessible.

After uninstalling ESS, my network functionality returns to normal.

Off topic:

One of my computers using ESS grinds to a halt after a few hours of use, therefore requiring a reboot. Another of my computers, on occasion (and consistently after the first occasion), fails to start up at all. The latter problem is described here:

http://www.wilderssecurity.com/showthread.php?t=190881

I own a two-year ESS license for two computers, but I am about to remove ESS from both computers. I am also recommending that my clients do the same.

However, I remain willing to help Marcus with any testing. I hope that ESET gets these problems ironed out quickly. Based on ESET's history, ESS really should be the number one security program on the market.

[kwg]

-{ Quote: "Clearly there is still work to be done on this. Hopefully they are still working on it." }-
I am sure they are still working on it. After a difficult week, though, I hope they are taking a break this weekend.

[kC_]

im back on nod32 2.7 for the time being & trusting my nat router/win firewall to block incoming.. eset have refunded my ess license

hope it gets sorted for you guys, i just dont wish to be paying & wasting days/weeks/months on my license waiting for this to be fixed.

2 bad things eset did..
- ignored it during beta, then assured me it was fixed in the release after RC1.

and email support once i'd purchased the ess license was kinda robotic...
"there is a newer version v3.0.563 try it and see if it fixes it, we have no changelog, but it fixes some networkey stuff"

&

"there is a newer version v3.0.566 try it and see if it fixes it, we have no changelog, but it fixes some more networkey stuff"

kinda leaves me with a bad impression.. but they were VERY quick to refund :thumb:

[ASpace]

That is why there are 30 day trial versions , KC . Next time use them for 30 days and on the 31st buy ESS :thumb:

[kC_]

-{ Quote: "That is why there are 30 day trial versions , KC . Next time use them for 30 days and on the 31st buy ESS :thumb:" }-

tbh if an eset support tech says an issue is fixed, i should be able to trust that;D

[stueycaster]

It has stopped working again. It seems like it stopped after the other computer was shut off all night. For me it always worked the first day then the second day it stopped.

I can't see the blocked connections in the firewall log because I forgot to set it to log them. Now it won't change the setting. When I try it gives me a "Failed to change settings" error message.

[stueycaster]

I just did the reinstallation process and it started working again. It should stay fixed all day. This time I set it to log the blocked connections and it accepted the change.

-{ Quote: "Re the newest version v 566: the network issue it fixes is not this one.
I have uninstalled the trial but as soon as they fix this problem plus the worrying problem re: 'Bug? ekrn.exe can be terminated by users' which the forum seems to have gone quiet on, I will buy the full version but not until." }-

Have you seen a change log Palombaro? It still doesn't show at the download site. I'd like to see it.

[Palombaro]

-{ Quote: "I just did the reinstallation process and it started working again. It should stay fixed all day. This time I set it to log the blocked connections and it accepted the change.



Have you seen a change log Palombaro? It still doesn't show at the download site. I'd like to see it." }-

No I haven't seen the changelog but Marcos in another thread said, '....no need to upgrade as the only change was a fix of the bug that prevented installation on certain systems when a network connection was already established', which is not the same problem as this.

[stueycaster]

Ok thanks.

[Marcin_K]

Today, without any conf changes, all works great again... Funny thing is yesterday I put the original .dat file again... Now I'm totally confused.

[stueycaster]

-{ Quote: "Today, without any conf changes, all works great again... Funny thing is yesterday I put the original .dat file again... Now I'm totally confused." }-
I just thought of something.

When I set up the network on the Ubuntu Linux side of my computer it took quite a while for it to show up. In the forum I found that it is normal for it to take as long as fifteen minutes. I've seen it take a while to start up in Windows too though nothing like Ubuntu.

This morning the first thing I did was to check to see if it was still working. Of course I had to turn on the other computer first. When I found that it wasn't I immediately reinstalled ESS.

Now you are saying it came back unexpectedly. Maybe I rushed the network. The next time I run into this I will wait a while and check it again before I decide it's broken.

[tranglos]

-{ Quote: "Are there others who have this problem? ESET is more likely to take it seriously if there are more than just two of us. Please post something here to let them know if you're having it too." }-

Same here, the latest ESS build installed yesterday, Nov 17.

I can do cd \\othercomp\share, and I can see the shares defined in My Network Places, but I cannot browse computers on the home LAN. At best only the local machine is shown.

I now have ESS running on both machines, but the problem occurred also when only one system was running ESS (and the other was not firewalled at all).

.marek

[stueycaster]

-{ Quote: "Same here, the latest ESS build installed yesterday, Nov 17.

I can do cd \\othercomp\share, and I can see the shares defined in My Network Places, but I cannot browse computers on the home LAN. At best only the local machine is shown.

I now have ESS running on both machines, but the problem occurred also when only one system was running ESS (and the other was not firewalled at all).

.marek" }-
The best I can tell you is that Marcos has been in here and has tried to help us out with this. ESET is obviously working on it and my guess is that it shouldn't be long. If you want more details you can read through the posts on this thread.

[stueycaster]

After reinstalling ESS this morning I was able to view the workgroup right up until I shut down the other computer. Then about an hour later I turned the other computer on. Then I waited about 15 minutes and when I tried to view them again it didn't work.

Yesterday the other computer was left on all day and the view thing worked right up til bedtime. Then it was dead again this morning.

I think that after the workgroup has been broken by turning off one of it's members the firewall loses it and can't get it back.

Of course I could be wrong. Has anybody else noticed this behavior?

[stueycaster]

It started working again without me changing anything. The only thing I did was restart my computer. It just seems to me like it's something about it taking time for the workgroup to get back together after it's been broken. Does that make sense?

[stueycaster]

I'm through trying to figure out what is wrong with this thing. I'll leave it up to the experts.

Today I came home from work, Started up the other computer, waited about 15 minutes then tried the view network thing. It didn't work.

I tried to call up the view workgroup link on the other computer and it didn't work.

Then I rebooted my computer and everything started working right again.

I guess I'll just wait til they fix it.

[Tunerz]

-{ Quote: "Please confirm or deny:
- Is the Trusted zone configured properly and all computers in your LAN are members of it?
- Does the problem perist no matter whether interactive or automatic mode is selected?
- Does disabling the firewall completely make a difference?
- Have you enabled logging of all blocked connections and no blocked connection appeared in the firewall log?
- Do you have another firewall installed?" }-

1. Yes
2. Yes
3. Yes
4. Yes, showing blocked connections
5. No

Switching to NOD32 v3+Windows XP firewall for a while, will be switching back if this issue is fixed.:-X

[mlapoint99]

I have the same problem, and assume that others have as well, as I have been communicating with Eset customer support for a week now on this issue. The only replies I have had request that I run hijackthis and Belard Advisor after telling me I am the only one with the problem.

Here's what I can add:

My home network: 1 laptop and 1 desktop networked wirelessly through a Dlink DI 614+ router (Question is anyone having this problem using a Dlink router)

There is also a wireless HP deskjet 6980 printer on the network. (Question: Is anyone having this problem using a wireless printer?)

The log file also says that ESS believes it is under an ARP attack from devices in the trusted zone. (the printer???)

For now, I have uninstalled ESS and installed NOD32 and Comodo firewall. Everything works great, however since I also have bought a 2 year subscription I need ESS to work reliably.

One final comment. I am sure that Eset customer support is overwhelmed with requests since they are in the midst of a major release, but replying to customers that have problems with inane computer generated answers 3 days after a service request was made is simply not acceptable. All customer support reps need to be made aware that this is an unresolved issue and inform the customer that they are working on it.

[stueycaster]

After copying the new dat file into the program file my View workgroup link works if I do the following:

Have the other computer turned on first. That computer is running ESET Antivirus ver. 3

Turn on this computer second. This one has ESS.

If this computer is already on when I turn that one on the workgroup won't show.

[Palombaro]

-{ Quote: "After copying the new dat file into the program file my View workgroup link works if I do the following:

Have the other computer turned on first. That computer is running ESET Antivirus ver. 3

Turn on this computer second. This one has ESS.

If this computer is already on when I turn that one on the workgroup won't show." }-

Does it continue to work over a matter of days?

[tosbsas]

where do one get the dat file??

Ruben

[dannyboy]

-{ Quote: "plus the worrying problem re: 'Bug? ekrn.exe can be terminated by users' which the forum seems to have gone quiet on, I will buy the full version but not until." }-


this is not a bug, it was possible with v2.7 too (and many other programs). It is down to the way Windows is designed, more than anything else.

[mlapoint99]

:thumbd: New version does not fix the problem.:thumbd:

I have 2 computers networked wirelessly through a router used for printer and file sharing and internet access.

I Installed ESS 3.0.566 on my laptop. The Desktop is running with NOD32 and Comodo firewall. The Desktop is already connected to the network and shares are available. The Laptop is then booted after the desktop is on the network. ESS works flawlessly for 2 hours.

I then disconnect the desktop from the network. I immediately check "View network computers". After a few seconds delay, the dreade "The network not accessible" message pops up on the laptop with ESS. I reconnect the desktop to the network. The laptop is still giving the network not accessible message. Shared folders on the desktop are however accessible from the laptop and ping works even if if view network computers says otherwise.

I guess we will need to wait for another release.

[kwg]

Ruben,
-{ Quote: "where do one get the dat file?" }-
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.

[tosbsas]

ok, thanks

Ruben

PS: kind of mixed info - does it help?

[kC_]

nope
.

[stueycaster]

-{ Quote: "Does it continue to work over a matter of days?" }-
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.

[tosbsas]

any chance to get that one too?

Ruben

[stueycaster]

-{ Quote: ":thumbd: New version does not fix the problem.:thumbd:

I have 2 computers networked wirelessly through a router used for printer and file sharing and internet access.

I Installed ESS 3.0.566 on my laptop. The Desktop is running with NOD32 and Comodo firewall. The Desktop is already connected to the network and shares are available. The Laptop is then booted after the desktop is on the network. ESS works flawlessly for 2 hours.

I then disconnect the desktop from the network. I immediately check "View network computers". After a few seconds delay, the dreade "The network not accessible" message pops up on the laptop with ESS. I reconnect the desktop to the network. The laptop is still giving the network not accessible message. Shared folders on the desktop are however accessible from the laptop and ping works even if if view network computers says otherwise.

I guess we will need to wait for another release." }-

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.

[Marcos]

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.

[kC_]

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

nothing logged as being blocked

[stueycaster]

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.

[stueycaster]

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

[Marcin_K]

-{ Quote: "I wonder if someone else could confirm or deny that the problem goes away after disabling all IDS rules." }-

I deny that.

[kC_]

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

[Marcin_K]

-{ Quote: ""view workgroup computers" is still functioning after 30mins" }-

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).

[kC_]

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

[stueycaster]

-{ Quote: "

I would really like to know how many of you view workgroup computers without any trouble (with ESS on board of course)." }-
This is definitely an ESS bug. If you read through the posts in this thread plus another thread there is a lot of detail.

http://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.

[kC_]

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!

[stueycaster]

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.

[kC_]

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:thumb:

[kC_]

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.

[Marcin_K]

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

[Palombaro]

-{ Quote: "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 .

[stueycaster]

-{ Quote: "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.

[Palombaro]

-{ Quote: "
Marcos has been in touch and I'm sure they're working on it now.

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

[Jacqui D]

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

[stueycaster]

-{ Quote: "Good news that they are still working on it. Has he been touch since the testing of the alternative .date file?" }-
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.

[stueycaster]

-{ Quote: "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" }-
When I reboot the computer with ESS while the other computer is running the view workgroup link starts working every time. The other computer has EAV. Then when the other computer is shut down the link fails again. This might be what is happening with yours. It might work when you reboot.

[Jacqui D]

-{ Quote: "When I reboot the computer with ESS while the other computer is running the view workgroup link starts working every time. The other computer has EAV. Then when the other computer is shut down the link fails again. This might be what is happening with yours. It might work when you reboot." }-

I have discovered that by unchecking and rechecking the Eset Firewall Port in my "Local Area Connections Properties" that I am able to view my workgroup computers always, regardless of whether the other workgroup computers are on or off. My concern is that I may have effectively disabled the firewall. That said, I seem to still get ESS ask permission for outbound connections etc., so maybe it is still functioning? Also when I re-check this option I get asked to install some software, as stated above, which I have elected to not install.

This is a link to the appropriate dialogue with the eset re-enabled, but without installing the software:
http://i.pbase.com/o3/78/186978/1/89532755.P5FlZ2EO.eset.jpg (you may have to copy/paste the link to see this image with some browsers. http://i.pbase.com/o3/78/186978/1/89532755.P5FlZ2EO.eset.jpg)

[stueycaster]

-{ Quote: "I have discovered that by unchecking and rechecking the Eset Firewall Port in my "Local Area Connections Properties" that I am able to view my workgroup computers always, regardless of whether the other workgroup computers are on or off. My concern is that I may have effectively disabled the firewall. That said, I seem to still get ESS ask permission for outbound connections etc., so maybe it is still functioning? Also when I re-check this option I get asked to install some software, as stated above, which I have elected to not install.

This is a link to the appropriate dialogue with the eset re-enabled, but without installing the software:
http://i.pbase.com/o3/78/186978/1/89532755.P5FlZ2EO.eset.jpg (you may have to copy/paste the link to see this image with some browsers. http://i.pbase.com/o3/78/186978/1/89532755.P5FlZ2EO.eset.jpg)" }-
I tried what you did and when I got the message about the installation it looked to me like it was important. I would think that it was installed before it was unchecked. I allowed it to install it. I've installed other software that called up the windows logo thing. I've never had any adverse effects that I noticed. My HP Printer called up a bunch of them.

You probably could wait for word from someone more knowledgable than me if you like. I just thought I'd tell you how I feel about it. I really think that thing needs to be installed.

[Palombaro]

Any chance of some input from ESET regarding a possible update to ESS fixing this problem. My 30 day trial is running out and if this problem is resolved when it does I would install ESS on all my computers at that time. Any news?

[kC_]

-{ Quote: "My 30 day trial is running out" }-

how is that true when only 3 days ago you stated http://www.wilderssecurity.com/showpost.php?p=1126065&postcount=96

if that were true & you really did a fresh instal you would have 26days + remaining.

i guess one of your posts is a fib;)

[Palombaro]

-{ Quote: "

i guess one of your posts is a fib;)" }-
Be careful when you accuse somebody of lying. Your 30 day trial starts from the day you first install ESS on your computer. Subsequent fresh installs change absolutely nothing. If it were any other way all we would have to do when our annual subscription was running out would be to uninstall, remove all obvious registry keys and folders and then reinstall and hey presto we have another year gratis. If only it were so. Think about it KC_ !!
An apology would be welcome

[kC_]

ah i see sorry, i thought it was 30 day from fresh.. well there is a 90 day trial offer here
https://www.betterantivirus.com/nod32-and-virus-news/archives/738-ESET-Smart-Security-Free-90-day-trial.html

would give you a bit more time

[Palombaro]

-{ Quote: "ah i see sorry, i thought it was 30 day from fresh.. well there is a 90 day trial offer here
https://www.betterantivirus.com/nod32-and-virus-news/archives/738-ESET-Smart-Security-Free-90-day-trial.html

would give you a bit more time" }-

Info and apology welcome and accepted

[Jacqui D]

-{ Quote: "I tried what you did and when I got the message about the installation it looked to me like it was important. I would think that it was installed before it was unchecked. I allowed it to install it. I've installed other software that called up the windows logo thing. I've never had any adverse effects that I noticed. My HP Printer called up a bunch of them.

You probably could wait for word from someone more knowledgable than me if you like. I just thought I'd tell you how I feel about it. I really think that thing needs to be installed." }-

Thanks for your advice. It certainly looks like it is something that needs to be installed, however the firewall seems to be working OK and I have total access to my workgroup computers by keeping that thing uninstalled. I am also behind a router with NAT/SPI/firewall etc. and until I got ESS I only had NOD32 antivirus and was running with the Windows firewall only.

Hopefully this matter will be resolved soon.

Again, many thanks for your input.

[stueycaster]

I hate to bring this up again but it didn't get fixed with version 3.0.621. It's still doing what it has always done.

When I turn off the other computer then restart it breaks the "View workgroup computers" link in "My Network Places". I get this Error Message:

"Mshome is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
The list of servers for this workgroup is not currently available."

Then if I restart this computer with the other one running it starts working again.

[Marcos]

-{ Quote: "I hate to bring this up again but it didn't get fixed with version 3.0.621. It's still doing what it has always done.

When I turn off the other computer then restart it breaks the "View workgroup computers" link in "My Network Places". I get this Error Message:

"Mshome is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
The list of servers for this workgroup is not currently available."

Then if I restart this computer with the other one running it starts working again." }-

If possible, could you try installing a different network card to see if it's releated somehow to its drivers? Maybe a partial interference occurs when ESS drivers are installed, but that's just a hunch.

[K1LL3M]

I see the same behaviour.

Networking works perfectly for about 30mins after a reboot. If I try to access the home network after this it is inaccessible.

[Palombaro]

-{ Quote: "If possible, could you try installing a different network card to see if it's releated somehow to its drivers? Maybe a partial interference occurs when ESS drivers are installed, but that's just a hunch." }-
If the problem is widespread it is very unlikely to be the fault of one particular network card. The problem is in the software.

[stueycaster]

-{ Quote: "If possible, could you try installing a different network card to see if it's releated somehow to its drivers? Maybe a partial interference occurs when ESS drivers are installed, but that's just a hunch." }-
Are all of us who are having this problem using the same Lan card? I guess that could be. I have an onboard Lan:

• Realtek® 8110S Dual layout
- Integrated Fast Ethernet MAC and PHY in one chip.
- Supports 10, 100Mb/s and Gb/s

If all the others have this then it's probably the problem. MSI is really bad about their software. I've bought my last MSI component because of it.

[kC_]

-{ Quote: "Are all of us who are having this problem using the same Lan card? " }-

at first i thought that aswel, but since i re-installed windows xp in november i havnt had the problem since. and thats the same OS/same hardware/same drivers.

give it a go, worked here

[stueycaster]

-{ Quote: "at first i thought that aswel, but since i re-installed windows xp in november i havnt had the problem since. and thats the same OS/same hardware/same drivers.

give it a go, worked here" }-
I'm thinking about doing that. The thing is I just did that a few months back. It wasn't because of ESS. It was because of my mistake with installing a second operating system on my computer. It didn't fix it back then but ESS was still in the beta stage.

The reason why I'm considering it is because this morning I uninstalled and reinstalled ESS 3 or 4 times. I did this because I have the "No System Tray Menu" thing too. I tried installers that I got from a couple different download pages. Now the interactive firewall has stopped asking about new application access. It's just allowing everything. I checked the controls and the applications are not set up to allow. I guess it's probably because of the registry. I could run a registry cleaner but I don't trust them. I used one in the past and it killed shortcuts to some of my System and Administrative Tools. I have version 2.7 installed now.

Boy do I hate the thought of reinstalling Windows again. Installing the updates, drivers and third party apps plus getting all the settings right takes a long time. The good thing is that it runs really sweet for quite a while afterward.

[tosbsas]

(;.)) Stuey, I know what you mean.

What I did was getting me TrueImage and make a ground system image - that way I only need to get windows updates and than the apps missing (:-))

Ruben

[stueycaster]

-{ Quote: "I'm thinking about doing that. The thing is I just did that a few months back. It wasn't because of ESS. It was because of my mistake with installing a second operating system on my computer. It didn't fix it back then but ESS was still in the beta stage.

The reason why I'm considering it is because this morning I uninstalled and reinstalled ESS 3 or 4 times. I did this because I have the "No System Tray Menu" thing too. I tried installers that I got from a couple different download pages. Now the interactive firewall has stopped asking about new application access. It's just allowing everything. I checked the controls and the applications are not set up to allow. I guess it's probably because of the registry. I could run a registry cleaner but I don't trust them. I used one in the past and it killed shortcuts to some of my System and Administrative Tools. I have version 2.7 installed now.

Boy do I hate the thought of reinstalling Windows again. Installing the updates, drivers and third party apps plus getting all the settings right takes a long time. The good thing is that it runs really sweet for quite a while afterward." }-
I forgot to mention something above. The fact that if I do reinstall and if it doesn't take care of it then I'm going to be ripping mad.

[stueycaster]

Boy do I feel like an idiot. I just discovered that even with Version 2.7 installed my "View workgroup computers" link fails when I turn off the other computer then turn it back on. Obviously it's not caused by ESS. I am sorry ESET.

The reason it always looked like it was working with Version 2.7 was because I always tried it after restarting this computer with the other one turned on. It always works when I do that.

Man I can't believe it. All these months I have been driving the good folks at ESET crazy over this and it isn't even their fault. I guess it's a Windows problem. Probably I don't have the network set up right.

Please accept my sincere apologies ESET.

[patch]

-{ Quote: "Boy do I feel like an idiot. I just discovered that even with Version 2.7 installed my "View workgroup computers" link fails when I turn off the other computer then turn it back on. Obviously it's not caused by ESS. I am sorry ESET.
" }-

Partly agree.
I think Microsoft's implementation on XP is fragile, but probably not the only cause of the problems.

Have been having a similar problem on LG P1 pro running XP for awhile. Seems to be made worse by simultaneously connecting cable and wireless (get name already registered error at times).

View work group computers stopped working on a second XP desktop machine recently (Intel PRO/100 VE Network connection). Seemed to correspond to upgrading to ESS. Makes me wonder about TCP stack corruption or similar.

Three other windows 2000 machines have no problems
Linked by billion 7402vgp router with latest firmware 5.52h1

stueycaster if you find a way of getting it working without a fresh XP install, let us / me know. I really don't want to go through all that.

[Palombaro]

-{ Quote: "Boy do I feel like an idiot. I just discovered that even with Version 2.7 installed my "View workgroup computers" link fails when I turn off the other computer then turn it back on. Obviously it's not caused by ESS. I am sorry ESET.
Please accept my sincere apologies ESET." }-

My experience is not the same as yours Stueycaster. Once all ESET products are uninstalled from all computers on the network the problem disappears and does not return i.e at least for me it is an ESET specific problem. Neither do I think it is a question of network cards. I have three computers on my network, 1 PC and two laptops . The PC is connected to the router by Ethernet cable, the two laptops by wifi but with different LAN cards. It doesn't matter which combination of the computers are on and connected to the network with ESS the problem remains. Remove ESS and the problem evaporates and does not return.
Though KC 's problems were solved by a reinstall of Windows I personally would not be too sure that that is the universal solution to the problem. Only time will tell but I am sceptical .
My hunch is that it is a ESS software problem. It is a pity because ESET products are always very good but they almost seem to be in denial about this problem.

[Clive T]

Add me to the list of unhappy networkers here. My configuration is just about the same as others who are having problems and I can't contribute any insights I'm afraid.

Back to v2.7. Problems disappear.

[Jacqui D]

Please add me to the list of networkers still unable to connect to My Workgroup Computers. I also notice an error 3019 in the event viewer which seems to be connected to this issue. According to MS (http://support.microsoft.com/default.aspx?kbid=315244) this has something to do with loopback adapter using TCP/IP. The only workaround that works solidly for me is to uncheck the "Eset Personal Firewall" under the properties of my Local Area Connection and then recheck the option and opt to not install the ESET unsigned software.

I am on Win XP x64 / Broadcom NetXtreme 57xx 10/100/1GB adapter.

Jacqui

[stueycaster]

-{ Quote: "Boy do I feel like an idiot. I just discovered that even with Version 2.7 installed my "View workgroup computers" link fails when I turn off the other computer then turn it back on. Obviously it's not caused by ESS. I am sorry ESET.

The reason it always looked like it was working with Version 2.7 was because I always tried it after restarting this computer with the other one turned on. It always works when I do that.

Man I can't believe it. All these months I have been driving the good folks at ESET crazy over this and it isn't even their fault. I guess it's a Windows problem. Probably I don't have the network set up right.

Please accept my sincere apologies ESET." }-
I think I'm driving myself crazy over this crap. When I tested the workgroup link with 2.7 installed I forgot to allow time for it to show back up on the network. It's working fine with 2.7 installed. Obviously ESS is still the culprit. Sorry about the above post. It was wrong.

[stueycaster]

Bear with me guys. I've found that I get too freaked out if something isn't working right on my computer. I need to lighten up a little. Sorry about the flip flopping. Like I said "freaked out".

One good thing came from this. I found that my network is set up right.

[stueycaster]

-{ Quote: "Please add me to the list of networkers still unable to connect to My Workgroup Computers. I also notice an error 3019 in the event viewer which seems to be connected to this issue. According to MS (http://support.microsoft.com/default.aspx?kbid=315244) this has something to do with loopback adapter using TCP/IP. The only workaround that works solidly for me is to uncheck the "Eset Personal Firewall" under the properties of my Local Area Connection and then recheck the option and opt to not install the ESET unsigned software.

I am on Win XP x64 / Broadcom NetXtreme 57xx 10/100/1GB adapter.

Jacqui" }-
Jacqui buddy you are really freaking me out with that. I think that's uninstalling the ESET driver. Sure, the GUI will look good but it probably won't block intrusion or viruses. But, I may be wrong.

[Jacqui D]

-{ Quote: "Jacqui buddy you are really freaking me out with that. I think that's uninstalling the ESET driver. Sure, the GUI will look good but it probably won't block intrusion or viruses. But, I may be wrong." }-

No problem, the firewall is detecting and blocking outbound connections as expected and I am also behind a NAT router with SPI firewall (DLINK DIR655 n) w/WPA2 personal. I never had a "proper" s/w firewall before ESS since they have only recently become available for 64-bit. NOD 2.7 is all I have ever used in conjunction with the windows firewall.

Coupled with safe computing practices, I have had no issues thus far, but it would be nice if Eset could focus on this issue and get it sorted.

Jacqui

[patch]

I think we have a Browser service problem
Description of operation http://support.microsoft.com/kb/188001
Trouble shooting http://support.microsoft.com/kb/188305

For better but non-Microsoft information see
Description http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html
Trouble shooting http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html
And http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Browser

For me when it's not working, "browstat status" run on computer1 shows
Status for domain HOME on transport \Device\NetBT_Tcpip_{...41}
Browsing is NOT active on domain.
Master browser name is held by: computer1
Master browser is running build 2600

Similarly from computer2, "browstat status" shows
Status for domain HOME on transport \Device\NetBT_Tcpip_{...47}
Browsing is active on domain.
Master browser name is: computer1
Master browser is running build 2600
1 backup servers retrieved from master computer1
\\computer1
There are 1 servers in domain HOME on transport \Device\NetBT_Tcpip_{...47}
There are 0 domains in domain HOME on transport \Device\NetBT_Tcpip_{...47}

Which I figure is not correct. With some playing with parameters & restarting it worked (Computer2 became the Browser server). Not sure if I have fixed anything but can now see the problem.

[stueycaster]

-{ Quote: "No problem, the firewall is detecting and blocking outbound connections as expected and I am also behind a NAT router with SPI firewall (DLINK DIR655 n) w/WPA2 personal. I never had a "proper" s/w firewall before ESS since they have only recently become available for 64-bit. NOD 2.7 is all I have ever used in conjunction with the windows firewall.

Coupled with safe computing practices, I have had no issues thus far, but it would be nice if Eset could focus on this issue and get it sorted.

Jacqui" }-
Ok Jacqui buddy. I'll leave you alone over it now. :thumb:

[pomocnik]

i have same problem

1. Yes
2. Yes
3. Yes
4. -
5. No.


i use XP SP2

[Jacqui D]

-{ Quote: "I think we have a Browser service problem" }-

For sure this is a fact. The Computer Browser service on our computers is fouled up by the ESS firewall. I have always had the Computer Browser service disabled on the other computers except my main system on my network because there were always master browser election issues. I have always been able to "see" those computers under "view workgroup computers" until I installed the ESS software.

The problem is identifying the cause vs. the symptoms. That problem lies with ESET.

For now, I am through dabbling with this issue since I will probably end up breaking my system altogether:(

Jacqui

[stueycaster]

I found a way that I can get around this bug. It'll work for me because I have EAV 3 on the other computer. On this computer I went into Administrative Tools/Services and set Computer Browser to disabled and stopped the service. Now the other computer can keep track of the workgroup since it doesn't have the ESS Firewall to mess it up. It seems to be working.

ESET still needs to fix this. At some point I plan to buy myself a laptop. When that happens I will definitely want this computer to keep track of the workgroup since it stays on all the time.

Update: I need to say thanks to Jacqui and Patch. I didn't know about Computer Browser til you guys pointed it out here.

[Palombaro]

I would like to know whether ESET are working on this issue and whether or not they are now giving it some priority.

[stueycaster]

-{ Quote: "I would like to know whether ESET are working on this issue and whether or not they are now giving it some priority." }-
Some time soon after Christmas I plan to send an instant message to Marcos with this new information. I don't want to bother anybody with it on Christmas Eve though. I'm sure they have been working hard on this and deserve the holiday.

I would imagine that the reason it didn't get fixed with version 621 is because this is really kind of separate from the network problems that others have. Does that make sense? I don't know. I'm just a computer geek wannabe. This is just a hobby for me. Anyway, like Jacqui said, it looks like the Computer Browser Service is what is being affected by the firewall. Whenever the other computer shut down this computer would elect itself Master Browser but failed because of the firewall. Then when this computer shut down the other one elected itself Master and it worked because it has EAV. I shut down the service in this computer and the issue went away.

I'd suggest this. If you're behind a router firewall and you have a computer that handles no sensitive info install EAV on it, leave the Computer Browser Service running and leave the computer on all the time. Then shut off the Computer Browser Service in all the ESS computers. Leave it like that til ESET fixes this issue. It really is working for me.

[stueycaster]

Boy do I ever feel ignored. I just read this:

http://www.eset.com/support/news.php

I don't see where there is any mention of Home Network problems at all. Maybe they're supposed to be part of those issues that did get fixed but this didn't. I guess it's difficult to fix this one so they put it off because they needed to get version 621 out before Christmas. I hope that's all it is because I really do feel ignored.

I've started three threads about this. I've been complaining about it since 9/21. There have been 188 replies and 7,015 views on them. I've also been one of their biggest supporters in this forum.

If I didn't feel like this program will soon be the best thing on the market i'd go get myself another product. I really am pissed.

[stueycaster]

I think I know why they haven't put much effort into fixing this issue. It's too easy to work around the problem and it's not system threatening or anything like that. That doesn't make me feel any better about it though. It's just that I've put so much time and effort into it.

[kC_]

-{ Quote: "It's just that I've put so much time and effort into it." }-
have you tried re-installing windows?

[stueycaster]

-{ Quote: "have you tried re-installing windows?" }-
That will be a last ditch effort kC my friend. It's just that it really does work right with Ver. 2.7. Plus now that I've set up this computer to always allow the other computer to be the Master Browser it's working fine. I just think that ESET didn't try hard enough on this.

There may come a day when I reinstall Windows but I have to try everything else first. I appreciate your concern. Thank you.

[kC_]

sorry its just you said "time & effort"

[stueycaster]

No problem kC buddy. I was talking about the time and effort I've put into this thread and researching possible fixes for this problem and stuff like that. I've been dealing with this for 3 months now. Oh well.

Merry Christmas :)

[kringles]

@stueycaster $ kC_
Re install (restoring to a fresh install using Acronis TI) on my three PCs (1 Vista other 2 XP) did not help. The only solution in my case was to remove ESS from all three PCs. My problem may be slightly different in apprearance. After the initial install of ESS on all three PCs network is ok for several hours. Then without any apparent reason ( no reboots etc.) the Vista PC cannot 'see' the other PCs. The two XP PCs can 'see' each other and the
Vista PC. Remove ESS all ok.

Then installed latest version of Comodo Firewall 3.0 on all three PCs with NOD 32 V 3.0. Have been running for a day with no network problems.

My conclusion is that ESS is the problem in this case. Have not given up yet but maybe I will get to like this Comodo product enough to stick with it instead of ESS.

Merry Christmas & Happy Holidays
kringles

[stueycaster]

-{ Quote: "@stueycaster $ kC_
Re install (restoring to a fresh install using Acronis TI) on my three PCs (1 Vista other 2 XP) did not help. The only solution in my case was to remove ESS from all three PCs. My problem may be slightly different in apprearance. After the initial install of ESS on all three PCs network is ok for several hours. Then without any apparent reason ( no reboots etc.) the Vista PC cannot 'see' the other PCs. The two XP PCs can 'see' each other and the
Vista PC. Remove ESS all ok.

Then installed latest version of Comodo Firewall 3.0 on all three PCs with NOD 32 V 3.0. Have been running for a day with no network problems.

My conclusion is that ESS is the problem in this case. Have not given up yet but maybe I will get to like this Comodo product enough to stick with it instead of ESS.

Merry Christmas & Happy Holidays
kringles" }-
I keep thinking that they'll have to fix this thing at some point. It's definitely a bug in their software. The number of times this thread has been viewed says that a lot of people know about it too. That's bad for public relations.

[Jenee]

I also have the same problem and other computers in my network cannot access my computer (my computer is the only one so far with ESS as the firewall).
The only way I have found to get around it is to go through the network setup wizard again on my pc, restart my pc and then the network works fine. I have to do this each day.

[stueycaster]

-{ Quote: "I also have the same problem and other computers in my network cannot access my computer (my computer is the only one so far with ESS as the firewall).
The only way I have found to get around it is to go through the network setup wizard again on my pc, restart my pc and then the network works fine. I have to do this each day." }-
By "cannot access my computer" do you mean that the other computers can't access the shares or can't access your computer through the "View workgroup computers" link. If they can't access the shares I don't know what to tell you. Sorry. But if the workgroup link is at fault maybe this will help.

In post #128 on this page Patch pointed out some articles about the relationship of computers on a network. Maybe I can save you from having to read all that.

It seems that one of the computers has to be the "Master Browser". That computer maintains a list of the computers on a workgroup and the shares on each one. The one with the most uptime gets chosen for that responsibility. The firewall in ESS somehow stops that computer from being able to do this.

If that computer gets turned off then one of the others will take on the responsibility. This is why restarting the ESS computer fixes the problem. I was able to get around this problem by doing this:

Go to Control Panel/Administrative Tools/Services. Find "Computer Browser" and double click it. Set "Startup Type" to Disabled. In "Service status" click Stop. Click Apply.

Now that computer can never be the master browser. It worked for me. I don't have the problem any more. Once ESET fixes the problem I'll set this computer to allow the service again.

[Jenee]

I installed the latest version 621 and I no longer have any problems with the network now. It all works fine. This new version seems to have sorted it out very well.

[spiritfly]

-{ Quote: "I installed the latest version 621 and I no longer have any problems with the network now. It all works fine. This new version seems to have sorted it out very well." }-

Idon't think so. I have just installed it on one of my machines and as soon as I installed it, the pc cannot see itself in the network, nor can other pcs see it.I had another ESS on my main pc, but that is the case with it also.

At first I never really doubted ESS, so I searched through google about it and I found a strange problem being solved by installing the NETBEUI. I tried that and somehow it worked on my main pc! I did that right away with my second one and it did not worked. Then I read some more about this NETBEUI protocol and it said that it doesn't apply at my case(a home network behind a router with hardware firewall linksys). And at the end I simply uninstalled ESS and everything started working perfectly.

[Palombaro]

Though all the methods that people are using may be helpful , in the final analysis the problem clearly lies with ESS. It is far too widespread to be dismissed as a 'rogue' network card or a need to reinstall Windows on a computer which is some way compromised. It's a software bug and ultimately it is one that ESET will have to resolve.

[Jenee]

-{ Quote: "Idon't think so. I have just installed it on one of my machines and as soon as I installed it, the pc cannot see itself in the network, nor can other pcs see it.I had another ESS on my main pc, but that is the case with it also.

At first I never really doubted ESS, so I searched through google about it and I found a strange problem being solved by installing the NETBEUI. I tried that and somehow it worked on my main pc! I did that right away with my second one and it did not worked. Then I read some more about this NETBEUI protocol and it said that it doesn't apply at my case(a home network behind a router with hardware firewall linksys). And at the end I simply uninstalled ESS and everything started working perfectly." }-

When I was having the network issue, I used to run the network setup wizard and that would fix the problems until the pcs were restarted. I had run this just before I installed V621 so perhaps that is why I no longer have any problems. Perhaps you could try running the network setup after installing ESS again and see if that works.

[patch]

Still not working for me using:
ESS 3.0.621.0 Modules current as of 30/12/2007.
--Configured default (firewall automatic filtering) with uPnP & full logging enabled
Windows XP Professional, current updates
Local computers on a wired network behind a Billion 7402vgp NAT & local DNS
Note also have Windows 2000 machines, and "View workgroup computers" work properly when one of them is the "Master browser"

With ESS installed on XP computer Computer1 get from computer1 :(
>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : Computer1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
Physical Address. . . . . . . . . : 00-07-E9-82-A7-94
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
Lease Obtained. . . . . . . . . . : Sunday, 30 December 2007 11:47:05 AM
Lease Expires . . . . . . . . . . : Sunday, 30 December 2007 11:47:05 PM

>browstat status
Status for domain HOME on transport \Device\NetBT_Tcpip_{6B9AFBD2-4C18-4524-8AAF
-5A0FC9157641}
Browsing is NOT active on domain.
Master browser name is held by: Computer1
Master browser is running build 2600

Un-installing ESS.
Switching off all computers.
Starting up Computer1 then others (to ensure computer 1 is master browser)
"View workgroup computers" work properly :) and
>browstat status
Status for domain HOME on transport \Device\NetBT_Tcpip_{6B9AFBD2-4C18-4524-8AAF -5A0FC9157641}
Browsing is active on domain.
Master browser name is: Computer1
Master browser is running build 2600
1 backup servers retrieved from master Computer1
\\Computer1
There are 1 servers in domain HOME on transport \Device\NetBT_Tcpip_{6B9AFBD 2-4C18-4524-8AAF-5A0FC9157641}
There are 1 domains in domain HOME on transport \Device\NetBT_Tcpip_{6B9AFBD 2-4C18-4524-8AAF-5A0FC9157641}

Re-installing ESS.
Without restarting any computers
"View workgroup computers" stops working :( and
>browstat status
Status for domain HOME on transport \Device\NetBT_Tcpip_{6B9AFBD2-4C18-4524-8AAF -5A0FC9157641}
Browsing is NOT active on domain.
Master browser name is held by: Computer1
Master browser is running build 2600

Note
Ipconfig /all does not change significantly with above testing.
Running Network setup wizard makes no difference to the above results.
Used regedit to clear all entries with "ESET", including in above example prior to reloading ESS

[stueycaster]

I don't think anybody is saying that ESET isn't responsible for fixing this.

[stueycaster]

-{ Quote: "When I was having the network issue, I used to run the network setup wizard and that would fix the problems until the pcs were restarted. I had run this just before I installed V621 so perhaps that is why I no longer have any problems. Perhaps you could try running the network setup after installing ESS again and see if that works." }-
I've done that. It didn't fix mine. It's ok. Like I've been saying for the last three months, I'm sure they'll fix it sometime.

[sangam]

i have had the same problem you report. i feel that stueycaster, is correct in pinpointing the source of the issue, & that shutting computer browser service to off on ess machine, should temporarily, solve this. however need to verify this, yet.

[kringles]

The problem is I have three licenses (one for each PC, 2 XP, ! Vista) and i wish to run ESS on all three. Should computer browser be turned of for all three? Would networking work then? The PCs are being used a lot, maybe during a lull I can reinstall ESS 621 again and play around some.
Happy New Year!

[stueycaster]

-{ Quote: "The problem is I have three licenses (one for each PC, 2 XP, ! Vista) and i wish to run ESS on all three. Should computer browser be turned of for all three? Would networking work then? The PCs are being used a lot, maybe during a lull I can reinstall ESS 621 again and play around some.
Happy New Year!" }-
You'd have to run EAV or Nod32 on one of them. The one that's not going to handle any sensitive data like bank numbers. Then leave that one on all the time or at least be sure it is on whenever you need to access the network. Leave Computer Browser enabled on that one. Then It will always be Master Browser.

It won't work with ESS on all three. The firewall seems to disable the Computer Browser Service. You can run EAV or Nod32 on an ESS license.

This isn't ideal but it should work til ESET fixes the problem.

Thank Patch and Jacqui for the info about the Computer Browser Service.

[Jenee]

I have the problem back again after installing ESS on the rest of the PCs in my network. No matter what I do, nothing will work, even the suggestion re master browser.

[patch]

-{ Quote: "i wish to run ESS on all three. Should computer browser be turned of for all three? Would networking work then? " }-
That would guarantee Browser services were never available, so no. What you want is Browser services running on at least one computer able to act as a functional master browser (the voting should then ensure exactly one is the master browser). A computer running nod32 instead of ESS is an option ATM. My windows 2000 machines running ESS also work for me.

-{ Quote: "I have the problem back again after installing ESS on the rest of the PCs in my network. No matter what I do, nothing will work, even the suggestion re master browser." }-

The master browser service lets you browse the network.
You do not need it if you just want to access network resources.

Got to "My Network places", select "Add a new network place"
If browser services are up ATM then browse to the network resource / computer you want future access to.
If browser services are not functioning, just type in the full path name.

From then on just use the created network shortcut, which will work independent of browser services.

BTW
I wonder if the fact not all users have problems is the different protocols used in legacy systems without a domain name controller.

Edit
If you want to know which computers are / are not properly functioning master browsers on you network then load browstat http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html on your computers and run "browstat status" from a cmd window when the browser services are / are not functioning.
The master browser will depend on which computers were online when the election last occurred (which you can control by switching computers off).
You can then force the election to a favourable outcome by switching off browser services on those computers it doesn't work on (provided you end up with browser services enabled and working on at least one powered up computer).

[sangam]

-{ Quote: "BTW
I wonder if the fact not all users have problems is the different protocols used in legacy systems without a domain name controller." }-

no domain controllers, where i have experienced this problem.

[stevenoon]

I have been having the same problem on and off for a couple of weeks at least. Uninstall / reinstall of ESS seems to temporally resolve the issue. I am unable to browse the workgroup in Network Places (XP Pro SP2) and also receive an error message about failed drive mappings when I log in.

Steve.

[Jenee]

I re-established all the shares on each PC in my network and, although I can't view the computers, each PC can now see and access all the shares so this suits me fine as the share access was all that was accessible through the PCs showing up in the network anyway. I can probably live with this.

[Palombaro]

-{ Quote: "I re-established all the shares on each PC in my network and, although I can't view the computers, each PC can now see and access all the shares so this suits me fine as the share access was all that was accessible through the PCs showing up in the network anyway. I can probably live with this." }-But if we are paying should we have to live with a bug that ESET have known about for some time. I can't help think that they have just given up on the problem.
Some feedback from ESET on the work put in by Patch and Jacqui on the browser line would at least give us some hope.

[stueycaster]

-{ Quote: "But if we are paying should we have to live with a bug that ESET have known about for some time. I can't help think that they have just given up on the problem.
Some feedback from ESET on the work put in by Patch and Jacqui on the browser line would at least give us some hope." }-
Agreed, Some feedback from ESET would be nice. I've started three different threads about this. I've been complaining about this since Sep. 24. Marcos dropped in and asked a few questions. Other than that I haven't heard a thing. I'm getting sick of waiting.

The only thing that keeps me holding on is the fact that other than this ESS is working great for me. The workaround that I mentioned in previous posts is working fine. But then my network has only two computers. Also there is all the bad stuff I've read about other products. You should pop into the forums of the other guys. People have lots of problems with their stuff too. One that struck me was this guy complaining to Kaspersky about the fact that their scanner took twice as long as the scanner in Nod32.

Look at the number of views on this thread. Over the past three months there have been 8,275 views on all three of the threads I started. Too many people know about their screwup for them to ignore. Besides, selling a faulty firewall and then not trying to fix it is pretty unethical. They'll fix it. They have to.

[Jenee]

When I started the network today, 2 of the PCs could see each other in Network Places but not the third PC and only one of those PCs could see any shares on the third PC. The third PC could not see any PCs in Network Places but could see only one share on one other PC. It really is weird.
My network uses 192.168.0.0 so can anyone tell me why ESS has IP:127.0.0.1 as the trusted zone address with a subnet of 192.168.0.0.
I deleted the reference to 127.0.0.1, added an address range of 192.168.0.0 to 192.168.0.50. Then I ran the network setup wizard again, restarted the PC and after restarting, ESS popped up a box asking for selection on Network access (file sharing or no access). I selected file sharing and now all PCs can seel all other PCs in Network Places. I don't know if it will still be fixed when the network is started tomorrow but here's hoping.
I did note that in the trusted zone in ESS it has added back the IP:127.0.0.1???

[Palombaro]

-{ Quote: "
The only thing that keeps me holding on is the fact that other than this ESS is working great for me. The workaround that I mentioned in previous posts is working fine. But then my network has only two computers. Also there is all the bad stuff I've read about other products. You should pop into the forums of the other guys. People have lots of problems with their stuff too. ." }-

Ditto. On the one hand, ESET do rather have a tendency to treat the problems that customers report less urgently than they merit. Also some of the technical feedback and analytical work that some of the more technically savvy contributors to this forum do often appears to be greeted with indifference by ESET.
On the other hand they do have a history of producing high quality reliable products and you have to hope that that will be the case with ESS.
I guess ESET's company motto is 'IN OUR OWN TIME' !

[stueycaster]

-{ Quote: "When I started the network today, 2 of the PCs could see each other in Network Places but not the third PC and only one of those PCs could see any shares on the third PC. The third PC could not see any PCs in Network Places but could see only one share on one other PC. It really is weird.
" }-
On my computer "My Network Places" seems to lose some of the shares too. I think it loses the ones that I don't use often. That's why I need for the "View workgroup computers" link to work properly.

-{ Quote: "I'd suggest this. If you're behind a router firewall and you have a computer that handles no sensitive info install EAV on it, leave the Computer Browser Service running and leave the computer on all the time. Then shut off the Computer Browser Service in all the ESS computers. Leave it like that til ESET fixes this issue. It really is working for me." }-
This should help. Of course I can't guarantee anything. Your computer is set up differently than mine.

[patch]

-{ Quote: " It really is weird.
My network uses 192.168.0.0 so can anyone tell me why ESS has IP:127.0.0.1 as the trusted zone address with a subnet of 192.168.0.0.
" }-
I believe you will find 127.0.0.1 is a way for the computer to refer to itself. So it is needed for local communication within each computer.

-{ Quote: "When I started the network today, 2 of the PCs could see each other in Network Places but not the third PC and only one of those PCs could see any shares on the third PC. The third PC could not see any PCs in Network Places but could see only one share on one other PC. It really is weird. " }-
I suggest running "browstat status" as described earlier. It made random failures much less random for me.

For example I found one of my machines was not allowing Anonymous access, which is what each computer tries to do when accessing the master browser. Fixed in regedit
[HKLM \System \CurrentControlSet \Control \Lsa]
server must have a restrictanonymous value of "0

Look also at node type, which must not be type 2 peer-peer
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters\DHCP Node Type]
Value Node Type
1 Broadcast.
2 Peer-Peer.
4 Mixed.
8 Hybrid.

Use of NetBIOS Over TCP/IP (NetBT) needs to be consistent between machines otherwise only some machines will see the Master browser See http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html
Check Network connections --> Local area network connection --> Properties --> Internet Protocol (TCP/IP) --> Properties --> WINS

The important point being, while we know ESET have a problem with "View workgroup computer", the protocol Microsoft use is not particularly robust, so you may have some additional issues with your network.

BTW
I suspect it is the permutations of "NetBT" & "Direct hosted SMB" occurring in mixed environments that causes the ESS browser bug.

[senorvivo]

Having the same problem . Any news of a solution from ESET?

[hirudoid2]

I am still hoping for a solution. My license expires December 2008. Even a short message that they are working to solve it or that they cannot solve it would be better, I could then move on to an other security suite.
??? :o

[Jenee]

I am beginning to think that only being able to view shares is the way Eset designed the program. The wording relating to local networks always seems to refer to shared resources rather than computers. I previously said I could get by with just seeing shared resources but the problem is, it is erratic and not all shares are accessible at any one time.

[senorvivo]

-{ Quote: "I am beginning to think that only being able to view shares is the way Eset designed the program. The wording relating to local networks always seems to refer to shared resources rather than computers. I previously said I could get by with just seeing shared resources but the problem is, it is erratic and not all shares are accessible at any one time." }-

Isn't it time somebody working for ESET said something authoritative on the matter?

[Bubba]

-{ Quote: "Isn't it time somebody working for ESET said something authoritative on the matter?" }-Through out this thread Marcos (http://www.wilderssecurity.com/member.php?u=1860) has asked numerous questions of users concerning this issue and while I might have over looked some answers to his questions by users, I do not see much feedback to his questions.

I'll list them below and if users with this problem would assist by answering some or all of his questions it might help with this matter.

* "If possible, could you try installing a different network card to see if it's releated somehow to its drivers? Maybe a partial interference occurs when ESS drivers are installed, but that's just a hunch."

* "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"

* "Do all of you use a 1GB NIC and switching it to 100mps mode helps?"

* "what OS are you running? (32 or 64-bit?)
- has someone observed this problem also with EAV?

* "- Is the Trusted zone configured properly and all computers in your LAN are members of it?
- Does the problem perist no matter whether interactive or automatic mode is selected?
- Does disabling the firewall completely make a difference?
- Have you enabled logging of all blocked connections and no blocked connection appeared in the firewall log?
- Do you have another firewall installed?"

[Marcos]

Stueycaster mentioned that after disabling the Computer browser service it worked fine. Maybe you could try the same and let us know about the result. Is one computer running ESS and the other EAV or what configuration do you use?

[senorvivo]

-{ Quote: "Through out this thread Marcos (http://www.wilderssecurity.com/member.php?u=1860) has asked numerous questions of users concerning this issue and while I might have over looked some answers to his questions by users, I do not see much feedback to his questions.

[/I]" }-

Just not true Bubba. There has been a lot of specific feedback to Marcos' questions. I suggest you look again

[Bubba]

-{ Quote: "Just not true Bubba. There has been a lot of specific feedback to Marcos' questions. I suggest you look again" }-Yes, there has been some feedback from users but in particular I was looking at the 3 posts you have made since joining but see no feedback. If Eset is expected to work thru this issue, they then need as much user input that they can get in order to attempt to duplicate this matter. Of course I am assuming from your first post yesterday you have this issue and would hope you wouldn't mind offering as much info as you can according to the questions asked by Marcos.

Bubba

[stueycaster]

-{ Quote: "Stueycaster mentioned that after disabling the Computer browser service it worked fine. Maybe you could try the same and let us know about the result. Is one computer running ESS and the other EAV or what configuration do you use?" }-
My computer has ESS and my wife's computer has EAV. On my computer I went into Administrative Tools/services.msc. Under "Computer Browser" I set "Startup Type" to disabled and "service status " I clicked stop. I made no changes on her computer. Since then I haven't had a single problem with the view workgroup link.

I don't have access to another LAN card.

I can check out the other questions tomorrow evening when my wife is at work. She's using her computer now.

I haven't checked out anything else in quite a while. Since I applied the Computer Browser thing it's been working right.

[sherryxp2000]

I too OCCASIONALLY get the View Workgroup computers error. I had been doing a power down, and just hoped it worked when I turned the machine back on. Sometimes it did, sometimes not.

Now what I have done, is I ran the Network ID wizard. I have NEVER run this before as I always setup my network manually. Anyways I tried the Netword ID Wizard out of curiousity while I had the error.

After the process and a reboot, everything has worked fine for the last 3 days.

If I lose my Workgroup again, I'll make a post.

[Jenee]

-{ Quote: "I too OCCASIONALLY get the View Workgroup computers error. I had been doing a power down, and just hoped it worked when I turned the machine back on. Sometimes it did, sometimes not.

Now what I have done, is I ran the Network ID wizard. I have NEVER run this before as I always setup my network manually. Anyways I tried the Netword ID Wizard out of curiousity while I had the error.

After the process and a reboot, everything has worked fine for the last 3 days.

If I lose my Workgroup again, I'll make a post." }-

How many computers in your network and did you run the wizard on all of them?

[Jenee]

I'll list them below and if users with this problem would assist by answering some or all of his questions it might help with this matter.

* "If possible, could you try installing a different network card to see if it's releated somehow to its drivers? Maybe a partial interference occurs when ESS drivers are installed, but that's just a hunch."

I have 3 PCs in my network all with different network cards.

* "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"

No the problem does not go away

* "Do all of you use a 1GB NIC and switching it to 100mps mode helps?"

two NICs are 100mps and one is 1GB and all PCs have the problem

* "what OS are you running? (32 or 64-bit?)

All OSs are WinXP Pro


* "- Is the Trusted zone configured properly and all computers in your LAN are members of it?

Yes

- Does the problem persist no matter whether interactive or automatic mode is selected?

Yes

- Does disabling the firewall completely make a difference?

Yes

- Have you enabled logging of all blocked connections and no blocked connection appeared in the firewall log?

I am not sure if this is relevant but one PC has the following logged "Detected Reverse TCP DeSynchronisation attack" with the source IP being itself and the target IP being another PC in the network

- Do you have another firewall installed?"

No

[sherryxp2000]

-{ Quote: "How many computers in your network and did you run the wizard on all of them?" }-

There are 3 PC's in my network, and plus random other PC's that I take in for repair work that I do at home. So always a mix of network cards, and a mix of AV programs.

The only computer I ran the wizard on was the one that contained ESET EAV.

The other two PC's have different AV.

[sherryxp2000]

The problem reappeared just this moment work group error. So the Network ID Wizard did nothing to fix the problem on the machine with ESET suite.

[kwg]

Here's an experiment I have tried:

1. Disconnect all other computers from the network. Keep this computer, running ESS, connected.

2. Reboot this computer.

3. Restart the Computer Browser service.

4. View Workgroup Computers.

After several seconds, I receive this message: "The list of servers for this network is not currently available."

When this computer is the only computer on the network, shouldn't this computer be able to see itself?

When I uninstall ESS, the network behaves normally, no matter how many computers are connected to the network.

[sherryxp2000]

-{ Quote: "Here's an experiment I have tried:

When this computer is the only computer on the network, shouldn't this computer be able to see itself?

When I uninstall ESS, the network behaves normally, no matter how many computers are connected to the network." }-

I can vouch for that, I turned all my other PC's off, and my computer can NOT see itself either. (the one with ESS)


My other computers when on by theirselves, always see theirself. (all have non-ESS AV suites)

[Marcos]

We've been trying to replicate this problem to no avail. If there was a problem viewing network computers it persisted even after uninstalling ESS. If you uninstall ESS, I gather the function in question begins working properly, right?

[kwg]

-{ Quote: "We've been trying to replicate this problem to no avail. If there was a problem viewing network computers it persisted even after uninstalling ESS. If you uninstall ESS, I gather the function in question begins working properly, right?" }-

Marcos, the problem persists as long as ESS is installed. As soon as I uninstall ESS, the network returns to normal.

[stueycaster]

Marcos,
Did you try to restart the EAV computer with the ESS computer already running. The problem with the "View workgroup computers" link is one that comes and goes according to these circumstances. On my 2 computer network the one with ESS worked correctly if it was started with the other computer already running. Then as soon as the other computer (the one with EAV) is restarted the view workgroup link fails.

I see it this way. when the ESS computer is started with the other computer already running the other one has already assumed the position of Master Browser and the workgroup link works correctly. Then when you restart the computer with EAV the one with ESS tries to assume master and fails because something in the firewall stops it.

Now since I've disabled the ESS computer from being able to assume Master the EAV computer always takes the responsibility. My view workgroup link always works correctly.

I hope that all makes sense. It's really hard to explain.

[Jenee]

-{ Quote: "Marcos,
Did you try to restart the EAV computer with the ESS computer already running. The problem with the "View workgroup computers" link is one that comes and goes according to these circumstances. On my 2 computer network the one with ESS worked correctly if it was started with the other computer already running. Then as soon as the other computer (the one with EAV) is restarted the view workgroup link fails.

I see it this way. when the ESS computer is started with the other computer already running the other one has already assumed the position of Master Browser and the workgroup link works correctly. Then when you restart the computer with EAV the one with ESS tries to assume master and fails because something in the firewall stops it.

Now since I've disabled the ESS computer from being able to assume Master the EAV computer always takes the responsibility. My view workgroup link always works correctly.

I hope that all makes sense. It's really hard to explain." }-

I am not sure I agree with this. The computer in my network that is always the master browser (I don't know why and have not been able to change it) could not view workgroup computers even before ESS was installed on it but I had started another PC that did have ESS installed.
In one of my posts above I detailed a block that is appearing on the computer that is the master browser and this may also have something to do with the problem.

"I am not sure if this is relevant but one PC has the following logged "Detected Reverse TCP DeSynchronisation attack" with the source IP being itself and the target IP being another PC in the network"

This message appears on the PC which is master browser when it is started first and then another PC is started.

[sherryxp2000]

-{ Quote: "We've been trying to replicate this problem to no avail. If there was a problem viewing network computers it persisted even after uninstalling ESS. If you uninstall ESS, I gather the function in question begins working properly, right?" }-

Yes, that's the case for me.

[Jacqui D]

-{ Quote: "Marcos, the problem persists as long as ESS is installed. As soon as I uninstall ESS, the network returns to normal." }-

Same here.

In addition, the following is logged in the ESET personal firewall log which I believe has something to do with this issue:

1/10/2008 7:14:02 PM No usable rule found 192.168.0.254 224.0.0.22 IGMP
1/10/2008 7:14:01 PM No usable rule found 192.168.0.254 224.0.0.22 IGMP

192.168.0.254 is my computer and I have no idea what the 224.0.0.22 target is.

Jacqui

[stueycaster]

Has anybody tried to disable the "Computer Browser" service in your ESS computer with EAV or Nod32 on another one to see if it helps?

[sherryxp2000]

-{ Quote: "Has anybody tried to disable the "Computer Browser" service in your ESS computer with EAV or Nod32 on another one to see if it helps?" }-

Yes I tried that, but it didn't seem to make a difference.

[sherryxp2000]

I found a solution. I did a lot of Google searching, and found perhaps 4 to 5 pages that had the same solution. While I still think it's ESet's problem, this solution may help them find the cure.

Add this registry entry (your PC may or may not have it, mine did not)

As always, perform a registry backup first.

==================================
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters]

"DhcpNodeType"=dword:00000004
==================================

This should fix the workgroup error. The value 4 can be different, but after reading what each value does, 4 seems best. If this solution does not help, addtionally add this below, but more than likely you won't have to do this second addition. (again my registry had this missing also)

==================================
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters]

"NodeType"=dword:00000001
==================================

Now what MAY happen is, if you plug into different work group networks, you MAY have to redo these registry patches. For instance, if you work on your workgroup at home........take your laptop to the office, and if it's set up under workgroup aLSO.......... this CAN cause changes.

One of the supporting links

http://microsoft-personal-operating-systems.hostweb.com/TopicMessages/microsoft.public.windowsxp.network_web/781146/1/Default.aspx

The Microsoft Computer Browser Service should actually be left alone.

Also for a few more rare cases, this may also help.

http://support.microsoft.com/?kbid=318030

[kwg]

-{ Quote: "Has anybody tried to disable the "Computer Browser" service in your ESS computer with EAV or Nod32 on another one to see if it helps?" }-

Yes, and it made no difference. As I indicated in my previous post, I also restarted the Computer Browser service, and it made no difference.

Again, let me emphasize: I experience this problem even when there is only one computer on the network. The problem has nothing to do with the configuration of other computers on the network.

[kwg]

-{ Quote: "
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters]

"DhcpNodeType"=dword:00000004" }-
Unfortunately, this solution did not work for me, even after rebooting. The reason may be that all of the computers on my network have fixed IP addresses. Even with only a single computer on my network, this solution did not work.

[sherryxp2000]

-{ Quote: "Unfortunately, this solution did not work for me, even after rebooting. The reason may be that all of the computers on my network have fixed IP addresses." }-

Well it MAY be a momentary fix for me. I'll have to try it for a few days, and make sure the error doesn't occur again.

[Jenee]

I have done some experimenting and reading up about the Master Browser and Backup Browser. The workgroup must have a master browser and backup browser, how they are allocated, I don't know.
What I do know is that ESS stops a PC being a master browser. I found this out because the PC which used to be the master browser (and I thought still was) has this error in event log:

The browser service has failed to retrieve the backup list too many times on transport \Device\NetBT_Tcpip_{EF01A7C3-E06E-43F1-B485-F9A590507174}. The backup browser is stopping.

This same error was on all other PCs with ESS installed (just different codes in the brackets.

I uninstalled ESS from one of the PCs and it immediately became a master browser. I then ran the network wizard on the other PCs and the network works fine.

I then turned off the PC without ESS installed and the network failed on the remaining PCs. I reinstalled ESS on the PC which I had previously uninstalled it from, the network failed and this PC had the same error in Event Viewer.

So with ESS installed, there are umpteen backup browsers and no master browser.

The only thing I can get close to is the allocation of IP addresses by ESS in the trusted zone which I think is causing the problem as the documentation on browsers refers to problems with IP addresses and subnets. My network uses 192.168.0.5, 192.168.0.4, 192.168.0.15 and the router is 192.168.0.1. In the ESS trusted zone setup, it has the IP as 27.0.0.1 and subnet of 192.168.0.0/255.255.255.0 and under local addresses all PCs have 27.0.0.1 and then their own IP address (eg 192.168.0.5)
I am no expert but the trusted zone settings do not appear to give access to other computers in the network.
I wish an Eset authority would comment on these trusted zone settings and the master browser problem.

[stueycaster]

-{ Quote: "Yes I tried that, but it didn't seem to make a difference." }-
-{ Quote: "Yes, and it made no difference. As I indicated in my previous post, I also restarted the Computer Browser service, and it made no difference.

Again, let me emphasize: I experience this problem even when there is only one computer on the network. The problem has nothing to do with the configuration of other computers on the network." }-
Well now I'm really confused. ??? I guess I'll just leave it up to the experts.

[Marcos]

I have sent a private message to Jenee. If someone else can reproduce this problem at any time, please drop me a PM.

[Jacqui D]

-{ Quote: "The only thing I can get close to is the allocation of IP addresses by ESS in the trusted zone which I think is causing the problem as the documentation on browsers refers to problems with IP addresses and subnets. My network uses 192.168.0.5, 192.168.0.4, 192.168.0.15 and the router is 192.168.0.1. In the ESS trusted zone setup, it has the IP as 27.0.0.1 and subnet of 192.168.0.0/255.255.255.0 and under local addresses all PCs have 27.0.0.1 and then their own IP address (eg 192.168.0.5)
I am no expert but the trusted zone settings do not appear to give access to other computers in the network.
I wish an Eset authority would comment on these trusted zone settings and the master browser problem." }-

I have a similar configuration to Jenee, my router is 192.168.0.1 and my computers are all 192.168.0.2xx, but ESET automatically chose a subnet of 192.168.0.0 / 255.255.255.0 for the trusted zone. Is this correct?

[Hotep]

I am also having this network issue. I ended up purchasing Network Magic in order to have access. If I uninstall ESET SS my network becomes visible on both computers. Once I re install my network disappears. I don't understand all the technical jargon or have the appropriate knowledge to try and figure this all out. I just know for me, without Network Magic, ESET is not an option as I heavily rely on my network use. Hopefully they will get this all sorted out.

[sherryxp2000]

Well the registry patches only worked for 2 days, now it's back to the workgroup error.

Something has to give.

It's like magic, it works, it don't, it works, it don't.

[Palombaro]

-{ Quote: "


The only thing I can get close to is the allocation of IP addresses by ESS in the trusted zone which I think is causing the problem as the documentation on browsers refers to problems with IP addresses and subnets. My network uses 192.168.0.5, 192.168.0.4, 192.168.0.15 and the router is 192.168.0.1. In the ESS trusted zone setup, it has the IP as 27.0.0.1 and subnet of 192.168.0.0/255.255.255.0 and under local addresses all PCs have 27.0.0.1 and then their own IP address (eg 192.168.0.5)
I am no expert but the trusted zone settings do not appear to give access to other computers in the network.
I wish an Eset authority would comment on these trusted zone settings and the master browser problem." }-

Ditto - more or less

[Marcos]

Just out of curiosity, is UPnP in the trusted zone allowed? If so, is the trusted zone configured correctly? Could you try creating a rule that will allow all connections to the remote port 1900 to see if that helps?

[stueycaster]

-{ Quote: "Just out of curiosity, is UPnP in the trusted zone allowed? If so, is the trusted zone configured correctly? Could you try creating a rule that will allow all connections to the remote port 1900 to see if that helps?" }-
UPnP and IGMP are both allowed and I have left default settings in the Trusted Zone.

I made a new rule, called it Remote Port 1900, allowed TCP and UDP in both directions and added 1900 to Remote Port. I don't know if there is anything else I need to do.

After enabling and starting the Computer Browser Service then rebooting the other computer the workgroup link failed again.

[patch]

-{ Quote: "If you uninstall ESS, I gather the function in question begins working properly, right?" }-
Correct
Uninstalling makes it work without restarting computers or router.
Clean instal (latest download from ESET & clearing registry entries, default settings & "Allow sharing") stops it working, again without restarting computer or router.

As specific as I can be, I believe the fault causes:
A computer to not act as a master browser for itself when elected to do so
See http://www.wilderssecurity.com/showpost.php?p=1150277&postcount=149
Interestingly it does function as a master browser for other windows XP or windows 2000 machines

It can be demonstrated with a one computer network behind a router (view workgroup error) or using the “browstat status” command on more complex networks.
It results in intermittent function on more complex networks, depending on which computer is elected as master browser at any point in time.

For me it occurs with ESS on windows XP professional.
It doesn’t occur with windows 2000 or when ESS is uninstalled.

-{ Quote: "Stueycaster mentioned that after disabling the Computer browser service it worked fine. Maybe you could try the same and let us know about the result." }-

Bad idea if you want to find & fix the bug. OK as a workaround if you have some computers not demonstrating the bug and want to force them to be the master browser.

-{ Quote: " if users with this problem would assist by answering some or all of his questions it might help with this matter.

* "If possible, could you try installing a different network card to see if it's releated somehow to its drivers? Maybe a partial interference occurs when ESS drivers are installed, but that's just a hunch."" }-
Sorry, bit hard for me to do but same fault occurs on different computers (desktop & laptop – LG P1 pro express dual)
-{ Quote: " * "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"" }-
No help
-{ Quote: " * "Do all of you use a 1GB NIC and switching it to 100mps mode helps?"" }-
100mps only
-{ Quote: " * "what OS are you running? (32 or 64-bit?)
- has someone observed this problem also with EAV?" }-
32 bit Windows XP professional. Not aware of problem with EAV, but haven't used it for a month & relying on my memory
-{ Quote: " * "- Is the Trusted zone configured properly and all computers in your LAN are members of it?"" }-
Yes.Left at default
Subnet 192.168.1.0 / 255.255.255.0
Computers with fault 192.168.1.20 and 192.168.1.1
-{ Quote: " * "- Does the problem perist no matter whether interactive or automatic mode is selected?"" }-
Same automatic or interactive
-{ Quote: " * "- Does disabling the firewall completely make a difference?" }-
Disabling has no effect, which is interesting as un-installing instantly fixes the problem & installing creates it. Hopefully this helps to localise the fault.
-{ Quote: " * "- Have you enabled logging of all blocked connections and no blocked connection appeared in the firewall log?" }-
Yes enabled, Blocked connection shown with default settings on automatic are shown below. The list is much longer if uPnP and streamin via IGMP are allowed.
15/01/2008 9:31:24 PM Communication denied by rule 192.168.1.254:50005 239.255.255.250:1900 UDP Block incoming SSDP (UPNP) requests C:\WINDOWS\system32\svchost.exe NT AUTHORITY\LOCAL SERVICE
15/01/2008 9:35:01 PM Communication denied by rule 192.168.1.20:59761 192.168.1.254:1900 UDP Block outgoing SSDP (UPNP) requests C:\WINDOWS\system32\svchost.exe NT AUTHORITY\SYSTEM
15/01/2008 9:35:02 PM Communication denied by rule 192.168.1.20:59761 192.168.1.20:1900 UDP Block outgoing SSDP (UPNP) requests C:\WINDOWS\system32\svchost.exe NT AUTHORITY\SYSTEM
15/01/2008 9:35:32 PM No usable rule found 192.168.1.20 224.0.0.22 IGMP

Note with suitable rules in the interactive mode I can ensure no blocked connections are shown, however it still doesn't work.
-{ Quote: " * "- Do you have another firewall installed?"" }-
No other fire wall ever used (other than built windows, no change if disable that)

[Jenee]

When ESS is installed, an Eset service is also installed under the properties of the local LAN. This service has a checkbox which can be unticked and if it is unticked, the LAN connection briefly stops and restarts. When the Eset service is ticked again, a Microsoft dialogue appears stating the software to be installed is not verified. When this box is OK'd, the LAN is again stopped and restarted.
Does anyone know what this Eset service is or does?
I haven't had a chance to test the network problem yet but I will try, in the next day or so, unchecking this service on all PCs in the network to see what happens.

[patch]

-{ Quote: "When ESS is installed, an Eset service is also installed under the properties of the local LAN. This service has a checkbox which can be unticked and if it is unticked,
/snip/
Does anyone know what this Eset service is or does?" }-

I suspect it is the method used by ESS to do low level network connection monitoring.
-{ Quote: "I haven't had a chance to test the network problem yet but I will try, in the next day or so, unchecking this service on all PCs in the network to see what happens." }-

Easiest way to test is simplify your network.
Switch off all but one computer.
Try "View workgroup computers" on the one remaining computer, if it shows itself all is good, if not that computer doesn't have a correctly functioning master browser.

[Jenee]

-{ Quote: "

Easiest way to test is simplify your network.
Switch off all but one computer.
Try "View workgroup computers" on the one remaining computer, if it shows itself all is good, if not that computer doesn't have a correctly functioning master browser." }-

I can't agree with this as sometimes at least one computer can see itself when "View workgroup computers" is selected in the network with other PCs online as well. The test needs to be done with at least two PCs in the network.

[Jacqui D]

-{ Quote: "When ESS is installed, an Eset service is also installed under the properties of the local LAN. This service has a checkbox which can be unticked and if it is unticked, the LAN connection briefly stops and restarts. When the Eset service is ticked again, a Microsoft dialogue appears stating the software to be installed is not verified. When this box is OK'd, the LAN is again stopped and restarted.
Does anyone know what this Eset service is or does?
I haven't had a chance to test the network problem yet but I will try, in the next day or so, unchecking this service on all PCs in the network to see what happens." }-

Jenee, please see my earlier post in this thread:
http://www.wilderssecurity.com/showpost.php?p=1126656&postcount=102

and Stuey's reply:
http://www.wilderssecurity.com/showpost.php?p=1126721&postcount=103

When electing to install the ESET unsigned software this error appears in the event log:

Event Type: Warning
Event Source: Server
Event Category: None
Event ID: 2504
Date: 1/10/2008
Time: 8:10:46 PM
User: N/A
Computer: PWS690
Description:
The server could not bind to the transport \Device\NetBT_Tcpip_{1E69027E-CB1B-4793-8D77-B49793CF5987}.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I am still using this workaround to access my workgroup computers, however, nobody has confirmed whether this does anything to the functionality of the firewall. That said, outbound connections are still being stopped by the firewall as tested. I am also behind a NAT router with SPI firewall.

Jacqui

[patch]

-{ Quote: "I can't agree with this as sometimes at least one computer can see itself when "View workgroup computers" is selected in the network with other PCs online as well. The test needs to be done with at least two PCs in the network." }-
mmm

Yes with multiple computers it is more complicated, as either computer maybe the master browser. Typically the computer accessing a remote master browser works better.

It is because of this and the fact I was trying to test for the fault rather than demonstrate intermittent function, that I suggested testing one computer at a time. I think you will find if you tested all of your computers one at time (others powered down) and the "View workgroup computers" worked for all. Then it would also work reliably with any combination of computers on (for the current ESET "View workgroup computers" bug).

It is also correct that if you have gone to the trouble of installing browstat, and are comfortable with the cmd window, then you can readily determine what is happening in more complex networks using that tool. I have the impression many people are not that keen on doing this though.

-{ Quote: "We've been trying to replicate this problem to no avail" }-
That is disturbing. Is there any more information we could provide to help you reproduce it?
Please let us know as soon as you can demonstrate the bug.
-{ Quote: "If there was a problem viewing network computers it persisted even after uninstalling ESS." }-
No all resolves when ESS is uninstalled & reoccurs when installed again

[kC_]

just out of interest i was one of the people reporting this problem from beta1 up to the final version, since re-installing xp, i havnt been able to reproduce the error... 2months+ now and all perfect

thats the same network, same hardware, same drivers & ESS. surely i should be able to reproduce it??..but nope ::) so i can see where marcos is coming from when saying they cannot reproduce it.:dry:

[Jenee]

-{ Quote: "Jenee, please see my earlier post in this thread:
http://www.wilderssecurity.com/showpost.php?p=1126656&postcount=102

and Stuey's reply:
http://www.wilderssecurity.com/showpost.php?p=1126721&postcount=103

When electing to install the ESET unsigned software this error appears in the event log:

Event Type: Warning
Event Source: Server
Event Category: None
Event ID: 2504
Date: 1/10/2008
Time: 8:10:46 PM
User: N/A
Computer: PWS690
Description:
The server could not bind to the transport \Device\NetBT_Tcpip_{1E69027E-CB1B-4793-8D77-B49793CF5987}.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I am still using this workaround to access my workgroup computers, however, nobody has confirmed whether this does anything to the functionality of the firewall. That said, outbound connections are still being stopped by the firewall as tested. I am also behind a NAT router with SPI firewall.

Jacqui" }-

I could not view the links but I am assuming that no one yet knows what this Eset service is.
When I allowed it to install, I did not get any event log errors.

[Jenee]

-{ Quote: "just out of interest i was one of the people reporting this problem from beta1 up to the final version, since re-installing xp, i havnt been able to reproduce the error... 2months+ now and all perfect

thats the same network, same hardware, same drivers & ESS. surely i should be able to reproduce it??..but nope ::) so i can see where marcos is coming from when saying they cannot reproduce it.:dry:" }-

Did you reinstall xp (i.e. repair type reinstall) on the existing disk or start with a clean disk and installed from scratch.

[kC_]

existing disk, fresh instal (format hd) xp pro sp2 oem

[stueycaster]

-{ Quote: "existing disk, fresh instal (format hd) xp pro sp2 oem" }-
Which did you do first, install ess or establish the network?

[patch]

-{ Quote: "
- Does disabling the firewall completely make a difference?

Yes
" }-
When I use the ESS --> Setup --> Personal firewall --> "Disable filtering:allow all traffic"
To disable the firewall, it makes no difference ie. the "View workgroup computers" Error persists.

Do you get the same Jenee, or are you saying for you the bug goes when the firewall is disabled like this?

-{ Quote: "I have discovered that by unchecking and rechecking the Eset Firewall Port in my "Local Area Connections Properties" that I am able to view my workgroup computers always" }-
When I uncheck that box, the "View workgroup computers" Error goes (ie. with one computer on the network, it can see itself.

If I enable it again the "View workgroup computers" Error returns
Jacqui D does the problem also return for you when you recheck the Eset Firewall Port in my "Local Area Connections Properties"?

Looking at the event log, this forces a master browser election each time, so it may have elected a different computer if you had more than one on at the time.

-{ Quote: "Also when I re-check this option I get asked to install some software, as stated above, which I have elected to not install." }-
I get the warning about installing an unsigned driver also.
I believe this just means ESET have not paid Microsoft's exorbitant fee to register their driver.
If you choose not to install the ESET driver, then I suspect that is why the error isn't returning (you are not restoring the software to it's previous state)

-{ Quote: "
When electing to install the ESET unsigned software this error appears in the event log:
/snip/
Description:
The server could not bind to the transport \Device\NetBT_Tcpip_{1E69027E-CB1B-4793-8D77-B49793CF5987}.
" }-
I get an Information event
The browser has forced an election on network \Device\NetBT_Tcpip_{6B9AFBD2-4C18-4524-8AAF-5A0FC9157641} because a master browser was stopped.

Not sure why there is a difference. Do you get the same with just one computer on.

-{ Quote: "@stueycaster $ kC_
Re install (restoring to a fresh install using Acronis TI) on my three PCs (1 Vista other 2 XP) did not help. " }-
Given I get the same problem on multiple computers, I too am sceptical that reinstalling windows is the solution.

If that is ESET's solution, they are suggesting a lot of inconvenience to their customers.
Perhaps we need a poll to see how widespread the problem is among XP Pro & other computers

[kC_]

-{ Quote: "Which did you do first, install ess or establish the network?" }-

instal xp
instal drivers
(network would of been established upon instal of lan driver)
instal ess
instal windows updates
reboot

[djmorgan]

I have a simular problem, I think! my laptop connects to my works network I can get Internet and email but cannot see the corporate network, I have tried all the suggestions here with no result, no I have not reinstalled the OS and won't do that.

[stueycaster]

-{ Quote: "instal xp
instal drivers
(network would of been established upon instal of lan driver)
instal ess
instal windows updates
reboot" }-
You didn't have to run the Network Setup Wizard?

[kC_]

-{ Quote: "You didn't have to run the Network Setup Wizard?" }-

never used wizards, prefer to setup manually..
what is so hard about setting a workgroup name and leaving the IP to obtain automatically?::)

[stueycaster]

-{ Quote: "never used wizards, prefer to setup manually..
what is so hard about setting a workgroup name and leaving the IP to obtain automatically?::)" }-
I didn't know there was any other way. What I was wondering is if the network was already running before you installed ESS?

[kC_]

yes as i would of accessed the ess installer from my windows 2003 server

[stueycaster]

-{ Quote: "yes as i would of accessed the ess installer from my windows 2003 server" }-
Ok. Thank you.

[Jacqui D]

-{ Quote: "
Jacqui D does the problem also return for you when you recheck the Eset Firewall Port in my "Local Area Connections Properties"?
" }-
When I recheck the Eset Firewall Port and click "apply" I get asked to install some unsigned software. Installing it leads to the error occurring and the inability to view my workgroup and also creates the error in the event log posted earlier. Opting to STOP installation leads to the ability to view the workgroup without any errors and the apparent correct operation of the firewall. i.e. the firewall stops outbound traffic according to the rules or prompts for allowance/denial. It is the best workaround solution that works for me.

-{ Quote: "
Not sure why there is a difference. Do you get the same with just one computer on.
" }-

One of my workgroup computers is on 24/7, so there are always at least two computers in my workgroup. I will test later when the system is down. I also get this warning in the event log when I opt to install the ESET firewall port:

Event Type: Warning
Event Source: MRxSmb
Event Category: None
Event ID: 3019
Date: 1/10/2008
Time: 8:12:49 PM
User: N/A
Computer: PWS690
Description:
The redirector failed to determine the connection type.

-{ Quote: "
Given I get the same problem on multiple computers, I too am sceptical that reinstalling windows is the solution.
" }-

I don't think reinstalling Windows is the solution. I installed ESS on a fresh install of XP 64/SP2 and have had this issue from the get go.

Jacqui

[Jacqui D]

-{ Quote: "yes as i would of accessed the ess installer from my windows 2003 server" }-

I only have XP-32's and one XP-64 in my workgroup. Maybe the presence of a "real" server helps with this issue since there are no browser election issues etc?

Anyone? Maybe Patch's suggestion for a poll would be a good idea.

Jacqui

[kC_]

the server03 box has been running long before ess was even on the drawing board, was running through beta1 etc..
it seems at least for me that it was possibly some software i had maybe installed in the past that had been uninstalled still causing some conflict.

[Jenee]

Patch, you quoted me as saying that disabling the firewall fixed the problem with "View Workgroup Computers". It doesn't. If I did say that then it should have been uninstalling the firewall fixed the problem.

[patch]

-{ Quote: " It doesn't." }-
Thanks for clarifying.
The aim is to demonstrate to ESET that the bug is consistent and reproducible across many users. Hopefully motivating them to find & fix it.

[Jenee]

I have not used EAV v3 but in Nod32 v2.7 there was a facility to repair the network which I found to be exceptionally good at fixing any network problems. Sometimes if my network did have various problems and the Windows network repair was not able to fix it, I would use the facility in Nod32 and it always worked. I wonder what this did exactly. Wish they would incorporate it into ESS perhaps.

[kC_]

was probably a winsock fix "netsh winsock reset"

or a simple to use tool for xp/03
http://www.snapfiles.com/get/winsockxpfix.html

[Jenee]

I am probably convinced that workgroup computer error is a browser issue and even the shares are erratic in that one pc will show them and another will not and never has since ESS was installed.
However, I have found that I can use the search facility to find computers on the network and access all the files. This will give me a temporary fix but can anyone tell me why a search will provide access but My Network Places cannot.

[kC_]

when i had the problem, mapped drives & previously made network shortcuts worked fine, only problemn was trying to list workgroups.

[sherryxp2000]

Mine won't even find nothing using a computer search.

Only way I can get my EAV machine to find the Workgroup is if my laptop is on. And even then, I haven't tried yet to see if the laptop or the EAV PC has to be on first.

-{ Quote: "I am probably convinced that workgroup computer error is a browser issue and even the shares are erratic in that one pc will show them and another will not and never has since ESS was installed.
However, I have found that I can use the search facility to find computers on the network and access all the files. This will give me a temporary fix but can anyone tell me why a search will provide access but My Network Places cannot." }-

[sherryxp2000]

Alright, I have found when the Work Group works, and when it doesn't. At least in my case.

EAV MACHINE IS OFF
LAPTOP IS OFF

Ok, I turn on my machine with EAV, and I get NO Workgroup when I try to view Workgroup. All I get is the ERROR Window for the view. I do a search, still nothing.

I turn on my Laptop, and I view workgroup. Laptop sees ITSELF. Ok, normal. But still it doesn't see my other machine. By the way, NEVER no error windows on this laptop machine. I do a search, and again, all the laptop finds is itself.

Ok now I REBOOT ONLY the EAV machine. I let it stop at the user logon.

The Laptop has now found itself and the EAV machine now. I do a search, normal as suspected, it finds both. I can even add the printer from the EAV machine to the laptop.

Now I finish logging into my EAV machine. Now the EAV sees both itself and the laptop. All is normal.

Hope this helps "find" the FIX!!! I eagerly await. Thanks. :)

[stueycaster]

-{ Quote: "Alright, I have found when the Work Group works, and when it doesn't. At least in my case.

EAV MACHINE IS OFF
LAPTOP IS OFF

Ok, I turn on my machine with EAV, and I get NO Workgroup when I try to view Workgroup. All I get is the ERROR Window for the view. I do a search, still nothing.

I turn on my Laptop, and I view workgroup. Laptop sees ITSELF. Ok, normal. But still it doesn't see my other machine. By the way, NEVER no error windows on this laptop machine. I do a search, and again, all the laptop finds is itself.

Ok now I REBOOT ONLY the EAV machine. I let it stop at the user logon.

The Laptop has now found itself and the EAV machine now. I do a search, normal as suspected, it finds both. I can even add the printer from the EAV machine to the laptop.

Now I finish logging into my EAV machine. Now the EAV sees both itself and the laptop. All is normal.

Hope this helps "find" the FIX!!! I eagerly await. Thanks. :)" }-
Are you using Eset Antivirus or Eset Smart Security. This forum and thread are about ESS. If you're using ESS then you have the same set up that I do and it's doing the same thing when you boot them. If you're using EAV then I don't understand because it's the firewall that is causing the problem.

Any time I rebooted the ESS machine with the laptop (with EAV) running the View workgroup link would start working correctly. But if I rebooted the laptop the workgroup link would fail.

I'm certain this is because the ESS computer can't deal with the Master Browser responsibility because the firewall is blocking it. Then when the ESS computer is rebooted the laptop takes over the responsibility and it works.

This hasn't been a problem for me since I shut down the Computer Browser service in my ESS computer. It always works right now. When I told people about this in my earlier posts I left something out. I left out the part about after shutting down the Computer Browser service you have to wait a while before trying it. Changes made in network settings sometimes don't take place immediately. When I wait 15 minutes it works. Try disabling the service again and this time wait 15 minutes before trying it. Maybe it will work. It does for me.

I'm not saying that ESS doesn't need to be fixed though. Someday I plan to have 2 laptops and when I do I'm going to want my desktop to remain Master Browser because it stays on all the time. Also I want to run ESS on all three.

[Jenee]

I cannot find any entries in the ESS log that indicates it is blocking the network so the only thing that may be effecting the browser service is the Eset service installed in the Local Area Connection and/or a registry entry.
I have changed all my PCs to Advanced File Sharing and I can now consistently see all the shares and all PCs except the one that is the master browser. If there is no master browser then I can't see any PCs.

[sherryxp2000]

Yes I am using ESS, just had a typo. Sorry for not paying attention.



-{ Quote: "Are you using Eset Antivirus or Eset Smart Security. This forum and thread are about ESS. If you're using ESS then you have the same set up that I do and it's doing the same thing when you boot them. If you're using EAV then I don't understand because it's the firewall that is causing the problem.

Any time I rebooted the ESS machine with the laptop (with EAV) running the View workgroup link would start working correctly. But if I rebooted the laptop the workgroup link would fail.

I'm certain this is because the ESS computer can't deal with the Master Browser responsibility because the firewall is blocking it. Then when the ESS computer is rebooted the laptop takes over the responsibility and it works.

This hasn't been a problem for me since I shut down the Computer Browser service in my ESS computer. It always works right now. When I told people about this in my earlier posts I left something out. I left out the part about after shutting down the Computer Browser service you have to wait a while before trying it. Changes made in network settings don't take place immediately sometimes. When I wait 15 minutes it works. Try disabling the service again and this time wait 15 minutes before trying it. Maybe it will work. It does for me.

I'm not saying that ESS doesn't need to be fixed though. Someday I plan to have 2 laptops and when I do I'm going to want my desktop to remain Master Browser because it stays on all the time. Also I want to run ESS on all three." }-

[Jenee]

-{ Quote: "just out of interest i was one of the people reporting this problem from beta1 up to the final version, since re-installing xp, i havnt been able to reproduce the error... 2months+ now and all perfect

thats the same network, same hardware, same drivers & ESS. surely i should be able to reproduce it??..but nope ::) so i can see where marcos is coming from when saying they cannot reproduce it.:dry:" }-

Are you able to list the rules created by ESS under System so that I can compare them to what I have. These rules seem to be the ones applying to the network. Could you also advise what is listed under the Trusted Zone.
Many thanks.

[patch]

-{ Quote: "Are you able to list the rules created by ESS under System so that I can compare them to what I have. These rules seem to be the ones applying to the network. Could you also advise what is listed under the Trusted Zone.
Many thanks." }-
I would be surprised if the rules were the issue as no entries are shown in the log and disabling the firewall doesn't help.

Only un-installing the Eset service installed under the properties of the local LAN (or ESS) fixes it. Indicating to me their driver is not compatible with some windows XP network configurations.

I suspect it is the permutations of "NetBT" & "Direct hosted SMB", (use of which depends on host settings, router settings and network environment) that is the cause of the bug.

[Jenee]

-{ Quote: "I would be surprised if the rules were the issue as no entries are shown in the log and disabling the firewall doesn't help.

Only un-installing the Eset service installed under the properties of the local LAN (or ESS) fixes it. Indicating to me their driver is not compatible with some windows XP network configurations.

I suspect it is the permutations of "NetBT" & "Direct hosted SMB", (use of which depends on host settings, router settings and network environment) that is the cause of the bug." }-

I tend to agree that it may have something to do with NetBT and SMBs but the real issue is the browsing service and they are all linked. What I can't understand is that KC has been able to remove the problem by starting with a clean install of XP. That indicates it is not an issue with hardware, drivers or router settings. However, the clean installation may have had an effect on how ESS set up the rules and may have also determined registry settings. None of us know if the installation of ESS modifies any registry settings that could affect the browsing service.

[stueycaster]

-{ Quote: "What I can't understand is that KC has been able to remove the problem by starting with a clean install of XP. " }-
This is just a guess on my part. KC_ runs Server 2003 on one of his computers. Since it's a server it probably runs all the time. Because of that it maintains Master Browser status. In one of the links that Patch provided for us it mentioned how the computer that spends the most time running is usually master. Also does that computer have ESS installed? Hopefully he'll drop in and clarify exactly what his configuration is and how he uses it.

Some others mentioned reinstalling their o/s without it fixing it.
-{ Quote: "don't agree. made a clean xp install and still stuck with the thing." }-
-{ Quote: "Me too.
Also other threads are appearing showing slightly different problems with network sharing. Clearly this is a general problem with ESS ." }-
Also since I disabled the Computer Browser service in my ESS computer this issue doesn't affect me at all.

[Jenee]

Thanks Stueycaster. We know it is a browser issue and we know that disabling the firewall does not fix it. That just leaves the service driver Eset installs on the NIC and a registry entry.
I recently added a new PC to my network but all the data was imaged from a PC previously in the network. This new PC had a fresh install of ESS and even if it is the master browser and is left on, it is still random as to whether it can see all the other PCs in the network. Most times it can only see itself and one other PC.
Does anyone know:
a) what effect does the removal of the Eset NIC service have on security integrity; and
b) if this service is removed, does it fix the problem?

[sherryxp2000]

I did a new XP install on an old system today. A new install still has Workgroup errors with ESS.

[kC_]

yep the server 03 box runs 24/7, has done for the past 3 years or so, it has always been set as the master browser & i always disable the computer browser service on the rest of my network..

this xp machine where i had the problem, was configured with outpost/nod32 2.7
network working fine, then i started to tryout the ess beta's which is when i started getting the problem.. (computer browser service was already disabled on the xp client)

since the xp machine was the original instal on the machine for 5-6years+ i thought about the fresh instal, and it sorted it immediatley.
(same drivers/hardware/services/network config)

is a very odd one indeed:blink:

[Jenee]

Each of the PCs in my network has a slightly different set of rules under System which relate to netbios access and file sharing and I don't understand why they should be different.
One PC has a rule to allow access to shared files and printers in the trusted zone for incoming direction and the other PC does not. All PCs have a similar rule for outgoing direction but not trusted zone. I don't know how to create the incoming rule on the PC where it is missing as I don't know what the "System" application is.
I know that disabling the firewall has no effect on the problem but these settings may still affect the service installed on the NIC and that is not disabled when the firewall is disabled.

[patch]

-{ Quote: "
since the xp machine was the original instal on the machine for 5-6years+ i thought about the fresh instal, and it sorted it immediatley.
(same drivers/hardware/services/network config)

is a very odd one indeed:blink:" }-

If you switch off all other computers does "View workgroup computers" still work on this XP machine?

This test is to see how the XP machine functions as a master browser as opposed to using a master browser elsewhere in your network.

[stueycaster]

Just in case I never mentioned this, on my ESS machine the view workgroup link fails if it is the only machine turned on. The view workgroup links on both computers are totally dependent on the EAV computer. The EAV computer can view it's own when the ESS machine is shut down.

[mayt]

Hello,

thank you all for your contribution to get this problem solved. We've managed to narrow down the problem. It seems the problem appears when ndis filter (present in ESS) is installed on a machine which is a browser master.

Further analysis and replication yet to come. We cannot guarantee any date when a fix might appear at the moment.

Thanks for understanding.

[stueycaster]

-{ Quote: "Hello,

thank you all for your contribution to get this problem solved. We've managed to narrow down the problem. It seems the problem appears when ndis filter (present in ESS) is installed on a machine which is a browser master.

Further analysis and replication yet to come. We cannot guarantee any date when a fix might appear at the moment.

Thanks for understanding." }-
Thanks for the info. At least we won't be left wondering what happened when the new release comes out soon and it isn't fixed. I'm sure you guys will fix it.

[Jacqui D]

-{ Quote: "Hello,

thank you all for your contribution to get this problem solved. We've managed to narrow down the problem. It seems the problem appears when ndis filter (present in ESS) is installed on a machine which is a browser master.

Further analysis and replication yet to come. We cannot guarantee any date when a fix might appear at the moment.

Thanks for understanding." }-
It is reassuring to note that ESET seem to have found the culprit. The workaround I am using, i.e. not installing the software for the ESET firewall miniport on the NIC (thru the Local Area Connection Properties) is probably related to this NDIS filter. Would it be possible, since I initially asked the question in post #102 and Jenee asked the same question later in post #240, for ESET to confirm whether the functionality of the firewall is adversely affected by using this workaround?

Thanks.

[patch]

-{ Quote: "Hello,

thank you all for your contribution to get this problem solved. We've managed to narrow down the problem. " }-
Wonderful news
Thank you for letting us know you have been able to reproduce the fault.

Please let us know if we can be on any further assistance in fixing it.

[papa33600]

Here is a possible partial workaround :
the view workgroup computers problem seems to arise whenever the computer
running ESS is elected as master browser. If another computer on the network
(not running ESS) is elected as master browser, then it works fine.
Thus you can try this :
edit your registry as follows :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters
MaintainServerList=No

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters
IsDomainMaster=FALSE

I also disabled the computer browser service.

This does not solve entirely the problem :
if the computer with ESS is the only one connected to the network, then there is no master browser, and so you get an error if you try to view workgroup computers.
And if you have several computers running ESS on the network, that might be even more complicated.

But it solved the problem in other cases, at least for me.
papa33600