Webmaster@xxxxxxxxxxxx wrote:
Hi, don't look like a virus to me. But on the other hand I don't really believe you "haven't changed anything" will be true either. As far as I remember Windows is using a set of name resolution possibilities like: .../etc/hosts lmhosts WINS Browser Master Broadcast So you should think about any changes done before the problem occurs. IMO even a reboot of the Master Browser might be a difference, already. So which Windows machines do you have? Can you resolve the names at the Windows Boxes using nbtstat ... can you ping other machines using ping <netbios name> There is something else where you might find some valuable information. The System Event log of your windows boxes, check esp. for Browser entries. Finally you should trace during opening the Network Neighborhood at one machine and check for the NBNS and BROWSER protocol too. What's going on there? Any Firewall installed at one of the Windows boxes, any MS Sec. updates installed recently? best regards Robert-----Ursprüngliche Nachricht----- Von: suse@xxxxxxxxxx [mailto:suse@xxxxxxxxxx] Gesendet: Donnerstag, 22. Juli 2004 20:18 An: suse-security@xxxxxxxx Betreff: Re: [suse-security] Problem with Windows Network Neighborhood and Linux While you may have not changed configuration, has the volume of traffic to the shares increased? If you are using hubs, do you see more collisions now than before? If you are relying on broadcasting of network shares, rather than a registration database, any of these items can cause these broadcasts to be unheard.@suse@xxxxxxxxxx : I haven´t changed anything in theconfiguration of thenetwork, so how come I suddenly have these problems. I don´t believe I caught a virus because my network sits behind two very restrictive firewalls and AV-systems, also virus-generated traffic should lead to problems in all network applications, not just in Neighborhood Browsing, I think. Greets, Jörg-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@xxxxxxxx Security-related bug reports go to security@xxxxxxx, not here
Another idea:any updates (maybe automated) on your Windows boxes or on your linux boxes (samba, samba-client) were installed?
Does anybody remember the problems with changing passwords on an samba server after microsoft introduced its patch KB828743 (i think it was this number) in may. I also hadn't changed any configuration files, but my colleagues couldn't change their passwords anymore.
;-) just my two euro cents guido
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@xxxxxxxx Security-related bug reports go to security@xxxxxxx, not here