• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 206
  • Last Modified:

2000 Machine won't get IP from DHCP server

I have a client who I set up a wireless network for.  Everything was working fine, and I get a call one day that it's not working.

Hmm.

Background info: 3 wireless PCs, one wired.  3 are 2000 and one is XP.  The XP one is wireless and I just use Windows WZC with it since it's easier.

I checked out the one wireless machine, for some reason the adapter's software wasn't seeing that it was installed and active (though in Device Manager it was).  I didn't have time to troubleshoot, so I removed the card and installed a wireless USB adapter.

I did the same on the other machine.  I also changed the WEP key on the router while I was resetting everything, and I made sure all the wireless machines had this new WEP key, typed exactly as it was on the router.

Two of the three wireless PCs are fine, working great.  This one is being a real pain.  I used the configuration software (Netgear) to connect to the network and apply the WEP key and it would connect to the network and show me its signal strength and throughput but it would receive an autoconfiguration IP address.

So I pulled out the PCI adapter and put in a USB adapter, same problem.  So that more than likely rules out a hardware issue.

Since it seemed like it was connecting to the router I tried specifying a static IP - nope.

I had this happen to me before and I can't remember what I did to solve it.

Any ideas?  Hopefully I can get it fixed tomorrow or Wednesday.

Thanks!
0
christo87
Asked:
christo87
  • 3
  • 3
  • 2
1 Solution
 
Jay_Jay70Commented:
Hi christo87,

can you scrap the netgear sw and let windows handle it?

Cheers!
0
 
Rob WilliamsCommented:
Try going back to basics. Remove all encryption, MAC filtering etc. and see if you can establish a connection. If so then gradually add the security features. For example, I have had some driver versions that will not support 128bit WEP but would 64Bit.
Also, a long shot, but you haven't made your DHCP range on the router so small that you have run out of IP's have you?
0
 
christo87Author Commented:
Jay_Jay70 - it's 2000, how would I configure Windows to handle it?

RobWill - No MAC filtering, I want to see if this can be done without taking the encryption down (since I want to see if I can guide them over the phone), but if it comes to it I can go on site.  The range has enough addresses for everything.

Thanks!
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
Jay_Jay70Commented:
ah my bad :) so used to xp machines these days......

0
 
christo87Author Commented:
Taking the encryption down didn't work,

I disabled APIPA via the registry so it wouldn't go straight to 169.254...tried WinsockFix, uninstalled and reinstalled TCP/IP...nothing.

Any ideas?
0
 
Rob WilliamsCommented:
Have you been able to resolve as of yet? If not, have you tried updating the firmware?
0
 
christo87Author Commented:
Tried updating the firmware, no go.  Maybe it's the adapter, who knows.

At any rate, the client decided to get a new system which is working fine (I'm on it right now migrating data).

Thanks for the effort!
0
 
Rob WilliamsCommented:
Thanks christo87,
Sorry not more help, but it seems you have a solution one way or the other.   :-)
Cheers.
--Rob
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 3
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now