DNS, WINS and DHCP
Again for share access via UNC (\\serverName\shareName), you could use WINS, but broadcasts should work just as well. Of course, make sure the local host firewalls allow access between systems. Either way, if you do want to install WINS, its very easy to do so on the server. Once you configure your DHCP scope you would assign options 44 and 46 to your clients (0x8 Hybrid, IP Address of WINS server). Guides and tutorials, visit ITGeared.com.
November 8th, 2011 4:59am

I think that you are confusing DNS domains and Windows domains. When you install DNS you must enter a domain name. All DNS names are heirachical (ie names separated by dots like machine.mydomain) and there must be a domain name for the other bits to link to. You can call your domain whatever you like but it must have a name. You can certainly set up DNS (and DHCP if you want) in a workgroup. Why not use your workgroup name as your DNS domain name? Nobody but you will ever see it if you are on a private LAN behind a router. Bill
Free Windows Admin Tool Kit Click here and download it now
November 8th, 2011 7:26am

Can a windows 2008 R2 member server that is in a workgroup (alone) not in a domain be a DNS, WINS and DHCP server. I want to use the server as a file and print server in a small office. The server would need to forward DNS requests to the DNS servers at Comcast. All office PC's need to be able to access and share files on this member server. Thanks Thank You, Scott
November 8th, 2011 8:20pm

yes, DNS, WINS and DHCP do not require Active Directory services. You can enable the roles in Server Manager. Quick video/tutorial on how to install the Windows Server 2008 DNS service: Install the Windows Server 2008 DNS Service http://itgeared.com/how-to-install-microsoft-windows-server Guides and tutorials, visit ITGeared.com.
Free Windows Admin Tool Kit Click here and download it now
November 8th, 2011 8:28pm

I tried and DNS wanted an uper level domain. What do I enter?Thank You, Scott
November 8th, 2011 8:32pm

Follow the tutorial that I posted. When you install DNS, there is nothing in the wizard that should prompt you for an "upper level domain". Can you be more specific about when you saw this prompt/error? Once you install the DNS service, the next step is to create zones on the server, if you want to provide name resolution internally for a domain name/hosts. If this is the case, do you have a registered DNS name that you may want to use? If this zone is for internal hosts name resolution, you can use a valid domain name but use a non-valid extension such as mycorp.LOCAL, or mycorp.INT, rather than using mycorp.com. Its up to you on how you want name resolution to function. If not, you do not have to create any zones. You can simply configure the forwarders as you asked and point it to your ISPs DNS servers. Guides and tutorials, visit ITGeared.com.
Free Windows Admin Tool Kit Click here and download it now
November 8th, 2011 8:37pm

Yes. Enable the File Server, DNS and DHCP roles. For WINS, enable it in Features, not Roles. If you are currently using DHCP from an ADSL device you will need to disable it. You cannot have two DHCP servers on the same segment. After you configure DNS you can set it to forward to an external DNS service. Bill
November 8th, 2011 8:39pm

I have no reason for DNS except internt access from all PC's. I don't need a zone internally. WINS should take care of my internal name resolution. If I need to use an internal domain I can use abc.corp but i prefer not too... I really only need to be able to map a network drive by name.Thank You, Scott
Free Windows Admin Tool Kit Click here and download it now
November 8th, 2011 8:41pm

If this is a single subnet, WINS is not really required either, unless you have a NetBIOS application that requires it. On a single subnet, NetBIOS name resolution will use Broadcasts if a WINS server is not available. With regard to DNS, if all you need is internet name resolution, I would simply configure the systems (via DHCP) to point directly to the ISP's DNS servers and not bother installing DNS on the local network. Guides and tutorials, visit ITGeared.com.
November 8th, 2011 8:47pm

I do need internal name resolution for share access. What will supply that? This is a single subnet with 5 PC's and two printers...Thank You, Scott
Free Windows Admin Tool Kit Click here and download it now
November 8th, 2011 8:50pm

Again for share access via UNC (\\serverName\shareName), you could use WINS, but broadcasts should work just as well. Of course, make sure the local host firewalls allow access between systems. Either way, if you do want to install WINS, its very easy to do so on the server. Once you configure your DHCP scope you would assign options 44 and 46 to your clients (0x8 Hybrid, IP Address of WINS server). Guides and tutorials, visit ITGeared.com.
November 8th, 2011 8:59pm

I aready have wins installed. It works fine. It's DNS that wont install without an uper level DNS domain.Thank You, Scott
Free Windows Admin Tool Kit Click here and download it now
November 8th, 2011 9:01pm

check out links below to install DNS: http://www.windowsreference.com/dns/how-to-setup-and-configure-dns-from-command-line-in-windows-server-2008-core/ http://technet.microsoft.com/en-us/library/cc725925.aspx if still can't install get a screen shot of the error and post it here. :) Good luck! Every second counts..make use of it.
November 8th, 2011 9:33pm

I think that you are confusing DNS domains and Windows domains. When you install DNS you must enter a domain name. All DNS names are heirachical (ie names separated by dots like machine.mydomain) and there must be a domain name for the other bits to link to. You can call your domain whatever you like but it must have a name. You can certainly set up DNS (and DHCP if you want) in a workgroup. Why not use your workgroup name as your DNS domain name? Nobody but you will ever see it if you are on a private LAN behind a router. Bill
Free Windows Admin Tool Kit Click here and download it now
November 8th, 2011 11:26pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics