I'm not quite sure if this is the proper forum for this topic; if not, feel free to redirect me to one where I'm most likely to get answers.

My setup:
-Windows 7 laptop with one wired Ethernet port and a wireless NIC
-Embest SBC6045 development board (SAM9G45 based board)
-Ubuntu Linux 10.04 VM using VMWare Player

I am trying to get NFS working, with the Linux VM being the NFS server. Right now with my current attempts I can see with Wireshark that the SBC6045 is attempting to contact the NFS host, but the Windows host is not forwarding the packets onto the Linux VM. I think I have an issue with my network setup on the VM.

I have my wired Ethernet port setup for DHCP with an Alternate Configuration to use a static IP address of 192.168.200.1. I then have the static IP address on my SBC6045 setup as 192.168.200.128 and I have the SBC6045 directly plugged into my laptop with a crossover cable. With the stock Linux installation that came loaded on the SBC6045, I can ping the Windows host just fine. But no matter what Network Adapter configuration that I've tried (NAT or Bridge), I can't ping the Linux guest VM. Every time the ping makes it to the Windows host, it is never forwarded to the Linux guest VM.

The only reason that I think this may be the appropriate forum is because of this post: viewtopic.php/f,12/t,20157/. If I can get to the point in which the development board and the Linux VM guest can talk to each other, then I think I can use that post to get me the rest of the way to get the NFS working. Any pointers on VM setup to do what I want?

Thanks,
Bryan

OK, I have a little more information based upon my current settings. I think it's down to needing to tell the SBC6045 how to route to the Linux VM.

SBC6045 IP address is 192.168.200.128
Windows Host wired Ethernet port static IP address is 192.168.200.1
SBC6045 has 192.168.200.1 as its default gateway
Linux Guest VM has network adapter in NAT mode. The host side has an IP address of 192.168.217.1 and the Linux side has an IP address of 192.168.217.128.

With this setup, I can power on my SBC6045, stop the boot process at U-Boot, and I can ping with Windows host Ethernet port. However, the SBC6045 cannot ping even the Windows host side of the VM link (192.168.217.1). So it looks like I need to define the route between 192.168.200.128 and 192.168.217.1. At the moment I'm not sure if I need to do this on the SBC6045 or if I need to do this on my Windows host. Any ideas?

Thanks,
Bryan

I finally got my setup working. I did figure out it was an issue with the virtual network port mapping not being setup correctly. If you're having similar issues and are wondering how to fix it, look at this post: http://communities.vmware.com/thread/334626?tstart=0.

-Bryan