0

I disabled the DNS/DHCP on my router and activated those services on a Windows 2008 server. Everything is working fine, but when I go to browse the network none of the machines can see any other machines, whereas they could when DNS/DHCP was handled by the router. All client settings are the same.

I'm unsure what actually drives this lookup for Windows. What is it and how can I enable it in Windows 2008 DNS or DHCP?

Improve this question
8
  • You must enable and configure WINS for Network Neighborhood/My Network Places/magic network thing to function. Which client are you using to open the (XP/Vista/7/2003/2008)?
    – brandeded
    Feb 8, 2013 at 18:06
  • Ok, I do not have that configured. Would my Actiontec router be running a similar role? Not sure what you mean about the client. I'm RDP onto the server.
    – Ryan Peters
    Feb 8, 2013 at 18:18
  • What about NetBIOS? How can I configure that with windows DNS?
    – Ryan Peters
    Feb 8, 2013 at 18:34
  • The client would be the access point for which you are hitting "network neighborhood". Actiontec, no. But it's quite possible that by using the Actiontec, your clients were allowed to elect a Browser Master (in replacement for a configured WINS server), but when they had their networking stack configured by DHCP, they no longer were electing the Browser Master. Let me look a bit further quickly and I'll post back.
    – brandeded
    Feb 8, 2013 at 18:36
  • Yes, client is a Win 8 machine. Should I use NetBIOS or wins? Either way, I can't figure out how to configure them. Thanks.
    – Ryan Peters
    Feb 8, 2013 at 18:38

2 Answers 2

Reset to default
0

Did you check network properties on each of the workstations and see if network discovery is active? I would think that since you changed your network around, the clients may be waiting for you to specify if the new network is a home/work/public network again.

Improve this answer
0

The answer was I just had to reboot the machines, and they showed up one-by-one in the network listing. Some still had the old DNS server and others simply needed a reboot. Johnny was technically correct, as was mbrownnyc. Thank you both.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .