[mickeyp]

Heh. If you used the underlying windows api calls, you could spoof the sender. Something I discovered when I did just that, in the Windows 2000 days.

Combine it with a for loop and you could generously message everyone on the LAN with little effort.

There's a reason why everyone around me turned off the net service after a while...

[Zach_the_Lizard]

I did something like this, also on Windows 2000, when I was in high school. It definitely surprised some teachers....

I also discovered that our student IDs and PINs were based on our birthdays, though I was not creative enough to come up with an amusing use of student logins.

[stordoff]

One of my friends figured that out a few days after someone sent a net send message to * (they got away with that one by logging in as another user who wasn't in the room before the IT staff VNCed into the machine to see who it was). We ended up getting messages from "GOD" for a while before net set was disabled entirely. One of the teachers knew about this, and his only comment was "if you're going to mess around with this, don't get caught".

A group of people did get caught messing around with the network a while later, but only after they'd privesced their way to a domain admin account, then screwed up with a script that reset a bunch of local admin passwords rather just the one they wanted. Somehow, the existence of a new domain admin account didn't get spotted for weeks before that.

[robrorcroptrer]

Hehe yes, the API was called something with named pipes IIRC. I created a GUI in Delphi that could spoof net send sender and used it at LANs and school.