Serious Sam 3 Ending
Destroy that like button if you can. This is how a game should end. RFACEBOOK: TWITTER: r rThis is the Ending / Final Boss of Serious Sam 3: BFE. Serious Sam 3: BFE is a first-person shooter video game developed by Croatia-based indie development studio Croteam and published by Devolver Digital.It is part of the Serious Sam series and the prequel to Serious Sam: The First Encounter.
AngelDeath wrote:Correction, I never said the semi-crashed computer is causing network traffic, that is the speculation consensus of others. What I said was that the semi-crashed (or possibly deep sleep) unresponsive computer is killing the network or the devices connected to that switch.
I can tell you the network switch is solid and not blinking when this occurs, the port leds do not blink simulating traffic. If you unplug the network switch to reset the switch (which I have done) the devices come back for less then 30 seoncds, and then lock up again. This occurred when I unplugged the unmanaged switch and plug it back in, the network printer came back to print 3 pages of 25 pages before it stopped, it was not until I unplugged the power to the unresponsive windows 10 Lenovo machine when it printer resumed printing the remainder 22 pages.As I said before I have made the NIC power management changes and now have to sit and wait to see IF and WHEN the computer if at all will go back into the unresponsive state to trigger this. IF it does not go into a unresponsive state or if it does and doesnt cause this situation, then the power management setting for the NIC is the causeExplain to me what you believe to be the difference between your first and second sentence.How, exactly, would a device 'kill' the network/switch/other devices on that switch without sending network traffic? We're not talking about PoE here, so what, exactly, do you believe is possibly traveling across that Cat5e/Cat6 cable that isn't network traffic?!Even if its 'garbage', malformed frames, that would still be considered 'network traffic'.You do know that the blinky lights on a switch aren't an ACTUAL diagnostic tool for anything more complex than basic connectivity.
Especially on cheap switches, but I've seen Cisco Catalyst switches be hit by bad nics/devices spewing garbage to the switch to the extent they became completely inaccessible from anything except the serial console, and yet those blinky green lights we blinking about the same amount as any normal day. Curtis3363 wrote:It doesn't and will not work as this thread so proves it as NO fix has been found by these Professionals.A search of Microsofts sites shows NO such issue.Well this topic has managed to digress into utter nonsense.This 'thread so proves' absolutely nothing beyond how blinding, preconceived notions lead to conclusions without any basis in fact or evidence.If, for some reason, you truly believe that Wireshark 'won't work' in these situations, then you're clearly ignorant of what Wireshark is, what it does, and how it is used.What 'Professionals' are you talking about? If you're talking about the handful of people who have shared similar experiences, none of them have actually tried to use a packet capture tool to diagnose the issue.I have no idea why are pointing out that no one has found a fix. That much is rather obvious to everyone. It's awfully difficult to find a fix when you refuse to use the correct tools to help you actually identify the issue.You do understand that Wireshark, or any packet capture tool, doesn't actually fix anything, right?
It's sole purpose is to capture the data being sent over the wire, in its raw form, so someone can analyze it.I'm not even saying that Wireshark will definitely find anything of actual use. What I am saying is that, with the symptoms that have been shared by multiple people, the next logical step is to run a tool like Wireshark.The fact that Microsoft's websites don't 'show this issue' has no real bearing on the issue at hand or even the conversation in this thread.
If anything, this is just anecdotal evidence that the issue ISN'T a Windows 10 problem.When it comes to IT, I prefer to work within the realm of fact and evidence as opposed to conjecture and ignorance.But maybe that's just me. AngelDeath wrote:DaveA-DoIT wrote:I'm not really sure what your trying to saye, or if your being sarcastic.But the OP, and others, have described a situation where the semi-crashed computer is causing network traffic that overwhelms the switch that it's attached to. They also describe that this state remains so until the offending machine is unplugged or forcibly reset.This is a PERFECT chance for a Wireshark capture. Obviously you don't run it on the offending machine, but if you understand what Wireshark does, this would be obvious.You start up Wireshark on a laptopart and do one of the following:- Use port mirroring on the switch to send offending traffic to another port and plug your laptop, already running Wireshark, into that.- Plug the offending machine directly into the laptopCorrection, I never said the semi-crashed computer is causing network traffic, that is the speculation consensus of others.
What I said was that the semi-crashed (or possibly deep sleep) unresponsive computer is killing the network or the devices connected to that switch. I can tell you the network switch is solid and not blinking when this occurs, the port leds do not blink simulating traffic.
If you unplug the network switch to reset the switch (which I have done) the devices come back for less then 30 seoncds, and then lock up again. This occurred when I unplugged the unmanaged switch and plug it back in, the network printer came back to print 3 pages of 25 pages before it stopped, it was not until I unplugged the power to the unresponsive windows 10 Lenovo machine when it printer resumed printing the remainder 22 pages.As I said before I have made the NIC power management changes and now have to sit and wait to see IF and WHEN the computer if at all will go back into the unresponsive state to trigger this.
Serious Sam 3 Ending Lyrics
IF it does not go into a unresponsive state or if it does and doesnt cause this situation, then the power management setting for the NIC is the causeDave is spot on with his reply to you. Chances are great that you're getting garbage spewed from the hung PC. You refuse to do a Wireshark capture to prove otherwise.
Your symptom of solid activity LEDs is the same symptom you'd see if you had an issue with STP and had a network loop. Basically that's showing you that it is a network issue. You have so much traffic going out to each port that your switch can't even give you a gap in the activity because it's just such a high amount of traffic going out. Likely that PC is broadcasting, or it's sending malformed packets that are being misinterpreted as broadcast packets.If you really think it's not a network issue, the least you could do is prove all of us that say it is, wrong.
Do a packet capture, post the log, and let the cards lie where they fall. If you're so sure it's not a network issue, what do you have to lose except a little bit of time? Then at least we can get on and maybe point to other possibilities.
Serious Sam Timeline
Curtis3363 wrote:You bragging about Wireshark works. No Fix = FunnyThis is a serious question Curtis.How do you have 24 years of experience in IT and yet you seem to have absolutely no concept of a diagnostic tool?And I'm not talking about Wireshark, specifically. I'm asking how, with that many years of experience, you've never been introduced to the concept of a tool (any tool) that's sole purpose is to gather data so that someone can review that data to obtain more information on what might be causing the root issue.That's a diagnostic tool.
That's what Wireshark does.If you're looking for a program that you can just double click and it magically fixes everything for you, you may be in the wrong career. DaveA-DoIT wrote:Curtis3363 wrote:You bragging about Wireshark works. No Fix = FunnyThis is a serious question Curtis.How do you have 24 years of experience in IT and yet you seem to have absolutely no concept of a diagnostic tool?And I'm not talking about Wireshark, specifically. I'm asking how, with that many years of experience, you've never been introduced to the concept of a tool (any tool) that's sole purpose is to gather data so that someone can review that data to obtain more information on what might be causing the root issue.That's a diagnostic tool.
That's what Wireshark does.If you're looking for a program that you can just double click and it magically fixes everything for you, you may be in the wrong career. You are right, I/m very dumb. Curtis3363 wrote:So this is NOT a regular Windows machine as it has applied GPO'sNow we have Variables, not a standalone machine.So what was the culprit that you can send to Microsoft to fix?IamMediocracy wrote:Aside from what Curtis3363 mentioned about GPO variability, the only other thing that jumps out at me is a gigabit NIC auto negotiating to 100Mbps full duplex.
Does the rest of the infrastructure support gigabit? Is there a mismatch? I know I've had mismatch issues before, never impacted the entire network or even an entire switch, but there's a first time for everything I suppose.I already stated in prior msgs that 2 locations are setup with AD (Active Directory) and 1 is not.The network isnt a gigbit network as far as I know (This client is a need be basis client), but NIC cards Auto-Neg should not create this issue, I dont believe this has anything to do with it. AngelDeath wrote:Curtis3363 wrote:So this is NOT a regular Windows machine as it has applied GPO'sNow we have Variables, not a standalone machine.So what was the culprit that you can send to Microsoft to fix?IamMediocracy wrote:Aside from what Curtis3363 mentioned about GPO variability, the only other thing that jumps out at me is a gigabit NIC auto negotiating to 100Mbps full duplex.
Does the rest of the infrastructure support gigabit? Is there a mismatch? Anytime an AD system is setup there is default gpo created based on the domain, there is nothing special in the gpo, standard default. As for your second statement of Gov't machines and priority and they would have a fix right away, please dont make me laugh, most of the gov't still runs older versions and doesnt upgrade in the masses are the rest of us. Also most who walk in doesnt call IT for a crashed system, most are smart enough, be it right or wrong, reset their own computers and doesnt get reported. AngelDeath wrote:Anytime an AD system is setup there is default gpo created based on the domain, there is nothing special in the gpo, standard default.
As for your second statement of Gov't machines and priority and they would have a fix right away, please dont make me laugh, most of the gov't still runs older versions and doesnt upgrade in the masses are the rest of us. Also most who walk in doesnt call IT for a crashed system, most are smart enough, be it right or wrong, reset their own computers and doesnt get reported.I just finished a job at the USDA, we were on Windows 10, another job I did for CSRA for the Gov all Windows 10 and the latest MAC OS, this isn't the 90's anymore, Gov gets whatever they want same with Switches and Wireless.They were using Steelheads, Cisco 5516-X, and Anchor wireless all the latest.
Bret Draper wrote:So there are alot of comments and I'm not going to sift through them all to see if this has been suggested. It sounds like spanning tree protocols might be mucked up or turned off and you are getting broadcast storms that are taking down your network.EDIT.Haha, literally like 30 min before I posted.
Sorry for suggesting the same thing.STP is not the first go-to if the network topology isn't changing. And even less so if you're not using STP-capable switches.And there's no reason to really think it's a 'broadcast storm' when the OP indicated that other PCs on a different switch experienced no issues. There was nothing in the post to indicate a complicated inter-network topology, so the best guess is it's all one subnet. A storm would affect all PCs to some extent.As they say in New England, 'Hard to say, not knowing.'
A look at the wire would have told us what was going on. Zero network traffic?
Look one place. Look somewhere else. But we've got to have the information to move forward.I apologize. I read 'kills the whole network' from his original post and assumed he meant the entire network ceased to function which would indicate a systemic problem relating to unchecked broadcast loops which would then be a broadcast storm. Just to add my experience:Wednesday 1st March, began to shutdown laptop at 4pm to head off on a long weekend. Windows 10 Laptop was taking ages to shutdown.
Serious Sam 3 Gameplay
After about 2 minutes users in office reported that they had lost network connectivity and then the phone began to ring from all areas of a large site reporting that they too had lost connectivity. Ensue a mad dash to the server room to check state of switches etc. All appeared to be running as expected.Run back upstairs and force shutdown my laptop, all users still with no network. Restart laptop and as soon as I logged back in.the network came back up!!!!I was in a rush as I had a big drive ahead of me so I checked that all areas of the site had network back and then ran out the door.Today is first day back in office and checking event logs can see nothing other than the last shutdown was unexpected.blah blah blah. Monitoring reported nothing going down etc.I'd seen this thread previously and thought, nah can't be Windows doing that. Now.I'm not so sure. It may have been pure coincidence but.Anyway that happened to me so maybe, just maybe.