If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Road... Go for it... it's easily fixed.... just change the time on a DC that doesn't provide time to the workstations by 1 hour and wait for the phone to start ringing.... Change it back and the phone will stop ringing... The (L)users won't call you back to thank you....

Don\'t SYN us.... We\'ll SYN you..... \"A nation that draws too broad a difference between its scholars and its warriors will have its thinking done by cowards, and its fighting done by fools.\" - Thucydides

Originally posted here by RoadClosed I am ALMOST tempted to try this....

I've had a problem authenticating workstations when the time on the workstations and the server don't match. I've never seen them get KICKED off the network though after they've been authenticated... I'm not saying it doesn't work. I've just never seen it and I don't dare try it.

Quitmzilla is a firefox extension that gives you stats on how long you have quit smoking, how much money you\'ve saved, how much you haven\'t smoked and recent milestones. Very helpful for people who quit smoking and used to smoke at their computers... Helps out with the urges.

Well, I'm starting to suspect the spyware suspicion may be correct. To test that theory, we started this morning by only connecting the servers and the three most critical computers to the network. Sure enough, they've done fine with no problems whatsoever. So now I'm running scans on all computers then adding one at a time to the network, watching a while for problems, then connecting the next. So far we now have several connected with no problems. It also may be a hardware issue with our using two switches, so we're on one switch now then will add the second when I fill up the first, and test to see if that's the problem. So it looks like we're on our way to finding the culprit...Should be interesting to see if we indeed do have a rogue computer DOSing the network.

Ok, so now the network's slowing down mysteriously. I've added a few computers, and so far it's been doing ok. Just added a second switch after filling up the first one (leaving the second bare for now to see if it works well or not), and now things are starting to slow down. It's a new switch though. So could it be a network card somewhere slowing things down, or perhaps the switch?

Don\'t SYN us.... We\'ll SYN you..... \"A nation that draws too broad a difference between its scholars and its warriors will have its thinking done by cowards, and its fighting done by fools.\" - Thucydides

try running EatherApe on your network (comes with the 'audit' CD so you don't have to install *nix). it will render a graphical image in real time of all the protocols all the computers on the network are using and the amount of data being sent.

So I switched that second swith out with one of our older switches (try saying that three times fast), and the slowdown immediately stopped. Been adding computers one by one to that switch since yesterday, and so far everything's still going just fine.

As I've added each computer one at a time slowly in hopes of catching the rogue, I have made some discoveries. I just now discovered that the front desk receptionist's computer had quite a few trojans on it. Also, I had network problems soon as I reconnected one of the conference room computers, so now I'm looking at both of those as possible network troublemakers.