If your Netgear Wireless router has a mostly default configuration it should be providing both DNS and DHCP services to your LAN (wired and wireless). You can confirm this by right-clicking the Network Manager applet (near the clock and your username) on each machine and selecting "connection information". There should be a number of fields (Broadcast Address, Netmask, Default Route, Primary DNS, Secondary DNS) that are identical on both machines, while the IP address is only different for the least significant (right-most) byte of the dotted-decimal value. You will probably see something like 192.168.yyy.xxx. The .yyy field should be identical while the .xxx field must be different. If all of the above is true, you're ready to move on.
In all instances that follow, a string shown in double quotes (") represents a command that should be entered verbatim (with variable substitution) into a command line (terminal) window. Do not include the quotes in the command. Single quotes (') signify the anticipated response to a command.
On each machine, open a terminal window (Applications->Accessories->Terminal) and enter the following command: "ping -c 5 " where is the IP address of the other machine. The response should look like 'PING () 56(84) bytes of data.' followed by 5 lines that look something like '64 bytes from : icmp_seq=1 ttl=64 time=1.46 ms' and a couple of lines that show overall statistics.
If that works, then ping the other machine using the hostname, "ping -c 5 " where is the hostname of the other machine. If you don't know the hostname, type "hostname" in the terminal window. The string returned must be non-null and unique for each machine. If the response to this ping looks similar to the response when pinging by IP you're good to go. In my experience, most Linux distros assume that you're connecting to a managed DHCP environment, where the DHCP server tells the client what it's hostname is for that session. Unfortunately, that doesn't work with the typical residential gateway (like your Netgear), so I wouldn't be surprised if this ping fails due to an inability to resolve the hostname. Check out the Ubuntu wiki and forums to fix this.
If both ping commands work, you can use either Samba or NFS. If you can only ping via IP, NFS is by far the easiest approach. It's also the approach I'd recommend for the homogenous (2 linux machines) environment you describe.
On each machine enter "aptitude search nfs" in the terminal window. I expect you'll find that nfs-common is already installed on both machines. If it is, you're ready to add a line in /etc/fstab on the laptop to define where and how to mount the folder that will be shared by the desktop machine. The man pages for fstab, mount and nfs will provide the necessary info to enable you to configure this how you wish.
On the desktop you'll need to add the nfs-server package. This is actually a virtual package, so I recommend using the kernel-space service. In the terminal window, issue the command "sudo apt-get install nfs-kernel-server". The nfsd service won't actually start until there's a valid /etc/exports file, so read the man pages for exports(5) and exportfs(8) for information on the syntax for that file (make it work for you). The nfsd service will then automatically start upon the next reboot. You can start it manually without rebooting by issuing the terminal command "sudo service nfs-kernel-server start".