Hello,
I have a machine, that I have installed the x64 version of XP Pro onto, which has three onboard network adaptors; two gigabit ethernet and one wireless 54G.
I'm having a problem connecting to my LAN, though...it was fine until I rebooted after running Windows Update onto it, now it can't see the network at all from any adaptor.
To make life simple, I've disabled all but one of the gigabit adaptors, which has an IP address of 192.168.32.248. The network it's attached to is the 192.168.32.0/24 subnet, but the only address it can ping is itself. If I try and ping another address within the same subnet (192.168.32.249 - my gateway, for example) I get the error "Destination Host Unreachable".
It's as though this machine has isolated itself from the rest of the subnet - I've tried clearing out the routing table, but this had no effect. I know Server 2003 does this when you first install, to protect the server before you've run in the updates, but I've never seen XP do it before...
Like I say, it was working fine before I updated it and I even joined it to my domain, which I'm wondering now whether that's part of the problem...
Any thoughts will be much appreciated,
Thanks,
Paul
I have a machine, that I have installed the x64 version of XP Pro onto, which has three onboard network adaptors; two gigabit ethernet and one wireless 54G.
I'm having a problem connecting to my LAN, though...it was fine until I rebooted after running Windows Update onto it, now it can't see the network at all from any adaptor.
To make life simple, I've disabled all but one of the gigabit adaptors, which has an IP address of 192.168.32.248. The network it's attached to is the 192.168.32.0/24 subnet, but the only address it can ping is itself. If I try and ping another address within the same subnet (192.168.32.249 - my gateway, for example) I get the error "Destination Host Unreachable".
It's as though this machine has isolated itself from the rest of the subnet - I've tried clearing out the routing table, but this had no effect. I know Server 2003 does this when you first install, to protect the server before you've run in the updates, but I've never seen XP do it before...
Like I say, it was working fine before I updated it and I even joined it to my domain, which I'm wondering now whether that's part of the problem...
Any thoughts will be much appreciated,
Thanks,
Paul