Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Glenn You are right, but I was talking about an entry in TCP/IP settings on the lan adapters and NOT in HOST file. The host file was correct even during the problem with cvslock. I think the problem was related to the double mode of the net. The office mode (with dhcp) and the home mode with a static ip address. Regards, Mauro "Glen Starrett" <glen.starrett at march-hare.com> ha scritto nel messaggio news:ekkn9n$tku$1 at paris.nodomain.org... > Mauro Maniforti wrote: > > Simply adding 127.0.0.1 fix the problem. This seem to force the use of host > > file or any local trick to resolve host names. Honestly is not clear to me > > why this was a problem, if someone can exmplain me more it will be very > > appreciated. > > That entry is there by default! By removing it in the first place you > effectively broke your own networking. > > I was able to reproduce the behavior on my notebook by editing my > system32\drivers\etc\hosts file (commenting out the localhost line) and > turning off my wireless adapter. If either the line in the hosts file > or the adapter are on, then it works properly. > > Conclusion: Leave the default entry in your hosts file alone. AFAIK > even unix machines have a hosts file with the localhost entry in them, > and it is required for proper operation of the machine. > > Regards, > > -- > Glen Starrett