National Instruments mDNS Responder Service

[wantacobra]

Justin

I'm not sure what to do here.  It appears that once I log in, I can manually start the mDNS service.  Is there a difference between an autostart and manual start? 

I have run the utility and disabled one of the name spaces.  I then can manually start the mDNS Responder service.  Does the disable option set a flag so the name space is disabled for the next reboot?  Does the test require a reboot after the disable?

On reboot, the mDNS service starts but does not transition to running state.  If I am admin on the machine, I can manually start this service after I log in.  I can also manually start the Device Loader service.  The question is why the mDNS service does not start automatically. 

I have noticed that Agilent IO Library mDNS starts successfully before the NI service.  Will this cause a problem/conflict?

Can we set a flag to dump a more detailed log of the mDNS service startup?

Mike

[Karvin]

Hi Mike,

I am facing a similar issue. The mDNS responder service wont start. I check other solutions mentioned in this thread and none worked. I tried disabling the name spaces and nothing worked either. Howeevr, when I rebooted and after the disable, I lost internet connectivity. But connectivity to local company network remained.

Which namespace did you disable before it worked?

Thanks,

Karthik

[wantacobra]

Karvin

I think I need to clarify my previous reply.  I have not had success yet.  As admin, I can manually start the mDNS Responder service.  This service starts, but it occurred to me this weekend that I need to check the event log to see if it successfully transitions to the "running" state.

My basic problem is the NI Device Loader Service.  This one does not start because it relies on the mDNS service to start successfully.  The more I thought about the problem this weekend, I need to understand why, as admin, I can manually start the NI Device Loader Service and see the USB and PXI devices behind the MXI Express card.

Thinking more about the troubleshooting for the mDNS issue:  

I still have a question if the "disable" sticks following a reboot.

1.  Without disabling any name spaces, manually start mDNS, note the time and then check the event log to see if the service transitions to "running" state.

2.  If the service does not indicate "running", then stop the service, disable the first namespace and attempt to start it again.  Check event log for "running" state.

3.  Repeat above for all name spaces.

Justin, do you agree with this test plan?  Any comments or suggestions?

Mike

[wantacobra]

More info:

Logged in as admin.  I stopped the mDNS service.  Was advised that NI Device Locator service would also be stopped.  Click OK.  

Manually start mDNS service.  Manually start NI Device Locator service.

Check event log and confirmed that mDNS and NI Device Locator services both are in running state.

These two services are started as "Local System" automatically on boot.  Is this any different than manually starting as admin?

I don't think the name spaces are causing this problem.  No name spaces were disabled and mDNS started and transitioned to running state.

Mike

[Karvin]

Mike,

Uninstalling all NI apps +

Renaming old NI folders in C:\Program Data(Win 7) +

Renaming old NI folder in C:\Program Files +

Removing all references to DAQ device in registry (you may have to use PsExec to run regedit in system account to delete keys) +

Then installing NI DAQ 9.2.2. +

Installing System Configuration 5.0 in a admin account

...worked for me.

NI Device loader started automatically on reboot too.

I am using the NI DAQ 6009 modules in my application.

Thanks,

Karthik

[wantacobra]

I have done a little more research and testing on this problem.  I have found evidence that the mDNS service DOES start automatically on boot...it just takes a long time.  I have not been able to locate in the log files when a service is started, but from the point in time when NI Device Loader tries to start, mDNS transitions to running state 2 minutes and 4 seconds later.

If I start and start mDNS after boot and login, the service starts quickly.

So, my problem is determining what is taking the time to start mDNS follow a boot.  The order services are started? 

Mike

[Justin_E]

Mike,

Let's see if I can answer some of the questions you've asked:

Is there a difference between an autostart and manual start?
Automatic services start at system logon, while manual services start as requested. Other than that, I'm not aware of any differences.

Does the disable option set a flag so the name space is disabled for the next reboot?  Does the test require a reboot after the disable?
No, I believe it just requires the application (mDNSResponder) to be re-launched. The namespace is disabled immediately after the command. Applications launched after the disable will see the changes.

I have noticed that Agilent IO Library mDNS starts successfully before the NI service.  Will this cause a problem/conflict?
No, it shouldn't. You can try disabling Agilent mDNS to see if anything changes.

Can we set a flag to dump a more detailed log of the mDNS service startup?
No, not with the released version of mDNS Responder.

I still have a question if the "disable" sticks following a reboot.
I believe the disable sticks following a reboot. You can check with the tool... run 'nimdnsNSPTool.exe -list' after a reboot and check the fActive value.

These two services are started as "Local System" automatically on boot.  Is this any different than manually starting as admin?
There are differences between starting something as "Local System" and starting as admin. Read this article for more details: http://msdn.microsoft.com/en-us/library/windows/desktop/ms685981%28v=vs.85%29.aspx
Things should still work though even if you aren't admin.

So, my problem is determining what is taking the time to start mDNS follow a boot.  The order services are started?
As long as the dependency services start before mDNS, it should start fine. NI System Web Server is the only dependency of mDNS

Let's get some clarification on what you're seeing:

1) What happens when the service is set to automatically start and you login under your local account?

2) What happens when the service is set to automatically start and you login under an administrative account?

3) What happens when you start the service manually under your local account?

4) What happens when you start the service manually under your administrative account?

[wantacobra]

Justin

In answer to what I am seeing:

1.  Autostart and login as a normal user:  mDNS service starts during boot process.  Windows detects the service hangs (nimdnsResponder.exe).  Ni Device Loader service attempts to start but exits since mDNS service is not in running state.  I have noted that about 2 minutes after Device Loader tries to start, mDNS enters the running state.  At this point Windows has started and I can login.  I check services and see that mDNS has started and Device Loader has not.  As a normal user, I can't manually start Device Loader.

2.  Autostart and login as a normal user:  Same as above for the Windows boot process.  I login in as admin and I check services and see that mDNS has started and Device Loader has not.  As a admin, I can manually start Device Loader and MAX finds all instruments. 

3.  Start service manually as a normal user:  After the boot process and logged in as a normal user, I can't manually start Device Loader.

4.  Start service manually as admin:  After the boot process and logged in as admin, I can manually start Device Loader and MAX finds all instruments. 

Notes:

1.     On boot, mDNS service successfully starts, but takes in excess of 2 minutes to transition to running state.  During the time mDNS is starting, Device Loader service attempts to start, but fails because mDNS is not “running”.  I have a Windows event that indicates the mDNS service is hung.  Two minutes later, I have Windows event that indicates mDNS service has transitioned to running.  This is the point that I can login.  Normal or admin does not make a difference other than being able to manually start Device Loader.

2.    On a previous post, it was suggested that I try to investigate the Name Space discovery process.  I can only test this theory by disabling a name space and then rebooting (assuming the disable sticks through the reboot).  I can manually stop, disable a name space and then start mDNS.  I have no method to determine if the disable name space fixed the problem, since the mDNS service successfully starts quickly after I log in whether I disable a name space or not. 

Question:  Does mDNS service code write to any log file?

Mike

[wantacobra]

Problem Solved!

Installed a beta version of mDNSResponder (214.3.1.32771, dated 8-10-11)

mDNSservice now starts automatically and transitions to running state.

NI Device Loader service automatically starts and transitions to running state.

MAX can display and command instruments located in PXI chassis.

Mike 

[wantacobra]

I have a problem with nimdnsResponder service bogging down my dual Xenon Intel board (8 processor cores).  Task manager shows this service is consuming greater than 50% of the CPU.  I have installed the same beta version (214.3.1.32771) of nimdnsResponder as in the previous post that fixed my initial development system.  An ideas?