Routing issues

[#1]

I'm unable to get onto google.com, I'm forced to use bing  nslookup resolves www.google.com:
$ nslookup www.google.com
Server: 192.168.1.1
Address: 192.168.1.1#53
Non-authoritative answer:
www.google.com canonical name = www.l.google.com.
Name: www.l.google.com
Address: 209.85.227.106
Name: www.l.google.com
Address: 209.85.227.147
Name: www.l.google.com
Address: 209.85.227.104
Name: www.l.google.com
Address: 209.85.227.99
Name: www.l.google.com
Address: 209.85.227.105
Name: www.l.google.com
Address: 209.85.227.103
when pinging any of the above I get:
$ ping 209.85.227.103
PING 209.85.227.103 (209.85.227.103): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host
When doing a traceroute I get:
$ traceroute -d www.google.com
traceroute: Warning: www.google.com has multiple addresses; using 209.85.227.104
traceroute to www.l.google.com (209.85.227.104), 64 hops max, 40 byte packets
traceroute: sendto: No route to host
1 traceroute: wrote www.l.google.com 40 chars, ret=-1
*traceroute: sendto: No route to host
traceroute: wrote www.l.google.com 40 chars, ret=-1

When I do a traceroute to any other site:
$ traceroute -d www.bing.com
traceroute: Warning: www.bing.com has multiple addresses; using 84.53.134.198
traceroute to a134.b.akamai.net (84.53.134.198), 64 hops max, 40 byte packets
1  192.168.1.1 (192.168.1.1)  1.675 ms  1.009 ms  1.202 ms
2  lo0-central2.pcl-ag02.plus.net (195.166.128.236)  13.138 ms  14.633 ms  14.148 ms
3  gi1-24-221.pcl-gw01.plus.net (84.92.6.40)  166.801 ms  13.970 ms  206.566 ms
4  te2-2.pte-gw1.plus.net (212.159.0.186)  11.516 ms  15.102 ms  12.913 ms
5  po4.pte-gw2.plus.net (212.159.1.188)  10.288 ms  10.537 ms  11.379 ms
6  po5.ptn-gw02.plus.net (212.159.1.142)  10.999 ms  11.530 ms  10.797 ms
7  * * *
8  84.53.179.242 (84.53.179.242)  150.041 ms  14.115 ms  223.486 ms
9  84.53.134.198 (84.53.134.198)  11.172 ms  11.722 ms  12.403 ms
Any ideas?

[#2]

Based on the response, this would normally suggest a local problem such as firewall or security software.
Your computer and internet is clearly online, but your computer doesn't even appear to be trying to route via the broadband connection.
We should normally expect at least one hop to Google (your router) before routing errors, possibly two (our gateway) if there is a routing issue our side (though this can be an indication of your IP being used on two connections, not a concern here though).
Can you provide the output of your route table from the machine?