[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 638
  • Last Modified:

SBS 2008 Virtualization DNS to host machine

Hello all,

 We have a virtualized SBS 2008 install. I virtualized the SBS box on top of a non-domain machine. As you can see in the network diagram (attached).

 However, the network cannot see SpartanV as it is a non-domain machine. For maintenance/updating purposes, I would like to be able to see it via the network, or at least by the SBS box.

 Is it possible for me to setup DNS to do this? How would I go about doing it?

Thanks for the help!
ee.jpg
0
LindsayCole
Asked:
LindsayCole
  • 5
  • 3
  • 2
  • +1
1 Solution
 
jorlando66Commented:
When you say "see" do you mean just communicate with by name resolution?  If so just create an A record in DNS pointing to the ip address of SpartanV.  You will not see it under the domain browse list as it is not a domain mmeber but you will be able to ping and navigate to it by name.
0
 
Darius GhassemCommented:
Here is the issue if you have the Hyper-V Host server pointing to the SBS 2008 as DNS then the Hyper-v server can be slow to boot up this is why you should keep your Hyper-v server off the domain.

Now if you are talking about My Network Places then you need to make sure the Computer Browser service is started and Netbios over TCP\IP is enabled on the TCP\IP settings
0
 
Rob WilliamsCommented:
Configuring Host/child permissions and management can be difficult. There is a great little tool that helps to configure this you might want to look at:. You definitely do not want to make the host a member of the domain.
http://code.msdn.microsoft.com/HVRemote
0
SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

 
LindsayColeAuthor Commented:
I wish to be able to RDP to the machine for any administration needs.

As you can see in the diagram, the Hyper V Machine is not on the domain. I tried to do this in the best way possible :)

Darius: Both of those settings are enabled.

Jorland: So I create an A Record in the SpartanSBS Forward Lookup Zone?

Sorry for the questions, it has been awhile since I have done server administration, and am trying to brush up and figure stuff out as I go again.
0
 
jorlando66Commented:
yes creating the a-record will simply map a name to an IP address which is my understanding of all you need to accomplish your goal of name resolution.
0
 
LindsayColeAuthor Commented:
I have added the A Record in spartan.local, which is under Forward Lookup Zones in DNS- and it did not allow me to see the host.

For the purpose of this, I want to be able to RDP the machine. Any suggestions?
0
 
Rob WilliamsCommented:
Adding the host record will automatically append the domain name and the machine is not a member of the domain.
A crude option is to use the LMHosts file:
http://msmvps.com/blogs/robwill/archive/2008/05/10/lmhosts-and-hosts-files.aspx
You don't need the domain entry, just the computer name.

However, communication between the DC and Hyper-V host is a nuisance to set up with permissions, firewall and such. The tool I suggested earlier is specifically for that.
0
 
LindsayColeAuthor Commented:
Hey RobWill, sorry I didn't mean to ignore your previous comment.

 I have read through the documentation for it, and I just don't see how it is going to allow domain PC's to view non domain. Maybe I am missing something? This doesn't seem to be a permissions problem, and is a configuration problem?

Thanks!
0
 
Rob WilliamsCommented:
I haven't used the updated tool, which offers more, and I doubt it will help that, but there are many issues with services not working, ports being blocked, and unable to access resources or authenticate due to permission issue. The tool allows easily configuring these to allow most services to work almost as if domain joined.
0
 
LindsayColeAuthor Commented:
Just want to follow up on this, none of these solutions helped unfortunately. I believe it to be a DNS issue still- but have no idea where to go from here.
0
 
LindsayColeAuthor Commented:
Helped with troubleshooting.
0

Featured Post

2018 Annual Membership Survey

Here at Experts Exchange, we strive to give members the best experience. Help us improve the site by taking this survey today! (Bonus: Be entered to win a great tech prize for participating!)

  • 5
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now