Windows 10 (not) detecting network printers.

S

sajunky

Honorary Master
Joined
Nov 1, 2010
Messages
13,120
Reaction score
276
Location
JHB
Not exactly about Windows 10 alone, as problem is known since Windows XP, still not resolved.
Detailed process of Windows detecting IP printers on the LAN is described below in details, it is a real shame.

This time it was HP 2600n colour laser printer. I haven't got access to the router or printer admin page, nor a sufficient time to gather sufficient information for manual IP configuration, so when printer was not detected automatically, I gave up; I enabled printer sharing on the USB connection. It works on Windows workgroup, but jobs from Apple laptop where stuck on the spooler's queue (not printing at all). It is a GDI printer (not PCL/Postscript), but other GDI printer - Laserjet 1100 connected to the same PC was printing from the Apple without problems. I tried fiddling on the Apple laptop (knowing zero about OS X) and after few seconds HP 2600n was recognised under Apple bonjour services. Clicking on it, it installed drivers automatically.
Question is: Why Windows 10 is unable to do the same?
sajunky said:
Another installation - 32-bit version on the old tablet Fujitsu Stylistic ST5112, 2GB RAM).

Common problem on each installation: - it installs Microsoft Graphics Adapter. It can't work in native LCD resolution (Intel 945GM) on 1280x1024 external monitor. After an hour or so on the Internet it still doesn't pickup the right diver. Have to download chipset inf (just in case) and graphics driver manually.

This case problem: Installed Microsoft WiFi driver (Intel PRO 3945ABG) doesn't work. Will try Intel driver, but it is much older.

Trying now a challenging project. There is HP printer with JetDirect 610n series on the LAN. Till now I installed printer manually on Windows XP by setting up static IP on the printer and manually configuring TCP port, printer model, etc... Now, I thought that I could try automatic printer installation. JetDirect supports three different discovery methods and Windows at least two of them, it should work.

1. The first part is fine. Reseting Jetdirect to defaults, everything is right, printer properly auto configure from DHCP server.
2. Trying autodetecting printer... sorry.
3. Trying autotedecting by hinting, it is TCP/IP printer... sorry.
4. Trying to supply printer's host name, all right - progress, it creates TCP port, but still is unable to pickup printer name&driver. Interrupting, will be trying something else...
5. Enabling SNMP standard community password (never used it before, overheard it is unsecure). No detection a/a.
6. Repeating #4, it forces me to create another TCP port, it says the other one is in use. Stupid - I installed three different printer drivers for this printer (PostScript/PCL) in the past, all using the same port. OK, giving up, now on the printer selection dialog box I can't find Laserjet 4050 on the list of printers.
7. Trying Windows Update button - big mistake. Windows is unable just to download driver's headers, it downloads the entire printers package - nearly 200MB!!! Still no autodetection, but at least I can find my printer on the list. It deserves comment that Windows 10 is not ready for smartphones with metered Internet connection.
8. Everything fine till power cut comes. Windows after restoring power is unable to transfer jobs to the printer.
9. Reverting to the old-school static IP method.

There is a bug in Devices and Printers applet. It allows me second-button click on 'Properties', but nothing happens. I noticed new items on the address bar or below, I could use it to delete redundant TCP ports created in previous attempts.
Click to expand...
 
Flip, since upgrading to windows 10 I have been having no stop issues with printing, MS couldn't care less and HP seems to still be in a 2005 mindset :mad:
 
Update. Simultaneous USB/LAN connection is not supported on this printer, so on the next visit I unplugged USB cable. Windows 10 will still not autodetect, but supplying printer's host name allows to add driver. The last things to do was to change on the router DHCP lease time to 'infinite', which works similar to the static IP (reserving the same IP address for this device), to keep Windows happy on every boot.
 
sajunky said:
Update. Simultaneous USB/LAN connection is not supported on this printer, so on the next visit I unplugged USB cable. Windows 10 will still not autodetect, but supplying printer's host name allows to add driver. The last things to do was to change on the router DHCP lease time to 'infinite', which works similar to the static IP (reserving the same IP address for this device), to keep Windows happy on every boot.
Click to expand...


Why not setup IP reservation instead of messing with the DHCP?
 
Rickster said:
Why not setup IP reservation instead of messing with the DHCP?
Click to expand...
Good question. It was one mice click away on the router's page. Alternative way needed to pickup one DHCP-free address, then go to the printer, disable DHCP and enter IP address manually.
On second thought it could be even correct action, assuming that Microsoft will fix this bug before ADSL router get lightning strike again (last season was replaced 3 times). It is my faith in Microsoft - you know. ;)

They must be aware of the bug which was present here since XP, BTW. In the preview version I deleted number of unused TCP ports, it kept assigning a new port to the same printer, so I am sure they are working on the fix. <G>
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X