NetBIOS names over VPN

I have a Windows Server 2008 R2 box hosting a VPN to grant remote access to a home network.
The network does not and will not have a domain. (I need FUS on XP machines)

The VPN works fine, except that I cannot access any other machines by name over the VPN.

I can access the VPN server by name, and I can access the other machines by IP address, but whenever I ping any other machine name, it waits ~30 seconds and says it couldn't find the host.

EDIT: If possible, I'd prefer a solution that doesn't involve reconfiguring the client machines, and that will allow the other machines to communicate with each-other even if the server goes down.

From serverfault SLaks

• NetBIOS is a non-routeable protocol. You will need to have a WINS server setup at the VPN endpoint, and configure your remote clients to use that WINS server.

  Are people really still using NetBIOS ??? You should REALLY transition to a DNS based name resolution setup.

  SLaks : Is there any solution that doesn't involve reconfiguring the other client machines?

  Zypher : depending on your server you might be able to pass WINS configuration. But really you should use DNS, pass internal DNS servers and use split dns.

  SLaks : Can Windows Server's DNS server automatically resolve other machine names without manually adding them or reconfiguring the other machines?

  techie007 : Static DNS entries generally need to be manually added. If the machines are getting IPs via DHCP you can use the Windows DHCP server and give it credentials to modify the DNS as comptuers come and go from the DHCP pool.

  SLaks : But then the network won't work if the server goes down. (I don't want to be forced to maintain the server 24/7)

  techie007 : If the server goes down, then I guess you aren't going to be VPNing in - problem vanquished. :) If it's a home network, then I'm guessing it's only a few devices -- hard set the IP addresses and then either use them, or put them in your VPN client's HOSTS file if you REALLY need to contact them by name. :)
  From Zypher

• I solved this by setting up the server as a WINS server and setting its IP in the (Linksys) router DHCP's WINS field.

  After renewing every machine's IP address, it works fine, without (I hope) making the local network dependent on my server, and without requiring any manual intervention after renewing the IP addresses.

  techie007 : How is depending on a WINS server any better than depending on a DNS server? Oh well, glad you got it working to your satisfaction. :)

  SLaks : @techie: I hope that this setup isn't actually _depending_ on the WINS server. I tried changing the WINS server in DHCP to a non-existent address and renewing a client's IP, and the client still worked fine and could ping other machines. If there actually is a dependency, please let me know.

  techie007 : Are you still talking about _VPN_ clients?

  SLaks : @techie: No. Obviously, the VPN clients won't work at all if the server is down, but (I hope and believe) the other machines on the local network will.
  From SLaks