When you suspect a network communication problem always work your way up from the hardware. Your troubleshooting technique should demonstrate that the hardware is working and then that TCP/IP is correctly configured. Since there is no DNS server netbios is being used for name resolution unless you have an LMHosts file configured. Command line tools like nslookup, nbtstat, arp, ping and the ipconfig command can demonstrate that the hardware is working and that TCP/IP is configured correctly. Here is a Microsoft guide for troubleshooting a simple network.
http://support.microsoft.com/kb/308007/Also look at any firewalls included with antivirus software. Most permit you to configure a trusted local network. You can temporarily disable your firewall as a troubleshooting technique.
Then look at Windows configuration. Once you have demonstrated that all devices are communicating at the TCP/IP level then check that file and printer sharing is enabled and that all devices are in the same workgroup. You haven't mentioned what OS you are working with. I am assuming XP. If Vista then there are additional steps.