I am a software trainer. Training facilities clone a master image onto multiple machines for the students. Previously, we used to name these student machines S1, S2, S3, etc.
The downfall to this, was that the hostname change meant we had to tweak every machine manually to fix things in IIS and some Server software we are running.
So, to avoid this, we have been doing some testing with cloning the images to S, S, S, S, etc
This means we have duplicate hostnames in the same workgroup. I don't care, as long as each machine still behaves itself. I think they need to be on the same workgroup in order to get internet and also for a license which they can all share.
However, I was thinking there would be problems with a local machine trying to hit an address and being confused with there being duplicate addresses to hit.
So far tests indicate that everything is working ok:
If I dump a helloWorld.txt under the root of IIS on one machine (http://S/helloworld.txt) I can hit it fine from that machine, but if I jump on another machine, I cannot hit it (which is good).
I heard there was some way to completely rule out the machines from getting confused with each other, you could tweak the hosts file with some sort of loopback command to 127.0.0.0/8 to ensure that the duplicate hostname machines would not conflict with each other?
Can anyone point out how to ensure the machines with duplicate names take their local address to be the one to use over other machines (both in IIS and any other protocols)
Hope I have clarified that OK - let me know via comments if not.