Had a little time to have a play, adding a network share on the server kicked netbios in to play and can now be found on the network! However RDP access still isn't working and I'm getting an error about privileges when trying to connect using software to manage the VMs which appears to need some wanky workaround to get access when not on a domain. I'm tempted just to use another VM host as it's taking longer to set this up than setting up and installing several hosts on Xen

you wont ping a server by name unless there is some way of resolving it, hence asking about dns. alternative is hosts files. all os's do this roughly the same way, so google hosts files mac/windows/suse etc.

I've just put a dns server on my qnap for roughly a similar reason, although BTs awful response to DNS requests also had sommat to do with it.

It's hyper V so is basically running windows, so net bios should be fine for resolution, I just assume one of the services hadn't started to make it work until I added a share.. Fixed now anyway.. If I get time at the weekend I'll see if I can get the rest working or just be lazy and install Xen which is far less work!


Sent from my iPad using Tapatalk

depends on how you've built it though. out of the box dns is its first resort, it'll drop back to netbios if it can't use dns.

Previously I had it running exactly the same setup on another machine and all worked as expected, , I think something just went screwy somewhere :-)

turned off the windows firewalls?

Just put up a DNS server, doesn't take long and will sort out all your problems.

We're in the process of ditching as many XEN hosts as we can and moving them to Hyper-V. We've had the bug on a few boxes with snapshots eating up loads of space on our storage and having a painful time getting the lost space back.