How do I connect my HP LaserJet 1020 printer to Windows 10?

anonymous

Guest

October 14, 2019 at 2:54 pm #1981242

Question from ignorance, I am not great with printer compatibility. My starting point is that all three Operating Systems are 1903 and so will not have SMB1 enabled unless that was done purposefully. The printer is vintage where SMB1 was standard, and the Plug-N-Play drivers would reflect that.

Is it possible, there’s that word, the two systems that work properly have updated drivers that are different from the faulty system?

If this is true, SMB1 could remain disabled, maintaining the more recent standard for security. But this is beyond my knowledge to say for certain.

Paul T

AskWoody MVP

October 15, 2019 at 8:52 am #1981865

A network print server won’t cost less than $40 so it’s probably best to persevere with your computers.

Have you tried removing / resetting the network on laptop S, then re-installing / setting it up from scratch?

cheers, Paul

Stephen Yeo

Guest

October 15, 2019 at 9:42 am #1981906

By removing the network, do you mean just the wifi connection or is there more that needs to be removed?

• Paul T

  AskWoody MVP

  October 16, 2019 at 3:07 am #1982744

• • Stephen Yeo

    AskWoody Plus

    October 16, 2019 at 3:56 am #1982765

    Thanks, that was a useful reference. Some of it wasn’t relevant, since I can reach the internet from all 3 PCs.

    But I decided to see if I could reach the Desktop computer via its IP address and the network troubleshooter.

    I obtained the Desktop’s IP address by running IPCONFIG on the Desktop. Then I tried pinging that address from the problem Laptop, and I did get a reply. So the Desktop is reachable from the problem Laptop via ping.

    I then tried running the network troubleshooter, as the article suggested. It didn’t find any problems, but offered to help with other problems, including “I’m trying to reach a specific website or folder on a network”. I tried that option, but entered the IP address (I guess I could have tried the network name of the Desktop PC, but I wasn’t sure what that would be). Not surprisingly, given that ping worked, I got the message

    “Website (numeric IP address of Desktop PC) is online but isn’t responding to connection attempts”

    The detailed explanation was

    “The remote computer isn’t responding to connections on port 80, possibly due to firewall or security policy settings, or because it might be temporarily unavailable. Windows couldn’t find any problems with the firewall on your computer”

    So one possibility is that the firewall on the Desktop PC is allowing connection attempts from one of the laptops, but not the other. That is consistent with the fact that the Desktop PC is visible in Windows File Explorer from one laptop but not the other. I suppose there might be a firewall in the router that is doing this, but the error message from the troubleshooter suggests that it was able to reach the Desktop PC via the router, but the Desktop refused the connection.

    I guess this is progress, but not yet a solution.

  • Paul T

    AskWoody MVP

    October 16, 2019 at 11:17 am #1983159

    Port 80 is a red herring – internet only.
    You need to remove all traces of the network from that laptop and then reinstall.

    cheers, Paul

Just Lurking

AskWoody Plus

October 15, 2019 at 10:49 am #1982043

@ Stephen Yeo

Present problem
Remote printing works on Laptop M but not on Laptop S (even though it worked on both Laptops until a week or two ago)

At the beginning of any trouble shooting, I usually ask *What happened just before you noticed the problem?* The time frame of *just before* varies from immediately to possible a day, or a few days, or even longer–but usually it’s fairly close to the problem beginning.

So, what changed or happened *a week or two ago*?

All 3 PCs running most recent version of Windows 10
Printing to the Laserjet used to work without any problem when Home Group was still part of Windows

After Home Group was removed, printer sharing still worked, but the shared printers needed to be set up again on the laptops whenever there was a significant update to Windows

I do not use Win10, so I’m in the dark here–so all three computers were successfully sharing the printer when you first set them up using Win10 *Home Group*? Microsoft (?) has now removed the option of using *Home Group*–what did Microsoft (?–or who or whatever changed that) change that *Home Group* setting to on each of the three computers–what’s in use now?

After *Home Group* was *removed*, all three computers continued to successfully share the printer, but you now had to do the following: “the shared printers needed to be set up again on the laptops whenever there was a significant update to Windows”.

*shared printers*–plural? Are there other printers involved? What had to be done to *set up again on the laptops*–what settings had to be reset?

And then, one or two weeks ago, something happened–and now laptop S can not connect to the Desktop computer–correct? Again, what happened one or two weeks ago?

I currently use Win7 and Win8.1. When setting those systems up, the advice I found recommended *not* using a *HomeGroup* network–instead use the *WorkGroup* network. The reason was that there were compatibility issues that created unexplained connection issues between computers that could not be easily resolved. I don’t know if that issue also has continued to effect the Win10 OS.

Apparently, the network type name needs to be the same on all shared computers–so the name, the capitalization, any spaces need to match–again the best recommendation was that one used *WORKGROUP*–capitalized, and all one word to avoid compatibility issues.

Now that *Home Group* has been removed, what is the network type that is being used, and is it the same and identical on all three computers?

• Stephen Yeo

  AskWoody Plus

  October 16, 2019 at 2:50 pm #1983302

  I’ve carried out every step in the article that you cited, except turning off the firewall and antivirus. These steps didn’t make any difference – still no sign of the Desktop PC and other Laptop from the problem Laptop.

  I guess I could try switching off the firewall and antivirus software – but on which PC? I seem to be able to ping the Desktop PC from the problem Laptop (at least by IP address). So it doesn’t seem as if the Laptop is blocking things – more that the Desktop responds to the ping but not to an attempt to establish a connection.

  But I would be the first to admit that I’m out of my depth here …

Just Lurking

AskWoody Plus

October 15, 2019 at 11:38 am #1982074

@ Stephen Yeo

Again, I don’t know what settings are available on Win10, but here’s the Win7 *Advanced sharing settings* that might be important to your situation:

*Network Discovery* needs to be turned on–check it for the laptop S computer.

Just Lurking

AskWoody Plus

October 17, 2019 at 6:43 pm #1983908

@ Stephen Yeo

I ran across this webpage while looking for information that might relate to your problem that you have posted:

How to Change Workgroup in Windows 10

In the comment section, there was a posting that suggested a technique that might help resolve your issue:

Comment #5 by Bandit233

Bandit233 wrote:

Brink, wanted to let you know your post is applicable to multiple Win 10 peer networking issues and should be linked to multiple threads in the forums. Here’s why: I’ve had multiple PC’s on my home network using peer networking, folder and file sharing, and printer sharing ever since Win 10 was released, but this month’s patch Tuesday release from MS broke my network connections on 2 of my PC’s. The computers all showed connected to my workgroup, but the file browser was unable to see the PCs, mapped drives and folders and shared printers were all dead. The ONLY thing that got my connections restored was your command prompt fix for joining a workgroup. Thanks for the fix, Cheers.

The method referred to here: *… your command prompt fix for joining a workgroup … * refers to OPTION TWO outlined on that webpage.

So, all three of your computers need to have a unique *Computer name*, but they all have to share the same *Workgroup* name:

If I understand Bandit233’s comment, even though his computers still shared the same *Workgroup* name, somehow the Win10 Update changed two of his computers so they no longer had access to his previously working network. By running the elevated command that’s outlined in *Option 2* on those two computers, and using the *same* Workgroup name as used previously, it re-set the network relationships so those two computers were successfully re-joined to a functioning status on the network.

Now, your problem may not have occurred after a Win10 Update–could have been some other glitch that occurred. But the problem sounds to be the same regardless of how it happened.

Worth a try to see if this resolves your problem.

Stephen Yeo

AskWoody Plus

October 22, 2019 at 7:34 am #1987649

You know, that was a very good suggestion. I was sure that it was going to work. But when I looked at the PCs, they were all connected to the workgroup “WORKGROUP”. I then tried adding the problem laptop to the group using the powershell command (option 3 in the reference you gave me) but that failed with the message that the laptop was already a member of the group.

I suppose I could try to create a new workgroup with a different name and then add all 3 PCs to the group, but that might affect the printing on the other laptop.

Anyway, thanks for a very thoughtful suggestion. Doesn’t seem to help though.

Just Lurking

AskWoody Plus

October 22, 2019 at 9:13 am #1987733

@ Stephen Yeo

… when I looked at the PCs, they were all connected to the workgroup “WORKGROUP”.

That’s exactly what Bandit233 said regarding his setup:

The computers all showed connected to my workgroup …

I then tried adding the problem laptop to the group using the powershell command (option 3 in the reference you gave me) …

But, (sigh) that is not what Bandit233 did to solve his problem with his wayward computers on his network. He states:

The ONLY thing that got my connections restored was your command prompt fix for joining a workgroup.

None of us know *exactly* what these various *command prompt* and Power Shell commands do–what flags, or switches are flipped on or off in the system. We do not know if the Power Shell command touches all the same things as the *command prompt* command.

Doesn’t seem to help though.

Yes, apparently *Option 3* does not work!

But until you actually do exactly what Bandit233 has reported worked (*Option 2*), I would have to say you do not know if that will also fix your problem.

I suppose I could try to create a new workgroup with a different name and then add all 3 PCs to the group, but that might affect the printing on the other laptop.

You certainly could try that–basically *starting over*. But just about anything you do has the potential of knocking out the current networking relationships that you may have to re-establish. But, I think accessing a shared printer only requires being able to *see* the computer on the network (i.e. the computer’s unique name), and the assigned name of the printer. If your current *working* laptop continues to be a part of the network after a name change, then, if needed, re-establishing the printer sharing should go without a problem.

But, I would still try *Option 2* first. It has no negative side effects that I can see, except it may not work!

PKCano

Manager

October 22, 2019 at 9:23 am #1987753

Have you downloaded from HP and installed the HP Laserjet software on Laptop S?

anonymous

Guest

October 23, 2019 at 4:45 am #1989049

Tried option 2, but that did not make the Desktop PC visible from the problem laptop. Oddly enough, the other laptop is visible from the problem laptop, but not the Desktop (or the shared printer)

anonymous

Guest

October 23, 2019 at 4:47 am #1989050

And in response to PKCano, I have been able to print from the problem Laptop in the past, but something has changed and neither the Desktop nor the shared printer is visible from the problem laptop – although the other laptop (from which I can print) is visible from the problem laptop.

So

the Desktop can see both Laptops

one Laptop can see the Desktop and the shared printer (and print)

the other (problem) Laptop can see the other Laptop, but not the Desktop or the shared printer.

all the PCs say they are part of WORKGROUP, and I’ve joined both the problem Laptop and the Desktop to WORKGROUP using the command line solutions suggested in another message.

At this point it “feels as if” the firewall on the Desktop is not allowing connections to the problem Laptop. but that is just a conjecture. I can ping the Desktop from the problem Laptop, but can’t see it in File Explorer.

Vincenzo

AskWoody Plus

October 23, 2019 at 1:23 pm #1989543

Have you checked that the security software or firewall is not the problem?

mledman

AskWoody Plus

October 23, 2019 at 7:26 pm #1989872

As a test, have you tried enabling SMB-1?

Win 10 home - 21H2
Attitude is a choice...Choose wisely

• PKCano

  Manager

  October 23, 2019 at 7:31 pm #1989874

• • mledman

    AskWoody Plus

    October 23, 2019 at 8:38 pm #1989935

    I Know 🙂

    I had a look at SMB-1 but there seem to be so many dire warnings about using it that I thought that would have to be a last resort.

    I’m wondering if Stephen has actually tried.

    Win 10 home - 21H2
    Attitude is a choice...Choose wisely

anonymous

Guest

October 23, 2019 at 9:56 pm #1989950

I do agree with you both that the test should be tried at least. The result may be instructive especially if it still fails.

What I wonder, if all three units are under Stephen’s administration, and he does not allow SMB-1, then how does the other laptop print?

It is hard to move forward without the test result communicated to the helpers.

Vincenzo

AskWoody Plus

October 23, 2019 at 7:53 pm #1989891

Have you checked that the security software or firewall is not the problem?

I should have added – by turning off the firewalls on all computers, rebooting, and trying.

• This reply was modified 3 years ago by Vincenzo.