• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

At work - Want to network a few computers together.

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
It all depends on how the network is configured.

At my former university, each office and dorm room had two network drops, each was connected to a 10/100 switch in a nearby wiring closet. The switches were configured to allow only one MAC address per network port. Attaching a hub to a network drop and using more than one computer would cause the switch to disable the port and alert the network administrator. Doing this once resulted in a warning. Doing this twice resulted in being fired (in the case of staff) or losing internet access for good (in the case of dorms). Using a router to bypass the one-MAC-per-drop limit didn't work either, as the network was frequently scanned for known Linksys/DLink/Netgear/etc SOHO router MAC address ranges.

It may sound like an insane policy, but it ensured balanced network traffic and easy monitoring of the usage of each and every computer on campus. This is critical these days for security and logging.
 
Originally posted by: nweaver
because the hub is not approved...the hub could cause other issues that you don't know about (arp storms, broadcast storms, accidental routing loops, etc)
How will your boss like it when you call support, and they network guy looks at the physical configuration, and refused to provide support to your homegrown hodgpodge unapproved additions to the network?

why not the network guy? if this is critical, just have your boss talk to the network guy and get it a big boost in priority.

Yup, Listen to nweaver for your own good, I've seen what a broadcast storm does to a network.... Not good. I worked with the network group at my university, not for very long before my summer job but I was just getting into it and a small section of the network had a packet storm and the resulting broadcast storm caused major issues.

There is a reason he is an "asshole", it's because people like you seem to decide that you can do whatever you want on the company network reguardless of the concequences that you do not understand.
 
Back
Top