←back to thread

511 points goldenskye | 1 comments | | HN request time: 0.207s | source
Show context
myself248 ◴[] No.43548328[source]
In high school, we had a Netware 3.12 environment, and the Guest account was enabled, albeit with very limited privileges. But for some reason, Guest could still use NET SEND, which popped up a little message in the bottom row of the destination machine's display.

The whole district shared a T1 connection to the internet. Which was more than plenty for email, but as this world-wide-web thing started gaining traction, it became quite the bottleneck. And as some of us had discovered mp3 files, the slowness simply would not do.

One day there was some severe weather and a power hiccup during school hours, and every station got a message from ADMIN informing us that the server room was running on UPS power and we should save our files and log out immediately.

Hmmmm.

A few weeks later, one of the bright sparks in the technology program realized that having everyone log off would free up some bandwidth. So he logged onto the next machine over as GUEST, and used a NET SEND ALL "SERVER ROOM POWER FAILURE - 11 MIN OF BATTERY REMAIN - SAVE FILES AND LOG OFF" and sure enough, within about a minute, the whole T1 was his. Did what he needed to do (i.e. leeching an entire fserv) for about 8 minutes, then NET SEND ALL "POWER RESTORED - RESUME YOUR WORK".

A few weeks later some hot commodity had just dropped and he repeated the drill. It still worked.

Nobody noticed that these messages came from GUEST, even the district administrator, who eventually called an electrical contractor to figure out why the power in the server room was so flaky. Someone eventually pointed it out to him, which got a very red-faced "that's really clever but please knock it off", and no further punishment. The next day, the Guest account had a lot fewer privileges.

replies(10): >>43548542 #>>43548580 #>>43549207 #>>43549937 #>>43550153 #>>43550197 #>>43551279 #>>43551610 #>>43551791 #>>43552941 #
pests ◴[] No.43548542[source]
I had discovered the windows net send command as a highschooler too. We mainly just messaged jokes back and forth. One student later decided to try the wildcard to send to everyone, just a simple "Hi". It went out over the entire district hitting multiple schools. I forget why, but no one knew who did it at first. But we had some software installed that let the admin/teacher remotely blank screens or lock the computer, etc. I remember they blanked his screen remotely and once he complained they knew it was him. Didn't get in too much trouble, but I still felt bad for teaching everyone about net send.
replies(5): >>43548595 #>>43548897 #>>43549501 #>>43552644 #>>43555725 #
1. BrainBacon ◴[] No.43548897[source]
I did the same thing by accident, except mine was "test", I heard murmors around about some strange message on computers in multiple schools in our district, so I fessed up immediately. Our network administrator was just mildly amused about the whole affair and no punishments were carried out.