Luckily, I found this old forum post, which had the solution: Just go into your atalkd.conf file and uncomment the line that says eth0.
I'll walk you through it:
Open a terminal, then type:
sudo nano /etc/netatalk/atalkd.confThen delete the # sign in front of the word 'eth0'. Pretty simple!
Apparently, netatalk will just bind to whatever network interface is laying around, so it can sometimes get confused and bind to the crippled one used by VMWare Server. This fix just tells it to look for eth0 from now on instead of picking one willy-nilly.