Skip to main content

Stupidity=Collissions et.al....

this is one stupid action i have to learn and unlearn. i recently set up a semi sub network in the office so i got a hub and pcs..there were two connections comming out from one of the hub connected in our open bay rack ..one was crossover (i did this just last week) and the other was straigh through (i knew it was there) so out of excitement i plugged all cabels from the pc and the two cables to the hub turned on the hub and......boom problems start flowing in. first internet was down the proxy server hangs. other pcs connected to our novell server starts logging off ..and worst offices starts calling staing that they cannot connect ..so i asked our MIS head ( hes been with the school for almost 10 years now handling the whole system before we took over) and started analyzing the error.. one sign we saw was the utilization was running at 98% and no pcs are connected ..looking for clues we stared at the fiber optic hub handling the backbone..and bam the collision error indicator is blinking fast informing us there is a problem ..out of nowhere my thoughts brought me to the straight through cable connected to the hub..immediately unplugging it brought the chaos down..whew!!!!!!!!!!

Comments

Post a Comment

Popular posts from this blog

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

Image Credit: https://www.pioneerrx.com A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and  Windows Workflow Foundation (WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time. Why reinvent the wheel? So I started querying the ...
Post a Comment
Read more

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python. The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below: Copy and paste the lines below : "**/*.pyc" : { "when" : "$(basename).py" }, "**/__pycache__" : true
Post a Comment
Read more

renaming default namespaces for VSTO projects in VS2008

So here is the scenario , you are starting a VSTO project and decided that your default namespace is ExcelAddInTesterApp . You created the project and started coding the project. After several days , your boss called and said "hey marvin , make use of this namespace OurCompany.ExcelAddInTesterApp , we have to add our company name to it got it?" . You get back to your machine thinking its just a simple property just like any project you've been working on. So you right clicked the VSTO project and hit properties . Boom! What the F@#$? The default namespace textbox is disabled!!!! I've been through this and I googled for ways to do it and ended up with a blog from a Microsoft MVP telling me it can't be done because it is disabled. Then I thought of Refactoring, the beauty and grandeur of the renaming process. I selected the namespace and hit the refactor menu hoping that this would solve the problem . Unfortunately , it did not rather it displayed the message b...
9 comments
Read more