By the way, I found a location to download the Windows 64 bit installer package for Bonjour. I found an older version of Bonjour but it didn't fix the issue. The following post by 007me has a more current version of the separate installer: Re: WIndows 7 64-bit bonjour service fail to start. Tried solutions, never work. Once I installed the 64 bit version, all was copasetic.
I'm not a programmer or developer but the separate iterations of background processes is sometimes intentional in order to have different apps/processes run in separate threads or memory (most common example is Chrome ... keeps windows/sites running in the background) ... others like Service Hosts are network related, etc. Since some are crucial to system/network operations, they auto-start and are driven by the OS so can't be "ended" unless via safe mode or manually disabled/uninstalled.
For a time, I couldn't get Bonjour Print Services to run in my new ASUS Windows 10 PC. Guys at the Microsoft store told me to install the latest iTunes for Windows, but that didn't do anything. I could see the mDNSResponder.exe in the Programs File/Bonjour directory, and a mdnsNSP.dll and dns_sd.jar, but no Bonjour Printer Wizard.
So I went to Apple's Bonjour Support page and downloaded the latest Bonjour (v 2.0.2.0, file created 5/18/2010). I chose Run in the download dialog. After Running the install program, I found a new directory, Bonjour Print Services. Inside that directory is the PrinterWizard.exe. I double clicked that and the Printer Wizard did its thing, finding my ancient HP Hewlett-Packard Laser Jet 1012 printer. The Wizard tried to find a print driver, but none of the drivers came close. I finished up the Wizard as best I could. I then went to Windows' Settings/Devices/Printers and found a new entry for "Hewlett-Packard hp LaserJet 1012." I clicked on its properties and allowed Microsoft to find a driver, choosing the LaserJet 1015. Eventually Bonjour got the message and I was able to print on the HP LaserJet 1012 connected to my AirPort Express's usb port. When you look at the Properties of the printer installed with the Bonjour it should show you your Apple AirPort's mac (media access protocol, not "macintosh') address.
Many thanks, that was exactly what I was looking for. Interestingly, the task manager showed that Bonjour was already active, but I restarted it anyway for good measure and I haven't had any error messages since.
Incidentally, would you happen to know why some of the "background processes" seem to be running several times (as per the task manager)? Moreover, when I tried to "end task" for some of the redundant processes, it didn't seem to have any effect...
How do I make it so my windows machine can resolve hostname.local addresses? I know how to edit C:\Windows\System32\drivers\etc\hosts but surely there's got to be some automatic way to make Windows just find these machines?
Windows 10 handles both hostname and hostname.local identically: it simultaneously tries LLMNR for the bare hostname, NetBIOS for the bare hostname, and (optionally) mDNS for hostname.local. This mDNS support is not restricted to 'Modern' apps anymore.
The latest version (v3.x) is not available as an independent download, but is installed as part of iTunes (and a few other applications). It is possible to use an archive manager (like 7-Zip or WinRAR) to extract Bonjour64.msi from the iTunes installer.
As @Kevin Keane points out here (and in the comments section above), Windows 10 now clobbers mDNS port 5353 with a service that only works for modern Windows apps. So to let Bonjour back onto the port, the windows mDNS service must be quashed via the registry edit described in the link above.
Caveat, I already had both iTunes and Bonjour Print Services installed. Simply uninstalling Bonjour Print Services and reinstalling didn't work -- I had to go into add-remove programs, uninstall both Bonjour and Bonjour Print Services, then reinstall Bonjour Print Services, before pinging .local addresses started working again (virtualbox host-only linux guest with avahi-daemon running). I think this is because my "Bonjour Service" service was tied to Bonjour, not Bonjour Print Services, and it wasn't re-registering itself.
I was shocked to hear that this can cause conflicts with the Apple bonjour network as it also uses .local and was asked to change our local domain from .local to something else like .private. I have not had any issues to date but its interesting that the Xirrus engineer disabled bonjour on all our wireless arrays recently.
from the looks of the process - which seems to be ruled out if you have Exchange deployed - and the possible affect on folder redirection it looks at first glance as if it would be a lot easier to just not use any Apple products.
This has worked fine consistently across many Windows 10 home, and pro (64 bit only) systems that I have tested on. Recently however my primary Windows 10 development machine died (may it rest in pieces). This was always my only dedicated windows machine for testing so I converted a Linux box to Windows 10 Home x86_64. As I previously had tested on Windows 10 Home I saw no potential for issues.
This entire project relies on this one small piece of code that now suddenly is failing on one system. This same system BTW was completely rebuilt twice with fresh software downloads of Bonjour Print services for Windows , and I have tested the Bonjour SDK for Windows as well.
Normally I would launch this from a VBS script that launches a BAT file , this is to suppress the window. It does not matter how I run it , I have even tried running it from Task manager and it simply fails after several minutes.
You can also try a PUT /bonjour/interface?name=Local+Area+Connection to force it to use that adapter (although it should be anyway), or a DELETE /bonjour/interface to allow to use all available interfaces (pointtopoint, loopback and !up flags are filtered out).
Not sure if this is helpful, I ran into an issue similar to what is described on my end while setting up a server on windows (Windows 7 Home). After two hours of scouring the forums (very informative by the way, thanks!) and trying everything listed from unchecking/checking the bonjour setting to even reinstalling the server fresh with the updated package yesterday, nothing worked
What drove me even crazier was that I could access the server via its local IP (192.168.1.20:8089) and could see that it was working and could stream via the browser no problem, but I could not get it to broadcast via bonjour. However, knowing that the server worked, and having confirmed that bonjour was working on the windows machine, I was left with only the router.
Yes, it can. Bonjour is an apple service, but it is used to LAN services like multiplayer for Starcraft. Some other services outside of iTunes and SC1 uses Bonjour as well. Adobe is also known to use bonjour.
Useful advice thanks. It also works with the new Airport Extreme. It is important to remember to uninstall the printer from any previous attempts, before following your instructions, otherwise Bonjour seems to default to the origi.
The fix was to select generic postscript drivers in XP (which was the first driver selected during installation, golly, apple even try and make things easier on windows for us, good old Steve Jobs). After this, printing worked with no problems at all.
ok, I must be moron, because no matter what I read and try nothing works, I do not get a test page to print. I tried going from my xp desktop to shared printers or just regulat, (I hate windows). can anyone offer a suggestions?
I was having issues printing from XP through my new Time Capsule (MBP working fine). Based on the post from wensley I changed my port from the Time-Capsure.local to IP_10.0.1.1 and all works fine now!!
I am glad it worked out for you Joe Soricelli. I recently had to reinstall Windows because of a nasty virus. I am glad I wrote in this forum, because I had forgotten how to configure the port. I googled my own name with some additional keywords and found this page again. Btw, in the old post I wrote the port name as 10.0.0.1, it should be 10.0.1.1 as Joe wrote.
Thanks for sharing your thoughts and excellent and It also works with the new Airport Extreme. It is important to remember to uninstall the printer from any previous attempts, before following your instructions, otherwise Bonjour seems to default to the original..
After trying several other solutions, this is the one that worked. Need to make sure you have the correct version of bonjour and it installs correctly. after that, this is pretty flawless. THANK YOU!!
7fc3f7cf58