This is becoming a bit of a catchphrase for me when advising people on troublshooting problems like this, but here goes:
The important thing to remember about virtualisation when solving
problems like this is that nothing magical happens to your network,
good or bad, just because someone took a network diagram and said "by
the way, these hosts are now virtual".
I'm assuming you've set up the HyperV server properly, tested that can talk to the network happily in itself, and installed the guest in line with best practices, including installing the Integration Services.
So assuming all that, how would you troubleshoot this if the guest machine wasn't virtual at all?
- You'd check that the ip addresses and in particular the DNS setting are set correctly
- you'd check that the server could ping the workstation
- You'd check name resolution (e.g. can the client ping itself by name, is the client in DNS, can you run NSlookup and resolve server names...)
- You'd check the firewall on the client (and any that might be between the client and the server) are not filtering traffic
- You might try seeing if you can connect to a share on a server over SMB...