Full Version: Machine won't obtain via DHCP

From: Rich (RICARD00) [#1]
4 Mar 22:01
To: ALL

I have a strange problem that I think is simple to fix but can I put my finger on it? No.

I have a Windows XP Pro machine on an SBS 2008 network. Will it bollocks pick up an IP address though. My laptop connected to the end of the same network cable does pick up an IP address though.

Additionally, if I put a static IP in there I can't browse the network either.

Any ideas?

From: patch [#2]
4 Mar 22:18
To: Rich (RICARD00) [#1] 4 Mar 22:44

Can you change the XP machine's network card? There's not some funky alternate configuration in the IP settings, is there? Though that shouldn't bugger up DHCP, it has to be said.

From: ANT_THOMAS [#3]
4 Mar 22:18
To: Rich (RICARD00) [#1] 4 Mar 22:44

Dodgy network card? Reinstall the drivers? Reseat the RAM? Increase the voltage of the graphics card? Use suggestions as you feel appropriate.

Though I'm guessing you will have thought of the first two already.

From: Rich (RICARD00) [#4]
4 Mar 22:45
To: ANT_THOMAS [#3] 4 Mar 22:55

Changed the card, same issue!

i know it'll be easy, I just need some inspiration, I'm even changing the data switch tomorrow!

From: Daniel Herman (HERMAND) [#5]
4 Mar 22:46
To: Rich (RICARD00) [#1] 4 Mar 22:47

Really does sound like the NIC, unless its something like patch says.

From: ANT_THOMAS [#6]
4 Mar 22:57
To: Rich (RICARD00) [#4] 4 Mar 23:22

TCP/IP issues with Windows then. Try and delete as many of the things in the LAN connection properties as you can and reinstall them? By the looks of it you can't uninstall TCP/IP but you can Client for Microsoft Networks, probably won't help but worth a try.

From: Rich (RICARD00) [#7]
4 Mar 23:22
To: Daniel Herman (HERMAND) [#5] 5 Mar 7:35

I've replaced it, same happens.

From: Hugh et al le J (KOSWIX) [#8]
5 Mar 1:36
To: Rich (RICARD00) [#7] 5 Mar 9:54

Turn it off and back on again.

From: Serg (NUKKLEAR) [#9]
5 Mar 2:59
To: Rich (RICARD00) [#1] 5 Mar 9:54

Reset the TCP/IP stack?

From: Slaves & Bulldozers (SHIELDSIT) [#10]
5 Mar 4:24
To: Rich (RICARD00) [#1] 5 Mar 9:54

Usually when this happens to me I run a Winsock fix tool to fix it. *most times it works, sometimes the bits are too messed up and a repair install is needed. Hope this does the trick for you!

From: dyl [#11]
5 Mar 10:07
To: Rich (RICARD00) [#1] 5 Mar 10:25

Boot a UBCD4Win or some Linux live thing and see if that gets an address. Though it sounds like you're sure it's software not hardware, that should confirm it.

Also, check the DHCP client service is running. I'd suggest SFC, but I've used that umpteen times and it's never fixed anything for me. Any third party firewalls installed? Or have there ever been? If so, run whatever cleanup tool the makers offer. Maybe try safe mode with networkinginging just as an experiment too.

From: patch [#12]
8 Mar 7:09
To: Rich (RICARD00) 8 Mar 13:15

Did you fix it?

From: Rich (RICARD00) [#13]
8 Mar 13:19
To: patch [#12] 8 Mar 13:43

No.

It's frustrating.

From: dyl [#14]
10 Mar 10:42
To: Rich (RICARD00) [#13] 10 Mar 12:41

Maybe you need to force it to reinstall TCP/IP, which I think you can do by adding new hardware, have disk, then choose nettcp.inf or something like that (off the top of my head).

From: Rich (RICARD00) [#15]
10 Mar 12:43
To: ALL

I suspected the switch in the end and I was right, looks like one port on the switch which works with my laptop for some reason but doesn't like the network card in the system in question.

Changed the port on the switch that the patch panel is hooked to and it has all been good.

Very odd, as my laptop works fine in that port and connected to the cable that the system in question is connected to.

From: Hugh et al le J (KOSWIX) [#16]
10 Mar 13:03
To: Rich (RICARD00) [#15] 10 Mar 14:17

Don't you just /love/ computers?

From: Rich (RICARD00) [#17]
10 Mar 14:20
To: Hugh et al le J (KOSWIX) [#16] 10 Mar 15:03

I always enjoy a totally logic defying problem.

Just shows you can never rule anything out!

From: W R O N G bot (DSMITHHFX) [#18]
11 Mar 0:46
To: Rich (RICARD00) [#15] 13 Mar 2:19

>Changed the port on the switch that the patch panel is hooked to

That happened to me about a year ago. Then about 6-weeks later it lost dhcp again, and changing ports on the (5-year old) switch didn't work.

Buying a new switch did.

Oh yeah, forgot to mention... after a forced cable modem "upgrade" two of my pc's started dropping connections like flies. Eventually I realized they were both connected via on-motherboard ethernet. When I stuffed them with pci nics, all was good.

From: Daniel Herman (HERMAND) [#19]
11 Mar 7:39
To: Rich (RICARD00) [#15] 13 Mar 2:19

sounds like it couldve been a speed / duplex mismatch.

From: Rich (RICARD00) [#20]
13 Mar 2:20
To: Daniel Herman (HERMAND) [#19] 13 Mar 12:01

Good suggestion but why would the machine work fine for so long? It's obviously on the switch side and I suspect, as mentioned above, that thw switch will keel over soon.

Show messages: 1-20 21-23

Reply to All

Full Version: Machine won't obtain via DHCP

Back to thread list | Login

© 2010 Project Beehive Forum