Very frustrated. After spending over 4 hours on the phone with HP support, then the remained of my day surfing the internet trying to figure out why my laptop will not "see" the network printer at my home I come here to see if any of you tech experts can help with my problem. First let me identify my computers. Computer 1: Main desk top computer running Windows 7 Ultimate 64-bit OS, Name: Desktop1 connect to Workgroup: WORKGROUP. Computer 2: (problem child) HP Pavilion dv7 running Windows 7 Home Premium 64-bit OS, Name: dv7bigpc Computer 3: (newest addition to the group, Angel, and does everything right - right out of the box!) HP Pavilion dm4 running Windows 7 Home Premium 64-bit OS, Name: dm4littlepc Issue: Computer 2 will not print from network printer. Doesn't even recognize it. But access the internet flawlessly from the network router. Computers 1 & 3 both see and can access files from Computer 2. However, Computer 2 can not access files from 1 & 3. In the HomeGroup window on Computer 1 & 3 only Computers 1 & 3 show up, but down in Network I can see all computers, even Computer 2. On Computer 2 on the Homegroup screen I can see computers 1 & 3. And in the Network list I can also see all the computers listed 1-3. When I select and click on Network Computer 1 or 3 from computer 2 I get a message "\\(computer name) is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The specified network provider name is invalid." All three are connect to the same workgroup name. Help! HP's solution was to buy a wireless printer from them for a discounted rate of $125 to $250 or spend an additional $59 for tech support when I already have the extended tech support purchased. I can't figure out if this is a Windows, HP, Homegroup or other issue.

Hi DeAwnaMom, I'm trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience. Regards, MiyaThis posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, It seems like a Network issue. Please confirm that the problematic machine has the "Client for Microsoft Networks" installed under that 'Adapter properties'. Have you tried both use IP address and computer name? If possible, please help collect the Network trace while reproduce the issue so that we can analysis what happens between the communication with the problematic machine’s network. Network trace 3.3 ================== Please collect network trace log on the problematic machine and the network printer host while reproducing the problem. To do this, a. Download Microsoft Network Monitor Tool from the following link and install it on the machines. http://www.microsoft.com/downloads/details.aspx?FamilyID=983b941d-06cb-4658-b7f6-3088333d062f&displaylang=en b. Start Network Monitor at Start -> Program -> Microsoft Network Monitor 3.3 -> Microsoft Network Monitor 3.3 on the machines. c. On the left-panel, check the LAN connection and unchecked the other unnecessary connections on the machines. d. Click Tools, click Options, switch to the Capture tap, and set the Temporary capture file size (MB) to 200 on the machines. e. Click Create a new capture tap, click Start on the Capture menu in the two Network Monitor windows. f. Now from the problematic machine, reproduce the issue. g. After that, click Stop on the Capture menu on both the machines, and click File->Save as to save the captured files. Please send the two files to workspace. Microsoft Workspace ============== Please upload the collected files to me via the Workspace I set up for you: URL: https://sftus.one.microsoft.com/choosetransfer.aspx?key=a0e9154e-f743-4cfa-b33d-6ee1ce67d36f Password: 6s50#oO7]R Thanks for your effort. Best regards, Spencer ShiPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, It seems like a Network issue. Please confirm that the problematic machine has the "Client for Microsoft Networks" installed under that 'Adapter properties'. Have you tried both use IP address and computer name? If possible, please help collect the Network trace while reproduce the issue so that we can analysis what happens between the communication with the problematic machine’s network. Network trace 3.3 ================== Please collect network trace log on the problematic machine and the network printer host while reproducing the problem. To do this, a. Download Microsoft Network Monitor Tool from the following link and install it on the machines. http://www.microsoft.com/downloads/details.aspx?FamilyID=983b941d-06cb-4658-b7f6-3088333d062f&displaylang=en b. Start Network Monitor at Start -> Program -> Microsoft Network Monitor 3.3 -> Microsoft Network Monitor 3.3 on the machines. c. On the left-panel, check the LAN connection and unchecked the other unnecessary connections on the machines. d. Click Tools, click Options, switch to the Capture tap, and set the Temporary capture file size (MB) to 200 on the machines. e. Click Create a new capture tap, click Start on the Capture menu in the two Network Monitor windows. f. Now from the problematic machine, reproduce the issue. g. After that, click Stop on the Capture menu on both the machines, and click File->Save as to save the captured files. Please send the two files to workspace. Microsoft Workspace ============== Please upload the collected files to me via the Workspace I set up for you: URL: https://sftus.one.microsoft.com/choosetransfer.aspx?key=a0e9154e-f743-4cfa-b33d-6ee1ce67d36f Password: 6s50#oO7]R Thanks for your effort. Best regards, Spencer ShiPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.