Re: windowsxp and flushDNS

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Miha Pihler (mihap-news_at_atlantis.si)
Date: 07/29/04 

Date: Thu, 29 Jul 2004 09:47:50 +0200

Hi John,

Sorry, but what exactly is the problem?

ipconfig /flushdns fill only clear out DNS cache. You get same result if you
stop or restart DNS Client on your WinXP client. To release your IP address
your need to type in ipconfig /release and to get IP back your type in
ipconfig /renew.

If you do the ipconfig /all one of information that you can see is DHCP
server. Check which server or device assigns you the DHCP IP.

If you would like your client to have specific IP, create a MAC reservation.

There can be more then one DHCP server in LAN. Once your client is started
it will "shout" on the network "are there any DHCP server that would like to
give me an IP?" It will take the IP from first response on the network.

Mike

"John Gerard" <JohnGerard@discussions.microsoft.com> wrote in message
news:E6FADE3A-C3E1-400E-9C11-2C0D4A5905D9@microsoft.com...
> Hello,
>
> I have a rather simple problem. I have one Windows 2000 server I just set
up. I have 2 client PC one is a Windows XP Home Edition PC and the other is
running Windows XP Pro. The WinXP Home PC has acquire the correct IP
address setup in DHCP. I am having a problem with the XP Pro PC where is it
showing in ipconfig /all an IP of 192.168.2.101. Both PCs are set up for
Dynamic updating of both IP and DNS settings. During setup of the Server the
Linksys router was set to DHCP starting address of 192.168.2.100. I tried
to perform a ipconfig /flushDNS on this PC but when I renew the IP address
it keeps acquiring the IP of 192.168.2.101. I double checked and dhcp has
been disabled in the router so the PC should not be looking for the address
there.
> I am thinking that there is some bug or registry edit I need to perform to
correct this problem. Any suggestions?
>
> Thanks,
> --
> John

Relevant Pages

  • Re: My Server is not anymore seen on network plese help ?
    ... here is the client ipconfig. ... wich as adress 192.168.1.102 which it is not reachable for some reason ... As you can see the DHCP ... Microsoft Windows Small Business Server 2003 Best Practices Analyzer ...
    (microsoft.public.windows.server.sbs)
  • Re: Application Hang
    ... Back to DHCP, what about the client ipconfig without the DG ip address? ... When the old server crashed, it required a new motherboard and CPU. ... You should see at least,006 DNS servers, 003 Router. ...
    (microsoft.public.windows.server.networking)
  • Re: Windows Server 2003 DHCP server - Does not release IP Addresses
    ... on the SWITCH or the ROUTER. ... the clients will not know which server to go for DHCP REQUEST. ... And, if that Switch had some issues, how will the other DHCP server ... This error is usually received when the client booting up via PXE is ...
    (microsoft.public.windows.server.general)
  • Re: DHCP handles Naks one one vlan differently
    ... If the problem is on the network with the DHCP server, ... Frame 156 ... Your (client) IP address: 0.0.0.0 ...
    (comp.dcom.sys.cisco)
  • Re: Sending hostname with DHCP
    ... default route and the default dns host. ... Below is my /etc/resolv.conf created by the dhcp client. ... > This seems to depend on the client as much as the server. ...
    (Fedora)