I've just setup a Windows 2008 R2 Terminal Server with IE9, it's intended to be used for testing. Unfortunately the web-bods tell me they ALL have a local apache on their machines and they've all edited their hosts file with lots of entries pointing to 127.0.0.1 (loopback).
This works fine on their own machine to point them at their own apache to see their results as they're developing on their Windows XP machines.
Of course, when they log onto the terminal server, they're not going to be able to access these, the hosts file is machine-based and multiple users could be on the Terminal Server at once.
I've been trying to think of a way that when User A logs onto the Terminal Server, a set of rules (in a file or location they can edit) unique to them are loaded and when they type in test.site1.com it will point it to their computer's IP 192.168.1.1 and User B types test.site1.com it will point it to User B's computer IP 192.168.1.2, this is while both users are logged onto the Terminal Server at the same time (lets say 192.168.1.10).
Ideally want to avoid having to make too many changes to their local apaches (besides making sure they listen on their actual LAN IP and not just 127.0.0.1 of course).
Hosts file is out from what I can tell... is there a clever proxy program that can do this? One I could install on the Terminal Server itself that will accept user-based config files? Or DNS as suggested below, great idea, again the only issue is providing different IPs for the same hostname to the respective user.
test.site1.com 192.168.1.1 for User A test.site1.com 192.168.1.1 for User B
This is while both User A and User B are logged onto the same Terminal Server.