>>>
>>>if you really want localhost to resolve to an IP address, you can add an entry to the hosts file (System32\drivers\etc.). However, I'd strongly recommend not using the name "localhost" for this.
>>
>>Humm... really?? why?
>>
>>Some applications, scripts of others not uses the UNC... But the URLs... And a crm script that I always wants to use, we never did that because it works with a sort of http://localhost/clientsgroupsa etc...
>>
>>And also seems more organized to me if we create a standard localhost instead of numbers...
>
>These days, some services expect that "localhost" refers to the local machine, usually resolving to 127.0.0.1. For example, the software suite for some HP printers installs an Apache Tomcat web server on your local machine. Changing the IP address for localhost could cause services like this to fail.
>
>Just create some other make-believe name, and add that to the HOSTS file on workstations. The name just needs to be something people won't want to access on the real Web. If you want to be sure it won't conflict, you can use an imaginary sub-domain of a domain you own e.g. mytestserver.bemimovel.com. You would then add a line to the HOSTS file, something like
>

>mytestserver.bemimovel.com    192.168.xxx.xxx
>

>Then, when someone visits http://mytestserver.bemimovel.com in a Web browser, they are directed to your test server at 192.168.xxx.xxx.

cool one... to our needs (intranet)... we need basically to create some stuff as http://servidor (server in portuguese).. tks