[Webinar] Streamline your web hosting managementRegister Today

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

VM server does not always appear in AD.

On occasion one of our VM servers is not always listed in AD when I do a Network search.
It is functioning properly.  It's a 2008 R2

How do I trouble shoot this?
0
J.R. Sitman
Asked:
J.R. Sitman
  • 7
  • 2
  • 2
  • +1
1 Solution
 
Raj-GTSystems EngineerCommented:
It is impossible for an object to drop in and out of AD like this. How exactly are you querying the AD?
0
 
J.R. SitmanAuthor Commented:
I can tell you that it is possible.  From a server, I simply click on the network icon.  All computers and server display, except this one.
0
 
MaheshArchitectCommented:
Is this server and VM host subnet id different from DC and is it separated by VLAN ID ?

Does there other virtual servers on VM host get discovered or none of them ?

If other servers are discovered on VM host then problem exists with this server only

Ensure that network discovery is enabled on this server, and also check if workstation and Tcp IP helper service is running in automatic mode

Mahesh
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Cliff GaliherCommented:
The "network" icon is *not* necessarily Active Directory. It shows machines that are visible to the network discovery service. That can be blocked by firewall software, DNS changes, and a variety of other things.

The short version is that the whole network browser component of Windows is there for legacy applications (and users) to use, but does rely on older technologies that are being phased out. If you want reliable access to a resource such as a printer or a file-share, you would publish that in Active Directory. Then you don't need to browse to a machine first. But as a previous poster commented, the machine doesn't (and isn't) dropping in and out of Active Directory now. It is only dropping out of the network browser, which is unrelated.
0
 
J.R. SitmanAuthor Commented:
That is very helpful.  Do you have a link for "publishing in AD"?
0
 
J.R. SitmanAuthor Commented:
@Mahesh  I will check these later today.
0
 
J.R. SitmanAuthor Commented:
Network discovery is on and both services are running.  Also I read the article about publishing and it states computers and servers are automatically published.
0
 
MaheshArchitectCommented:
Just try to disable antivirus software on server and check from client computer \ DC if it is discoverable ?
May be antivirus blocks the broadcast

Mahesh
0
 
Raj-GTSystems EngineerCommented:
Also if you haven't already, enable netbios over tcp on the vm nic properties.
0
 
J.R. SitmanAuthor Commented:
I enabled the netbios over tcp.  Still testing
0
 
J.R. SitmanAuthor Commented:
It seems that with netbios over tcp on, the problem is solved.

Thanks
0
 
J.R. SitmanAuthor Commented:
Thanks
0

Featured Post

Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

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