Hello all!

One of our PC's on our network has stopped logging in to the domain
and will not assign itself an IP address. The server is running DHCP
and there are loads of IP's available but I just get the Limited or No
Connection error and an IP is never given to the machine.
I have tried releasing the lease for this IP, but it still cannot get
an IP.

It worked fine until a few days ago!

Any help would be apprietiated.

Ben

The computer may not talk to the DHCP server. If you assign IP manually, can
you ping the DHCP server?

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com


"Boojie" <(E-Mail Removed)> wrote in message
news:bad1e022-5e12-4322-bf77-(E-Mail Removed)...
> Hello all!
>
> One of our PC's on our network has stopped logging in to the domain
> and will not assign itself an IP address. The server is running DHCP
> and there are loads of IP's available but I just get the Limited or No
> Connection error and an IP is never given to the machine.
> I have tried releasing the lease for this IP, but it still cannot get
> an IP.
>
> It worked fine until a few days ago!
>
> Any help would be apprietiated.
>
> Ben

Unfortunatly I won't be on that particular site until a week on
Tuesday so I will have to let you know then.

If it can/can't ping it, what could be the problems?

Boojie wrote:

> Unfortunatly I won't be on that particular site until a week on
> Tuesday so I will have to let you know then.
>
> If it can/can't ping it, what could be the problems?

1.One common problem is loose cables; either at the PC end or at the
other end. Reseat and retry.
2.Software glitches. Reboot and retry.
3.Bad NIC or other bad hardware. Try another PC.
--
Cheers, Bob

On 8 Feb, 11:52, Bob Willard <BobwB...@TrashThis.comcast.net> wrote:
> Boojie wrote:
> > Unfortunatly I won't be on that particular site until a week on
> > Tuesday so I will have to let you know then.
>
> > If it can/can't ping it, what could be the problems?
>
> 1.One common problem is loose cables; either at the PC end or at the
> * *other end. *Reseat and retry.
> 2.Software glitches. *Reboot and retry.
> 3.Bad NIC or other bad hardware. *Try another PC.
> --
> Cheers, Bob

First thing I tried was checking the cable. I used the same cable
attached to the same module in the wall but to a different computer,
it worked fine. When plugged into the faulty computer, both the LED's
glow so I presume it can detect there's something there.

Rebooted many times.

I'm leaning towards the bad NIC answer, it may need replacing.
Strange how it just went out of the blue though, does that sometimes
happen?

Thanks guys,

Ben.

Boojie wrote:

> On 8 Feb, 11:52, Bob Willard <BobwB...@TrashThis.comcast.net> wrote:
>
>>Boojie wrote:
>>
>>>Unfortunatly I won't be on that particular site until a week on
>>>Tuesday so I will have to let you know then.
>>
>>>If it can/can't ping it, what could be the problems?
>>
>>1.One common problem is loose cables; either at the PC end or at the
>> other end. Reseat and retry.
>>2.Software glitches. Reboot and retry.
>>3.Bad NIC or other bad hardware. Try another PC.
>>--
>>Cheers, Bob
>
>
> First thing I tried was checking the cable. I used the same cable
> attached to the same module in the wall but to a different computer,
> it worked fine. When plugged into the faulty computer, both the LED's
> glow so I presume it can detect there's something there.
>
> Rebooted many times.
>
> I'm leaning towards the bad NIC answer, it may need replacing.
> Strange how it just went out of the blue though, does that sometimes
> happen?
>
> Thanks guys,
>
> Ben.
>

NICs are pretty reliable, but any hardware can fail. If you are
comfortable opening the case, you may want to try reseating the
NIC (assuming that it is a card, not a chip on the MoBo).

NICs (cards) are cheap; I got one for $5, and I've seen them given
away at PC flea markets.
--
Cheers, Bob

Boojie wrote:
>
>
> First thing I tried was checking the cable. I used the same cable
> attached to the same module in the wall but to a different computer,
> it worked fine. When plugged into the faulty computer, both the LED's
> glow so I presume it can detect there's something there.
>
> Rebooted many times.
>
> I'm leaning towards the bad NIC answer, it may need replacing.
> Strange how it just went out of the blue though, does that sometimes
> happen?
>
> Thanks guys,
>
> Ben.


Have you tried to "repair" the connection. You do this by
right-clicking on the icon in the systems tray and then selecting
status. Now click on the "support" tab and then click on the repair
button.

If this doesn't work then at the command prompt run this:

ipconfig /flushdns

If this also doesn't work then try this at the command prompt:

netsh interface ip delete arpcache

If this also doesn't work then bang the machine with a 100 ton
hammer!!!!!

Tried the repair function etc.

Just for the record I'm a network engineer so I've tried all the
obvious things, it all just seems to have gone a bit mad. Next time
I'm in I will try a new NIC, I'm sure we have a few in stock.

If that doesn't work then it's hammer time!!

If there is a hardware or cable issue, most NICs would up with a 169.254 IP
address.

I have a similar case where the PC has full network access with a static
address but can't get a dynamic IP address - reserved or not.

My problem is that I'm supporting them on another continent. :-O

"Bob Willard" wrote:

> Boojie wrote:
>
> > Unfortunatly I won't be on that particular site until a week on
> > Tuesday so I will have to let you know then.
> >
> > If it can/can't ping it, what could be the problems?
>
> 1.One common problem is loose cables; either at the PC end or at the
> other end. Reseat and retry.
> 2.Software glitches. Reboot and retry.
> 3.Bad NIC or other bad hardware. Try another PC.
> --
> Cheers, Bob
>