ICS problem. busted tcp/ip stack?

[j_jones]

Ok. Here is what i have. 5 computer network. 2 XP home,
1 98, 1 ME. win 2k pro is the ics host. One of the XP
home's cant connect.

It will not get an ip address from the dhcp server. Goes
straight to 169.254.xxx.xxx. All other computers work
fine (including the other XP). I have switched out the
network cards for known working ones, and the drivers
appear to be fine.

If instead of setting the network nic to obtain
automatically, if i manually assign an ip (192.168.0.5 for
example), i can now ping 1) computers on the network. 2)
computers on the network by name. and 3) computers over
the internet by IP.

However, i can not ping internet machines by name. And i
can't use net send from the problem computer.

from the host, i can ping the problem computer by name and
by ip. File and print sharing works fine from the problem
computer as long as manual ip is stated. When I open up
Ie on the computer, it gives me the "work offline" message.

any suggestions?

 

[Matt]

Sounds like a common Windows problem, Instead of tracking it down, I
normally reinstall the system over itself, and it works fine, I believes its
a bug deep inside some XP coding. In both Pro and Home versions of Windows
XP, the systems have been known to get some sort of errors that completely
destroys the DHCP, leaving you with complete garbage. I would look into this
if I had more time, but like I said, a reinstall normally works. I suggest
you try it.

 

[jjones]

just to clean up my own thread, I did some tracking down
online, and found out the problem and correct it.

The problem was with DHCP in windows, for whatever reason
it was not holding the dhcp server correctly. What I did
was back up the registry and reinstall winsock. XP has a
networks diagnostic tool (search google for XP network
diagnostic) pre-installed that helped me and pointed me in
that direction (it should the dhcp server as being @
255.255.255.255, and I think used a tool I found online
called winsock fix and it cleared it right up. Winsock
fix first detects your windows, and then does the correct
fix. I have had winsock errors before, but this tool is
GREAT. Once i installed it, it fixed my problem within 5
minutes. Ahh, IT work, i love it. 8 days searching for
an answer, 5 minutes to fix it.

You should be able to google the winsock fix program. A
must have tool for any tech.

jjones

 

[Guest]

I am so glad to find this conversation. I was at wits end trying to get to the bottom of this. I will try it and see if it works. It has been 2 weeks for me.