boomam

The fix in there? Ive been aware of that since friday, thats the fix im on about. But im unsure as to why it happened in the first place, or why its happening on previously fixed machines?

The power cut off? No, they were replacing all the power distribution boards in the school so everything went off last half term during the work. The machines having the problems, that i know of, all go to different switches. Obviously, all the machines in one room go back to the same switch, but its happening all over the school.

Doesnt work still. Im testing it on my workstation, and it still doesnt remove the ESET folder. . ##EDIT## I changed the paths so the correct cases were in, and now all it does is delete everything in the all users start menu? Im gonna try changing it to the folder under the ESET one, even if it means leaving the top level ESET one there, empty.

Bump! .

Ive done some testing, and its true, normal users cant really do alot with the 4 shortcuts that NOD32 creates, but i'd still like a way to remove them from each machines. Ive tryed creating a batch file with a DOS command in, but it doesnt work: deltree c:\documents and settings\all users\start menu\programs\eset

Cant re-add, errors, if i expand the error, it says TCP/IP protocol not installed? Which is consistant with the fix i have to apply, but doesnt tell me the cause. Any more ideas? Ive found a KB article that outlines the problem, including the fix i do, but not even MS know of the cause? http://support.microsoft.com/kb/811259

As said, the DHCP logs, unless im looking in the wrong place, is usually in the normal system logs, of which there are no entries. Same with WINS. There is the odd DCOM and NETLOGIN error in regards to certain machines, but nothing out of the ordinary. I inheritted this network over a year ago, i was under the impression that every machine had McAfee on it, but i found out a week or so ago, when i was in the process of removing McAfee, that only a few did! :-o. Luckily, when McAfee is completely gone, i have a newly configured install of NOD32 to blast out. . Nothings come up in the virus scan, gonna try removing/adding to the domain.

The authentication problem was with one machine, this morning, that works fine? The test computer is still scanning for virii at the moment... A few of the fixed ones have dropped off again according to one of the teachers. .

So: DNS: I dont think its a DNS issue anymore. Ive found a computer that still has the problem, and remove its entry from the DNS list. Still has the problem. There are no errors in the logs, apart from one thats a result of me enabling scaveging this morning. DHCP: Cant find the logs for it, although nothing is listed in the general logs as usual for any DHCP errors. Netlogon: Again, no errors. Apart from two authentication errors for this morning for a machines in the library. And 5 of the machines i fixed on friday have the problem again. Gonna do a virus scan on the broken one ive got in here with me, see what i find.

I havnt no, as iirc, they wouldnt see the network. Different makes and models. Some were Dells, some were NECs, some where some RMs(we dont use RM, just some hand-me downs from a college from what i was told). They all have images unique to their HW. So one for Dell D740s, one for NECs, etc; I havnt messed with the DNS on our DC much, but i'll give it a look. What am i looking out for? Thinking about it, i wouldnt be suprised if it was a DNS problem, as we had DNS problems a week ago when almost all net traffic for us went dead. Took a while to get working for frog (our proxying is done by our VLE). That sounds familier, spanning tree is on on all of our switches, but its never caused problems in the past?

The problem persists though, even when the workstation next to a broken one is working fine. So surely that would indicate a workstation level problem rarther than a server one? As if the problem was intermittant, then a reboot half an hour later of a broken one would surely fix it? Maybe im being daft here, but if the problem was with an intermittant server problem, then why would the affected workstations keep on erroring on every boot, whilst working ones work fine? We're using, iirc, about 30-35% of our DHCP range at the moment. Uptime? About 2 weeks. The power for the entire school was shut off over half term. Since then ive had nothing but problems. Most of them have been the kids looping back on the 2-3 hubs we have. But in combination with a few other faults, the last few weeks have been murder for me. So, for Monday, i have to check: - DHCP logs. - Netlogin logs. I appreciate the input on this everyone. As I'd like to get down to the bottom of what caused the fault, for future reference, & piece of mind. .

Cool. Will keep a look out for that in future. . If the service has failed on the DC though, would it not affect all workstations? Plus, that wouldnt stop the workstations geting an IP would it? As im fairly sure thats the reason for the netlogin error, that it cant connect to the network to get the netlogin info off the DC? Will check the DC on monday though. .

Didnt know that about the LEDs. Good to know that is. Is that only on the switch thats got the problem, or does it trace all the way back to the core switch? The workstations that have the problem have 'limited or no connectivity'. So they see the network card, see a cable plugged in, but wont get an IP. Plus, when you try to login in, it complains about NETLOGIN service not running. If i login locally, and try to enable it manually, it doesnt work, bringing up an Error 10106.

True, but trust me, theres no loopbacks. If there was, it would affect all of our network, and give us very high pings to the DC. But it only affected some workstations (for example, 25/30 in one of our labs), while the rest functioned correctly. Plus, bizzarly, if i plug my diagnostic laptop into the same cable thats being used by a broken workstation, it works fine. So i dont think its an infrastructure based problem. Very odd, i'd like to say virus, but its hard to tell, could be anything really. Unfortunatelly. . I'd like to find out though. So any and all suggestions i'll look into. Upto now: - Loopbacks: Both diagnostics & physical checking have been done. No loopbacks. - Viruses: Unknown, no viruses on the main servers will check the workstations when McAfee has been removed from all workstations (dont want 2 AVs on the network at the same time. ).

Papercut here. Good software. Easy to use, low memory footprint, supports multiple servers. Can charge per person, per account. Can do top up cards, loads. I highly recommend it.

DHCP was up. As the other 30% of the network was running fine. All different image, as there were 3 times of machines that had the problem. Nope. Not a loopback. Because our switches have spanning tree on all of them, and usually on our network, everything drops off, plus, pings to the servers get very high. Odd problem. I wonder if i'll ever find out whats caused it?

What BECTA test is this?

Phew, what an afternoon, knackered!. Anyway: Heres what i have: Virus Scanner Enterprise: MsiExec.exe /I{5DF3D1BB-894E-4DCD-8275-159AC9829B43} Anti-Spyware Enterprise: c:\program files\network associates\virusscan\csscan /UninstallMAS I need the latter to un-install first, so i take that the batch file would read: c:\program files\network associates\virusscan\csscan /UninstallMAS c:\windows\system32\MsiExec.exe /I{5DF3D1BB-894E-4DCD-8275-159AC9829B43} /quiet /norestart

Thanks for the replys everyone. . We use spiceworks here, but its GUI runs like a dog at time, so its not really feasible. I had a bash at getting Librium to work, but had nothing but problems. .

Solved: http://www.edugeek.net/forums/showthread.php?p=162706 Although no cause why. .

Hi. Does anyone have any idea why 50-70% of the machines in our school starts having the "limited or no connectivity" problem? Where i have to manually login as local admin on each one, delete the winsock services from the registary then reinstall the TCP/IP driver on each one to get it working again? I had to manually do over 100 computers this afternoon! Im pleased ive found a fix, but i'd like to know why it happens. I dont think its a virus either, as its happened to machines that are with and without virus scanners. Thanks in advance all.

Yes. I dont think they are removing NSS, but the problem does happen?

What was the fix to that? I ask because im having the same problem here, and i updated NSS last night?

Found them. Theres a MSIEXEC one for the VirusScanner and a csscan /uninstallmas one for the spyware. Should be alright putting them both in a batch file shouldnt i?

Where in the registry is that? HKLM?