From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <20030220101316.14994.qmail@mail.prosyst.com> References: In-Reply-To: From: Nikolay Paskov To: 9fans@cse.psu.edu Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: [9fans] Re: ip resolving Date: Thu, 20 Feb 2003 10:13:16 +0000 Topicbox-Message-UUID: 6af60228-eacb-11e9-9e20-41e7f4b1d025 Russ Cox writes: >> Now it works. Why I can't use 132.187.1.1 instead 192.168.79.2 ? >> I have nat what is the problem? > > did you change it manually to 132.187.1.1? > i have a hard time believing vmware set it to that. > how did it get set to 132.187.1.1 in the first place? > > first of all, 132.187.1.1 is likely to be a router > rather than a dns server. vmware may be blocking > dns packets except the ones to itself. i don't know. > just use the vmware ones. > No, 132.187.1.1 is not a router I'm using it as DNS server on my linux box. I changed it manually of course. But may be you are right about blocking from vmware side. I have to check this. BTW now I have a problem with the DHCP server. Nothing is changed in configuration only rebooted and now I have no response from the DHCP server.