Need to change workgroup name

[Riddle_Decipher]

@HarvMann here's an image from the user guide for your device, the same info can be found on Page. 39 of Network defaults: Click here to verify

If you wish to thank me for my efforts, you could click on "Accept as solution" on my first post as the solution should help others too.

[HarvMann]

@Riddle_Decipher,

I have performed the Restore Network Defaults and reconfigured wireless.

Then removed and re-added TCP/IP printer.

The Belarc report still shows MSHOME.

[Riddle_Decipher]

@HarvMann I checked with the R&D Team and here's what they had to say about this:

If the printer is connected to the main computer which is the Server, then the Server Admin needs to grant permissions to all the computers connected to the Server for those computers to have access to the printer to print

The Workgroup is on the computers and not on the printer. Since the printer is already connected to the main Server computer, then the other computers should be configured to be connected to the same Workgroup (in your case, the MSHOME) as the Server computer. Then the Server Admin needs to grant user rights permission and access to all the other computers so that they can use the printer.

It shouldn't matter what the group has been named, as long as all devices are connected to the same group, I suggest you add them accordingly and check if it works on MSHOME.

[HarvMann]

@Riddle_Decipher,

The printer is not connected to a server!  My client does not have a server.

All devices are connected via wireless network:

- 3 Windows 10 computers in WORKGROUP

- HP OfficeJet Pro 8610 printer in MSHOME

- HP OfficeJet Pro 7740 printer in WORKGROUP

[Riddle_Decipher]

@HarvMann

I Suggest you go through this link on how to set up the workgroup for your computer as this isn't related to the printer but the computer: Click here for details

(The above link is 3rd party and is not owned by HP, I've posted this only so that I may help you resolve this issue by going beyond my support boundaries, please ignore the ads and take only the free suggestions)

I hope that answers your query,

If you wish to thank me for my efforts, you could click on "Accept as solution" on my post as the solution should help others too.

[HarvMann]

@Riddle_Decipher,

The computers all have the correct workgroup name. So the info provided is irrelavent.

Since there is no simple solution, the only remaining solution is:

- install the printer using a USB connection to 1 computer and configure as a shared printer

- on the remaining 2 computers, provide access and install the shared printer

- then check workgroup names

Comments?

[Riddle_Decipher]

@HarvMann The printers don't have a workgroup, it's only created on the computer and that's what the link I shared explains,

That said, please proceed with the steps you've mentioned, and it should help resolve the issue.

Good luck.

[FTS2019]

@HarvMann F.Y.I.

@Riddle_Decipher, in response to your answer:

"The printers don't have a workgroup, it's only created on the computer and that's what the link I shared explains,

That said, please proceed with the steps you've mentioned, and it should help resolve the issue.

Good luck."

Unfortunately @HarvMann and I are going to need a lot more than luck!

I am not satisfied with this response from HP as I am sure many others are too! It is evident very little investigation has taken place to reproduce these issues.

The printers DO have a workgroup! I have provided evidence below to show this ! The link you have provided does not help anyone and whilst the link you have provided might be useful for people that do not know how to configure a workgroup on their Windows machines, it does not help the people that want to change the printers default SMB domain name (Workgroup name) from MSHOME to something else.

Below are my investigation notes:

In defence of other users who have also identified the issues with scanning software I support their statements. Scanning tools do not just fabricate the SMB domain information, it collected through interrogating the devices and not only that a packet capture shows it as clear as daylight.

Please see packet capture below, it quite clearly shows the Printer is responding back with the MSHOME SMB domain name:

the bit you will be interested in is:

    "Name: MSHOME<00> (Workstation/Redirector)"

No. Time Source Destination Protocol Length Info
1860 75.611507 192.168.178.29 192.168.178.20 NBNS 233 Name query response NBSTAT

Frame 1860: 233 bytes on wire (1864 bits), 233 bytes captured (1864 bits) on interface 0
Ethernet II, Src: HewlettP_XX:XX:XX (a0:2b:b8:XX:XX:XX), Dst: Apple_XX:XX:XX (8C:85:90:XX:XX:XX)
Internet Protocol Version 4, Src: 192.168.178.29, Dst: 192.168.178.20
User Datagram Protocol, Src Port: 137, Dst Port: 62091
NetBIOS Name Service
Transaction ID: 0xdcc7
Flags: 0x8400, Response, Opcode: Name query, Authoritative, Reply code: No error
1... .... .... .... = Response: Message is a response
.000 0... .... .... = Opcode: Name query (0)
.... .1.. .... .... = Authoritative: Server is an authority for domain
.... ..0. .... .... = Truncated: Message is not truncated
.... ...0 .... .... = Recursion desired: Don't do query recursively
.... .... 0... .... = Recursion available: Server can't do recursive queries
.... .... ...0 .... = Broadcast: Not a broadcast packet
.... .... .... 0000 = Reply code: No error (0)
Questions: 0
Answer RRs: 1
Authority RRs: 0
Additional RRs: 0
Answers
*<00><00><00><00><00><00><00><00><00><00><00><00><00><00><00>: type NBSTAT, class IN
Name: *<00><00><00><00><00><00><00><00><00><00><00><00><00><00><00>
Type: NBSTAT (33)
Class: IN (1)
Time to live: 0 seconds
Data length: 135
Number of names: 5
Name: HPA02BB8XXXXXX<00> (Workstation/Redirector)
Name flags: 0x0600, ONT: B-node, Name is active, Permanent node name
0... .... .... .... = Name type: Unique name
.00. .... .... .... = ONT: B-node (0)
...0 .... .... .... = Name is being deregistered: No
.... 0... .... .... = Name is in conflict: No
.... .1.. .... .... = Name is active: Yes
.... ..1. .... .... = Permanent node name: Yes
Name: MSHOME<00> (Workstation/Redirector)
Name flags: 0x8600, Name type, ONT: B-node, Name is active, Permanent node name
1... .... .... .... = Name type: Group name
.00. .... .... .... = ONT: B-node (0)
...0 .... .... .... = Name is being deregistered: No
.... 0... .... .... = Name is in conflict: No
.... .1.. .... .... = Name is active: Yes
.... ..1. .... .... = Permanent node name: Yes

The information above clearly shows the printer does respond with a SMB domain name (Workgroup name) so assume it must be hardcoded as I have been unable to find any options through the web configuration pages or directly on the Printer to change SMB domain name from the default MSHOME.  

Your suggestions to change all  other devices on the network to match their SMB domain name (Workgroup) on the printer is just ridiculous and is not an acceptable solution!

I look forward to a response or perhaps a firmware update with a fix for the missing configuration options.

[HarvMann]

@FTS2019

Superb investigation!

A 2nd client of mine experienced the same issue. They resolved the problem by dumping the HP printer and replaced it by an All-in-one Brother wireless printer. 👍