Microsoft Windows XP Home

Discussion in 'Windows Desktop Systems' started by dreamworks, Oct 21, 2003.

  1. dreamworks

    dreamworks --== babyface ==--

    Messages:
    355
    I have recently added a few machines running on Microsoft Windows XP - Home edition in my network and suprisingly, all the machines that have been installed have the same ip address at 192.168.0.25 even though they are set to obtain an ip from the DHCP server.

    Any reason to this please?? : (
     
  2. dreamworks

    dreamworks --== babyface ==--

    Messages:
    355
    No one is willing to help me?? :confused:

    :eek: .. just like to know why is all the machines running on win xp home on my network automatically takes 192.168.0.25 as its IP and despite that no message of conflict of ip address? thats all ..
     
  3. Mr. K

    Mr. K OSNN Occasional

    Messages:
    75
    Location:
    Ottawa, Canada
    This may be a dumb question, but are you sure you're not looking at the Subnet Mask or Gateway addresses?

    Are you viewing the IPs on the individual machines or a client list on your DHCP server?
     
  4. GoNz0

    GoNz0 NTFS Stoner

    Messages:
    2,781
    Location:
    the year 2525
    thats the default ip when windows can't obtain an ip addy by itself.

    set the ip's manually.

    192.168.1.2
    192.168.1.3
    192.168.1.4
     
  5. dreamworks

    dreamworks --== babyface ==--

    Messages:
    355
    Its the IP on the client machine which I am looking at by typing the command ipconfig in the command prompt.

    Anyway, there is a DHCP server on the network and all other machines (running on Win98SE or Win2K) is able to obtain ip address from it except for these Win XP Home machines.

    I wish not to set the ip address manually, which is why the reason for the DHCP server. But I am puzzled, why all the Win XP Home machines? Even my Win XP Pro machines can obtain their IP address from the DHCP machines. : (
     
  6. muzikool

    muzikool Act your wage. Political User

    I don't know why Home is doing this when Pro is not, but I do know that those machines would not be able to access the network while all having the same IP. In other words, these machines are not actually receiving this IP from the DHCP server, nor are they actually registered on the network. My guess is that your issue is due to Home's lack of advanced networking features, but I'm not sure what specifically is causing the problem.

    For testing purposes, I would assign IPs manually, just to see if that gets the computers on the network. If so, you can work from there in solving the issue. Also, is the ICF disabled on those machines? If not, that could cause problems.