I've encountered this once or twice in the past. If you statically assign the default gateway (router) as your DNS server, name resolution doesn't always work. So, even if you compare your laptop settings with your desktop, you might be puzzled. Because, when DHCP assigned your gateway (router) as the DNS server, there's no problem. I never figured that one out. This was a very rare occurrence, though.
If you still want to use Static assignments, and if you know your ISP's DNS server addresses, enter those under Preferred and Alternate DNS server instead. Of course, your router still needs to be the Default Gateway.
A long shot, but check the Subnet Mask. By any chance, is it:
255.255.255.252 ?
If so, guess what? There are no more addresses available in your subnetwork.
That last 252 means that a maximum of two devices, or hosts are allowed. That would be the router, then either your laptop or desktop. (Under certain circumstances, ping might still work, if I'm not mistaken.)
It looks like you didn't set up this router yourself. If your subnet was set up this way, it may have been done to limit the number of users that could connect as a security measure. You will need to reconfigure your router under its DHCP settings. If you change that last octet to 248, it will allow up to six hosts to connect. Also, check the start and ending addresses available for the DHCP server to assign. Make sure there are enough addresses in that range for the DHCP server to assign.
This is a very short list of some common subnet mask values:
255.255.255.0 :: up to 254 hosts
255.255.255.128 :: up to 126 hosts
255.255.255.192 :: up to 62 hosts
255.255.255.224 :: up to 30 hosts
255.255.255.240 :: up to 14 hosts
255.255.255.248 :: up to 6 hosts
255.255.255.252 :: up to 2 hosts
Speaking of security, you are using WPA or WPA2 with a strong password, right?