So, I needed to step away from this for the night. I tried all the newest suggestions, and have come up empty handed.
Since he's able to get an IP from the router - and presumably can talk to the LAN ... I'd recommend pasting the outputs of these commands:
ping 192.168.1.1
ping 209.244.0.3
tracert -d 209.244.0.3
results:
192.168.1.1Pinging 192.168.1.1 with 32 bytes of data
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Ping statistics for 192.168.1.1:
Packets: sent = 4, received = 4, Lost = 0 (0% LOSS),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1 ms
209.244.0.3Pinging 209.244.0.3 with 32 bytes of data
Reply from 209.244.0.3: bytes=32 time=346ms TTL=56
Reply from 209.244.0.3: bytes=32 time=369ms TTL=56
Reply from 209.244.0.3: bytes=32 time=370ms TTL=56
Reply from 209.244.0.3: bytes=32 time=368ms TTL=56
Ping statistics for 209.244.0.3:
Packets: sent = 4, received = 4, Lost = 0 (0% LOSS),
Approximate round trip times in milli-seconds:
Minimum = 346ms, Maximum = 370ms, Average = 368 ms
tracert -d 209.244.0.3Tracing route to 209.244.0.3 over a maximum of 30 hops
1 1ms 1ms 1ms 192.168.1.1
2 * * * Request timed out
3 9ms 10ms 8 ms 68.87.183.229
4 19 ms 19 ms 19 ms 68.85.162.45
5 27ms 22ms 21ms 4.68.110.89
6 * 22ms 19ms 4.69.140.90
7 23ms 25ms 23 ms 4.69.140.98
8 27ms 24ms 24ms 4.69.134.70
9 130ms 64ms 84ms 4.69.155.67
10 29 ms 28ms 23ms 209.244.0.3
Trace complete