Vista - Windows dosn't recognise connection D-Link ADSL router

I am using a D-Link DSL-G604T wireless ADSL router with a Vista Home premium
system on an AMD Athlon 2800+ with 1GB of Memory. Just recently my computer
lost contact with the router (ie. it returns the error message "limited
connectivity" and the network centre doesn't acknowledge any connection with
the internet.) Vista's "Windows Network Diagnostics" attempts to fix it by
one of 2 ways - Auto assign new IP settings, and resetting the network
adaptor, neither of which work. Rebooting the router doen not work either.
Concidently it began around the time I was installing an update on some
software that ended up not installing properly which I subsequently
uninstalled. Hence I believe it may be a software problem. Definitely not
the router as I can still use the router through my notebook. It's not the
ethernet cable running between the router and the desktop as I switched the
cable and that made no difference. I'm thinking it's either the network card
in the desktop failing or a software corruption of some sort but don't know
how to progress the diagnostic further from this point.
I have tried restoring to just before the failed installation but to no avail.
Can anyone tell me how to test the netwotk adaptor to see whether it has
"blown a fuse"??

On Wed, 6 Feb 2008 02:35:02 -0800, Jason T
<JasonT@xxxxxx> wrote:
Shut everything down, the pc, the router, the dsl modem, everyhting.
Then turn on the dsl modem, wait 2 minutes and turn on the router,
wait 2 minutes and then finally turn on the pc. If the pc has an IP
address of 169.something then you are not getting an IP address from
the router.

Did you try rolling back the ethernet adapter driver? Some 3rd party
firewall software can cause these sorts of problems if they incorrectly
detect the ethernet connection as a new connection and put it into the wrong
zone or otherwise block connections to the router. Sometimes you can fix it
manually in the firewall or by resetting it to the default configuration,
other times it could require uninstalling and reinstalling the firewall.

"f/fgeorge" <ffgeorge@xxxxxx> wrote in message
news:j34jq3lcsittqud2l6069vmgrmnafle3fn@xxxxxx