Link-Layer Topology Mapper Terminates After A Few Minutes
I have a problem with the Computer Browser Services functions within my Windows Server 2012 environment. I have a small lab domain comprised of one server machine, called SERVER, running Windows Server 2012 R2, two (2) client computers, named NETBOOK and STUDIO, running windows 8/8.1, several iOS and BlackBerry mobile devices, and two Smart TVs.
Windows Server is used to run FileMaker, MediaMonkey, Windows Server Essentials 2012 R2's Digital Media Server, as well as typical services including File Server, Active Directory, DHCP, DNS, IIS, and an (incorrect) configuration of Remote Access, NAP, and Remote Desktop Services.
Symptoms The symptom I am experiencing is that from within SERVER, neither the client computers nor SERVER itself are enumerated up in File Explorer. I can, however, type "\\SERVER\" into the address bar and navigate to the client computers and the server itself.
Above is File Explorer from SERVER. Note that they can see each other, but SERVER is not enumerated.
From the client computers, NETBOOK and STUDIO, File Explorer does enumerate the client computers, but SERVER is not. Similarly you can type "SERVER" into the address bar and navigate to the SERVER and its shares.
Above is File Explorer from the client computers. Note that they can see each other, but SERVER is not enumerated.
Correlating Symptom
The symptoms coincide with the fact that the Link-layer Topology Discovery Mapper service will not remain active. I receive constant alerts advising that this service has stopped. I can go into the services.msc and start the service again but it only remains on for a few minutes before terminating itself for some unknown reason. But of course, I would also like to resolve glitch.
Please note, that even when I manually enable Link-layer Topology Discovery Mapper service and, all be it just for a few minutes it remains active, the exact symptoms persist and I am unable to enumerate the computers properly.
Possible Cause? I'm not sure what I may have done to cause this issue since four months the system ran well and this is a new glitch. The most recent change that I may have made, which could have affected this, was the installation of FileMaker Pro--which also installed Bonjour. I am aware that Bonjour does interact with other Network Devices to auto-configure and connect themselves.
I also may have tinkered with one or two firewalls rules from within Windows Server 2012 when I endeavored two make FileMaker and MediaMonkey servers accessible through firewall.
Please Help
I have searched Microsoft's blogs, TechNet, and the web, and have not found any solution for this problem. I hope you can provide some insight for me to resolve this.
I look forward to your response and I think you, in advance, for taking the time to read my message and for your consideration.
Hopefully you can point me in the right direction.
Much obliged,
David