I use a wired connection to a DI-514 router. Last night, my connection dropped randomly while my roommates all kept their connection (4 wireless laptops/PCs a wired XBOX360).

Done the obvious things like resetting the router and renewing my IP to no success.

I have my network settings set to automatically obtain IP. When I do an ipconfig, I get:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 169.254.218.106
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

I noticed that if I try to make changes to Internet Protocol (TCP/IP) Properties such as trying out different IPs, the window kind of locks up as though it's busy. I can close the window but it does some weird stuff to my desktop so I reset my computer.

Overall it's a huge hassle and I have little knowledge of how all this works.

Any help is really appreciated. Thanks

Try setting a static IP on your PC ... IP in the subnet range (but outside the normal DHCP range):

So if your router is at 192.168.0.1 (which I think the the default for most D-Link routers), the DHCP range is probably 192.168.0.100 - 192.168.0.199, so set:

IP: 192.168.0.250
Subnet mask: 255.255.255.0
Gateway: 192.168.0.1 (your router's IP)
DNS: 192.168.0.1 (your router's IP)

Paul B said:
Paul,
The first thing that JUMPS out at me is the IP Address of 169.254.218.x. This is a pseudo address that DOES NOT WORK, but is ASSIGNED LOCALLY when DHCP does not work.
The lack of a "Default Gateway" also points to no DHCP connectivity.
You have no "real" or "RF-1819 address", nor any internet usable address.
Given that you do not have a good address, you have NO gateway.

This seems to indicate that though you may have some connectivity, the wired, or WIFI connectivity is not good. Look at the physical wiring. You can have a "green light" and still be bad. Look at the router for auto/100/1000 BaseT support on the port you're plugged into.
Make sure that you're set up for DHCP and that the router is also set up.
Make sure you have good cables, and that the configuration on the Switch hasn't chaged.
Make sure the drivers update didn't change something that you need to modify, and have done in the past.

Gerritt

Thanks, but it didn't seem to do it.

Here's the weird part that might help someone figure this out. When I set something like the Static IP and click OK, the LAN properties window kinda freezes and you get a busy animation when you hover over it. The IP doesn't change (checking with ipconfig) until I shutdown which usually has to be done manually because the job is still running. When I do reset, the new IPs etc. are in ipconfig.

Seriously hope this isn't a hardware issue.

EDIT: I saw your post Gerritt right after submitting mine, I'll read what you posted.

Are you using onboard networking or an NIC?

If you go into Add or Remove Programs, then Add or Remove Windows Components, click on Networking Services, and uninstall, then reinstall these services.

The fact it freezes when yu try and assign an IP, probably means the OS is struggling to communicate with your NIC or onboard networking chip.

Hmm, well as it turns out, I tried the Static IP thing but this time turned it on and off twice with the same settings... And it seems to have worked.

But yeah, I have onboard network stuff. May have to check drivers?

Thanks.

Woo, at least it's working ... whenever I have a problem with DHCP, the first thing I always try is a static IP.

Even if a static IP address is working for you right now, it may not always work.
Unless all systems within your DHCP domain recognize that you've set a static, the DHCP Server may re-assign the same IP as you are using to another system. This may be what has been happening to you in reverse.
You've found a way around the problem, but have not yet established the root cause, so it may come back and bite you at any time.

Gerritt

... which is why I recommended he set a static IP outside of the DHCP pool range. Although I do agree with you, the root cause has not been found, this is just a workaround.

Yes, I agree that I need to find the root cause.

Could it be anything driver related?

Not sure on drivers, that would be one of the last things I would look at in that situation. I suppose if you can connect with a static IP but not DHCP, check to make sure the DHCP client service is running and set to Automatic in services.msc.

Check the DI-514 and make sure the DHCP Server is enabled and that the pool of addresses is large enough to support all of the devices. ie 192.168.0.2 - 192.168.0.128.
This would allow for dynamic assignment out of the 2 through 128 pool while leaving 129 - 254 open for static assignments.

Gerritt

I woke up this morning and the connection was gone again. I'm pretty sure the static IP I took is outside the DHCP range but I'll mess around with it when I get home later.

This is a little late in the game but have you checked the cable and connectors?
A flakey connector or a high resistance connection that opens after heating, could be causing some of the indications.

Gerritt

I checked with another cable and it was still down. Might be the adapter.. They're pretty cheap so I may try to pick one up.

My connection has been on and off (up one day, down for half a day, up for 2, down for 1, etc) and I don't think it has to do with my TCP/IP settings under LAN because it has worked when I had static settings entered or if they were automatically obtained.

Sooo, what do you guys think? Hardware problem?

Dang Paul, it seems we've run the gauntlet.
But, (ain't there always one of those), have you tried to bring up the secondary adapter on your MB? Most today give two, through possibly two RJ45 connectors.
Have you tried wiring it to a different port on the hub/switch/brouter?
These are the only things that I've got left.....
Good Luck!

Gerritt