DHCP IP failing

[krma-thkpds]

If I let DHCP to assign IP address to my machine automatically I don't receive any packages. Though the connection is connected, there is just no transport. And in connections there are no messages indicating anything is wrong.

So I manually assigned IP to the machine and entered DNS server and now it works. Anyone knows why DHCP assigned IP doesn't work for me?

PS.: It worked well since yesterday, when I installed Intel Chip-set Support. Does this has to do anything with it?

[jdhurst]

Unless your TCP/IP stack is somehow corrupted, DHCP should work whereever a manual IP works. Just make sure that all settings including IP, DNS and another settings have been set to default (cleared) for DHCP. I would not think Chip Set support would have anything to do with it.
... JD Hurst

[krma-thkpds]

No, if I clear the fields the connection persists, but I am unable to open any page, sign into any web based service etc.

Do you think this could be some kind of a driver problem?

[GomJabbar]

What JD Hurst mentioned is where I would look first. Below are a couple of links that can help. Open with Internet Explorer.

How to recover from Winsock2 Corruption

Troubleshoot TCP/IP Connectivity

[Kyocera]

How are you connected? DSL, router, etc. You can check your tcp/ip by pinging 127.0.0.1, this basically pings your nic and ensures your nic and tcpip stack is communicating. If you are behind a router at home I would check the router vendor web page for support/faq's. It would help to know a little more about your set up. Can you ping a web site with an assigned IP address? Do an ipconfig /all from command prompt and check your ip address, subnet, etc. there may be something going on there. Gomjabber is right about the winsock issue but it is rare, if you use any tools to try and fix the winsock issue, I suggest creating a restore point.