DeadlyDays :
Use ipconfig on the command prompt and give us the IPv4 Address listed under the WAN adapter heading. I assume you are net getting assigned a proper address from the DHCP server after you connect to the router wirelessly, typically windows will give you a 169.x.x.x address if the DHCP doesn't assign you one.
From working a DSL line I know routers tend to have this issue after a few years where the DHCP service starts to go wacky.
I'm asking both you and Mesmurized, I guess. I checked the ipconfig from the cmd prompt and received the following:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Adam>ping google.com
Pinging google.com [65.196.188.55] with 32 bytes of data:
Reply from 65.196.188.55: bytes=32 time=28ms TTL=59
Reply from 65.196.188.55: bytes=32 time=27ms TTL=59
Reply from 65.196.188.55: bytes=32 time=27ms TTL=59
Reply from 65.196.188.55: bytes=32 time=27ms TTL=59
Ping statistics for 65.196.188.55:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 28ms, Average = 27ms
C:\Users\Adam>ipconfig
Windows IP Configuration
Wireless LAN adapter Wireless Network Connection 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : home
Link-local IPv6 Address . . . . . : fe80::3de3:2a2e:1d3e:419c%11
IPv4 Address. . . . . . . . . . . : 192.168.1.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : home
Link-local IPv6 Address . . . . . : fe80::28c9:40e1:4709:1376%10
Default Gateway . . . . . . . . . :
Tunnel adapter Local Area Connection* 33:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :