DHCP server unavailable new machine -- newbie

[zbucklyo]

I apologize if this has been answered before, but I've spent an hour searching the forum and haven't been able to find anything. I'm a high end, but not IT professional, user, who stumbled on this site through google.

Brand new XP Pro machine, exhibiting the following, when trying to connect to RCN cable modem (have WIN2k machine that connects no problem):

1. Can't find DHCP server, so auto assigns 169.254.x.x IP address.
2. DHCP client service is running.
3. Automatic IP address etc. checked.
4. 3 com adapter 10/100/1000 on motherboard, diagnostics indicate ok, but also fail DHCP server test.
5. Tried ipconfig/release/renew to no avail with same issue.
6. Physical Cable is fine, as third light on cable modem comes on when connected, and software indicates connection. When cable unplugged from cable modem, software notes dropped connection.
7. However, initially tried to run through Netgear router, and router failed to recognize connection altogether -- no connection present.
8. Even though new machine, with no virus software on it, and no viruses (it has never been connected to the Internet), I did try the winsock fix executable suggested by bill castner. This did not work.
9. Many packets sent, zero packets received.

I'm totally frustrated, annoyed, since this should be a very simple thing to handle.

Any other suggestions, or should the operating system be reinstalled? (it came preinstalled), and connecting to the internet is the first thing I tried to do, other than fixing the annoying xp interface.

Thanks for your help...

 

[zbucklyo]

Two more things to add:

1. I did try the XP supplied "fix connection" -- it also failed when trying to renew the connection.

2. ICF is turned off, and there are no third party firewalls running on the machine

 

[dearingkr]

Have you tried re-installing drivers using the newest ones on the internet?

MCSE CCNA CCDA

 

[zbucklyo]

The latest drivers on 3coms website are as of 2002, so I assume that this machine which is new, is up-to-date

 

[dearingkr]

You mentioned that you have a link light on the cable modem, you should also have a link light at the NIC. If not then you have a bad cable or NIC. Even if you do have a link at boths ends, you could still have a bac NIC.

Have you tried installing a different NIC for testing purposes?

MCSE CCNA CCDA

 

[zbucklyo]

The link light is on at the NIC end as well, and the 3com diagnostics indicate that the NIC is ok.

 

[dearingkr]

Can you get on the network using a static IP?

MCSE CCNA CCDA

 

[zbucklyo]

It doesn't work with static IP either, but I just realized I've overlooked the main symptom anyway -- the fact that there are zero (and I mean zero) packets being received. It is not a DHCP issue, other than, because it can't receive packets, it can't connect to sever. So it is possible that despite passing the hardware self-test, there is a problem with the hardware. In any case, this is not the appropriate forum. Thanks for your help