>We had an incident recently where someone used the same IP address on a
>(a PC running winsock) as one of our fileservers... nevertheless, the
>fileserver spazzed out, NFS went completey awry, and we were forced to
>start rebooting clients and the server to get things back to normal.
>Besides going to 10BaseT (star configuration, intelligent hubs that only
>pass the proper IP address to the client connected to that leg of the hub)
>Is there any way to prevent this? ANYONE can edit their Winsock configuration
>and make the IP address the same, and really hose your network... And this
>is internally... How do you prevent this, short of spending TONS of money
>on new hubs?
1. Put your production boxes on their own subnet.
2. Bootp your users
Before anyone says anything, bootp doesn't STOP them from using a valid
address, but it will stop them from doing so "accidently".