T
TheScullster
Hi all
Hoping someone will be able to explain how IP addresses are assigned.
I have a laptop (formerly used on our corporate network) which I am
struggling to get onto my home network.
AIUI, at work our domain controller acts as DHCP server and "issues" an IP
address to each client that logs on.
With the laptop at home, where does this IP address get allocated from?
I have no DHCP/domain server at home - just a peer-peer wired network of XP
machines connected via a Netgear switch.
The point to which the laptop is connected at home, previously had another
desktop PC networking correctly.
I only currently have one other PC connected to the network, but this seems
fine.
Have googled this and found that it is a common fault with wireless
devices - not wired.
The error I am getting is "Limited or no Connectivity".
So far I have tried:
Releasing the IP address and renewing with ipconig.
Applying the patch from MS KB 884020
Repairing the broken IP status
Is the problem that the PC believes that it is still a member of a domain
and expects an IP address to be assigned in this way?
When connecting (or attempting to) at home, I have logged on to the machine
itself as local admin.
Any comments/suggestions on all this very welcome
Phil
Hoping someone will be able to explain how IP addresses are assigned.
I have a laptop (formerly used on our corporate network) which I am
struggling to get onto my home network.
AIUI, at work our domain controller acts as DHCP server and "issues" an IP
address to each client that logs on.
With the laptop at home, where does this IP address get allocated from?
I have no DHCP/domain server at home - just a peer-peer wired network of XP
machines connected via a Netgear switch.
The point to which the laptop is connected at home, previously had another
desktop PC networking correctly.
I only currently have one other PC connected to the network, but this seems
fine.
Have googled this and found that it is a common fault with wireless
devices - not wired.
The error I am getting is "Limited or no Connectivity".
So far I have tried:
Releasing the IP address and renewing with ipconig.
Applying the patch from MS KB 884020
Repairing the broken IP status
Is the problem that the PC believes that it is still a member of a domain
and expects an IP address to be assigned in this way?
When connecting (or attempting to) at home, I have logged on to the machine
itself as local admin.
Any comments/suggestions on all this very welcome
Phil