Are there many accespoints near your home? Like Sitecom?
I don't think so.
Also, What ISP Modem do you have? Stand Alone or built in router?
If it's a built in router, it's preferred to bridge the DSL modem.
Embarq 660 modem -- CenturyLink (formerly Embarq) support says it's plug-n-play and doesn't require bridging.
And my laptop network card is
Dell Wireless 1510 Wireless-N WLAN Mini-Card
What wireless modes are you using?
Try single mode G or mixed G and N?
Right now it is set to mixed, but I did change to other modes when troubleshooting a couple days ago, and that didn't seem to fix anything. But I can try again and make sure to go through every option.
What security mode are you using? WEP, WPA or WPA2? Preferred is WPA2.
Security mode is WPA-Personal and WPA mode is Auto.
Any cordless house phones?
Yes, two different ones.
Ensure DNS IP addresses are being filled in under Setup/Internet/Manual?
Both primary & secondary DNS show 0.0.0.0
Turn off Advanced DNS Services if you have this option.
It is off.
Turn on DNS Relay under Setup/Networking.
It is enabled.
Setup DHCP reserved IP addresses for all devices on the router.
DHCP server is enabled.
Ensure devices are set to auto obtain an IP address.
I'm 99% sure they are.
Set Firewall settings to Endpoint Independent for TCP and UDP.
I'm not familiar with these. I use Windows Firewall and I didn't see any settings like that, but I'm probably not looking in the right place.
Turn off all anti virus and firewall programs on PC while testing.
OK
Turn off all devices accept for one wired PC while testing.
OK.
Two new issues: Getting DNS Lookup Failed when trying to access some pages. Error 105 (net::ERR_NAME_NOT_RESOLVED): Unable to resolve the server's DNS address.
Also getting
Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.
This is happening with YouTube, but I can access the site if I use an incognito window in Chrome.
It is also happening with the DLink forums, but I cannot access via incognito window.
**This error is happening on both the wired and wireless connections, but access did come back up on the wired connection.