Hi - hope someone can help!

I have a W2K machine that has worked on the network, but has had some 'tinkering' done on it and now i cant get it to work. It doesnt appear to find the dhcp server (which is our router), and therefore isnt assigned an IP address. Trying ipconfig /all, i get:

Connection specific DNS suffix :
Description : Intel(R), etc
Physical Address : etc
DHCP enabled : Yes
Autoconfiguration Enabled : No
IP address : 0.0.0.0
Subnet Mask : 0.0.0.0
Default Gateway :
DHCP Server : 255.255.255.255
DNS Servers :

If I try fixed IP, it works and I can see all machines on the network, but I am unable to get connection to the internet.

I have tested all hardware, by unplugging the network lead from the 'faulty' PC and plugging it into a knoown good one (XP OS though) and this worked OK.

Is there any way I can monitor the W2K network traffic to see whether it is actually attempting to register with the DHCP server?

Is there any handy tips that anyone could recommend for me?

I have just spent the last day trying to fix this and i am just about ready to throw it out of the window (no pun intended!)

Thank for any help

69 Bay

Wireshark, formerly known as Ethereal.

Maybe your router has its own logs, too. But why is DHCP server in broadcast address (255.255.255.255) ?

Hi - thanks for replying

I presume that when the W2K PC boots up, it broadcasts on 255.255.255.255 to find the DHCP server. If the server responds, the address will change to the actual address of the server.

I did try connecting my XP laptop to the hub, which in turn is connected to the router. All worked OK. I then disconnected the uplink to the router and tried again, and the PC came up with similar results i.e. DHCP Server address set to 255.etc.

I dont know too much about networks, etc only stuff that i can pick up off the net (a dangerous thing!)

Thanks again

Mike

Do you have the DHCP Client service running? See the Event Log for any odd messages.

where do i find the Event Log?

I have run MSconfig, and DHCP Client is shown as ticked, and running in the services tab, if that helps

69 Bay

right, I have found the event viewer, and YES there is a problem with DHCP!

I have this listed under a DHCP error:
Your computer was not assigned an address from the network (by the DHCP server) for the Network Card with network address *****.
The following error occured:
An operation was attempetd on something that is not a socket. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.

It looks like the DHCP client is trying to register approx every 5 mins, as there are now 5 errors listed, each 5 mins apart...

I also have another error - I dont know if it is related. Its source is DCOM, the description is:

The server {****} did not register with DCOM within the required timeout.

What is DCOM? Could this be the source of my problem?

Have you any more advice on this problem?

Thanks for helping

69 Bay

You receive an "An operation was attempted on something that is not a socket" error message when you try to connect to a network

YA BEAUTY I HAVE JUST SOLVED IT!!!!

It turns out that my boss had tried to install a Vodafone package to get inetrnet access thro his mobile (Bluetooth). I have just uninstalled this and all works!

WHAT A WASTE OF TIME, BUT AT LEAST I CAN BLAME THE BOSS!!!

Thanks for helping guys

69 Bay

cool
but when the winsock gets corrupted, you can try this too:
http://www.softpedia.com/get/Tweak/N...nSockFix.shtml