It sounds like your client PC is unable to resolve the name "forlenza.local" using DNS. You have a few easy options to check this using common commands.
C:\>nslookup forlenza.local.
C:\>ping forlenza.local
If you get an error like Ping request could not find host forlenza.local
then it's definitely a problem with DNS.
Solution 1: Change DNS settings on the client PC
Right now, the client PC is probably using either your router or your ISP as a DNS server. But since neither your router nor your ISP know anything about the server you have set up, they can't answer the DNS query. You need to change the properties on your network adapter to use a specific DNS server. In that field, put the IP address of your server. (Make sure the server has a static IP.)
Solution 2: Change the DNS settings on your router
This might be the easiest option if you plan to run your server 24/7. Just log into your router and change the DNS settings to use the IP address of your server. But if your server is shut off, then nobody will be able to access the internet.
Solution 3: Use your server for DHCP instead of your router
If you're truly dedicated to running a server in your home, this is the best option. Right now, all of your computers probably get their IP address from the router using DHCP. You can disable DHCP on the router and enable it on the server, so that the server gives out IP addresses and network information.
1Maybe it would work better if you moved the computer upstairs from the basement? :-) – ziesemer – 2011-12-31T21:32:14.497