Windogg, I may have you beat with this one.
A few months ago, I had to install a bridge. Doing so, I had to renumber one of my servers (small change from x.x.x.1 to x.x.x.3). We sent out an e-mail with the change to everyone affected. Unfortunately, not all of them understood exactly what a "server IP number" was.
One of our telecommuters who works on site and has to change his IP (damn you windows 98!) thought it was his new IP. So, today at exactly 3:43 PM, he changed his IP to the servers IP and plugged into the network. Thus, dropping *everyone* working on files from the server.
I guess I should be glad the problem was so easily fixed. At least it wasn't hardware. Looks like I need to write some new instructions.
:disgust:
A few months ago, I had to install a bridge. Doing so, I had to renumber one of my servers (small change from x.x.x.1 to x.x.x.3). We sent out an e-mail with the change to everyone affected. Unfortunately, not all of them understood exactly what a "server IP number" was.
One of our telecommuters who works on site and has to change his IP (damn you windows 98!) thought it was his new IP. So, today at exactly 3:43 PM, he changed his IP to the servers IP and plugged into the network. Thus, dropping *everyone* working on files from the server.
I guess I should be glad the problem was so easily fixed. At least it wasn't hardware. Looks like I need to write some new instructions.
:disgust:
