hi Pete, Yes I like your solution better - as with most things, there are several ways to accomplish something. Like you, I had never thought of doing it your way - I will though.
Personally I like static IPs better because you at least no where the machine is - now, knowing who's logged onto that machine can still be questionable. The only problem with static IPs is maintaining them - at my last position, we used static IPs for 35 workstations, so that wasn't too bad to keep up with. regards, Mike ----- Original Message ----- From: Pete To: [email protected] Sent: Friday, March 30, 2007 11:20 AM Subject: Re: [php_mysql] Intranet Issue Hadn't thought of doing it that way! But wouldn't the solution that I ended up with - giving the computer acting as server the name SERVER, and calling with http://server - be simpler? We need to stop "automatic IP" soon, so that we can check who is seated at which machine, as part of our in-house security. -- Pete Clark Sunny Andalucia http://www.hotcosta.com/comm_1.htm
