If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Can't Print
PC A
Win 7 Pro pc has USB attached printer. I seen via WiFi tied to home LAN router I looked at the printer properties and see that is is shared. PC B Win XP Pro pc can attach via WiFi to home LAN I try to print from the PC B but docs show in PC B queue but does not print through PC A. What else to check ? |
Ads |
#2
|
|||
|
|||
Can't Print
More info
PC A sees the internet through the router. PC B sees the internet through the router via WiFi. But PC B cannot see PC A. What the ? OGee wrote: PC A Win 7 Pro pc has USB attached printer. I seen via WiFi tied to home LAN router I looked at the printer properties and see that is is shared. PC B Win XP Pro pc can attach via WiFi to home LAN I try to print from the PC B but docs show in PC B queue but does not print through PC A. What else to check ? |
#3
|
|||
|
|||
Can't Print
OGee wrote:
More info PC A sees the internet through the router. PC B sees the internet through the router via WiFi. But PC B cannot see PC A. What the ? PC A can see PC B. PC B cannot see PC A. I deleted printers on PC B and tried to Add but it will not let me even though PC B shows those printers in the list. OGee wrote: PC A Win 7 Pro pc has USB attached printer. I seen via WiFi tied to home LAN router I looked at the printer properties and see that is is shared. PC B Win XP Pro pc can attach via WiFi to home LAN I try to print from the PC B but docs show in PC B queue but does not print through PC A. What else to check ? |
#4
|
|||
|
|||
Can't Print
I am on a different Win XP Pro PC and cannot print to PC A even though
it shows in list. If I go to the printers list, it says the PC A printer name is invalid. I can sit at PC A and print to this printer. WHat happened ? OGee wrote: OGee wrote: More info PC A sees the internet through the router. PC B sees the internet through the router via WiFi. But PC B cannot see PC A. What the ? PC A can see PC B. PC B cannot see PC A. I deleted printers on PC B and tried to Add but it will not let me even though PC B shows those printers in the list. OGee wrote: PC A Â*Â*Â* Win 7 Pro pc Â*Â*Â* has USB attached printer. Â*Â*Â* I seen via WiFi Â*Â*Â* tied to home LAN router Â*Â*Â* I looked at the printer properties and see that is is shared. PC B Â*Â*Â* Win XP Pro pc Â*Â*Â* can attach via WiFi to home LAN I try to print from the PC B but docs show in PC B queue but does not print through PC A. What else to check ? |
#5
|
|||
|
|||
Can't Print
OGee wrote:
More info PC A sees the internet through the router. PC B sees the internet through the router via WiFi. But PC B cannot see PC A. What the ? Just for fun, run this for me. You can try the program on each PC (because each PC can see the Internet and get a copy of it). http://www.unixwiz.net/tools/nbtscan.html http://www.unixwiz.net/tools/nbtscan-1.0.35.exe nbtscan 192.168.1.0/24 The address value should match the value of "ipconfig" you get in Command Prompt, on each machine. In the example, it's going to check 192.168.1.x or about 256 addresses (approximately). ipconfig Windows IP Configuration Ethernet adapter Local Area Connection 2: Connection-specific DNS Suffix . : IP Address. . . . . . . . . . . . : 192.168.2.101 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.2.1 If I wanted to sweep all 256 subnets, I could adjust the netmask on the command. Doing this though, is going to take time. nbtscan 192.168.1.0/16 As that needs to check at least 64K addresses (approximately). It should scan all of 192.168.x.y. First check your ipconfig results, and see if the machines are (nominally) on the same subnet. Then give nbtscan a whirl for fun. Here you can see my scan, where I've "discovered" one of my OSes is on the wrong Workgroup. https://s8.postimg.cc/7b5m1derp/nbts...s_must_fix.gif When I set that up, initially .104 was a member of WORKGROUP and I changed it to MSHOME (the value you get if you use HomeGroups). After I made the change and rebooted as requested by the System control panel, I couldn't even *see* the machine with nbtscan. And that was because I needed to go back to the .104 machine and enable network file and printer sharing. If a machine won't show the network neighborhood, that could be the reason why. Usually it puts a prompt at the top of the window, to fix it. Paul |
#6
|
|||
|
|||
Can't Print
PC B nbtscan.exe 192.168.1.0/24
sees PC A and all other PCs. ipconfig agrees. All are in the same group. All are in 192.168.1 PC X a Win Pro PC sees the same. I did verify that PC A shares the printer. And I can print from PC A. If I go to Microsoft Windows Network is see PC A listed but clicking it I get this: --------------------------- Meow --------------------------- \\Katwin7 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 name is no longer available. --------------------------- OK --------------------------- This all used to work ! What permissions ? There are other PCs listed there and I can click on each and see folders etc, but not for PC B. Paul wrote: OGee wrote: More info PC A sees the internet through the router. PC B sees the internet through the router via WiFi. But PC B cannot see PC A. What the ? Just for fun, run this for me. You can try the program on each PC (because each PC can see the Internet and get a copy of it). http://www.unixwiz.net/tools/nbtscan.html http://www.unixwiz.net/tools/nbtscan-1.0.35.exe nbtscan 192.168.1.0/24 The address value should match the value of "ipconfig" you get in Command Prompt, on each machine. In the example, it's going to check 192.168.1.x or about 256 addresses (approximately). ipconfig Windows IP Configuration Ethernet adapter Local Area Connection 2: Connection-specific DNS Suffix . : IP Address. . . . . . . . . . . . : 192.168.2.101 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.2.1 If I wanted to sweep all 256 subnets, I could adjust the netmask on the command. Doing this though, is going to take time. nbtscan 192.168.1.0/16 As that needs to check at least 64K addresses (approximately). It should scan all of 192.168.x.y. First check your ipconfig results, and see if the machines are (nominally) on the same subnet. Then give nbtscan a whirl for fun. Here you can see my scan, where I've "discovered" one of my OSes is on the wrong Workgroup. https://s8.postimg.cc/7b5m1derp/nbts...s_must_fix.gif When I set that up, initially .104 was a member of WORKGROUP and I changed it to MSHOME (the value you get if you use HomeGroups). After I made the change and rebooted as requested by the System control panel, I couldn't even *see* the machine with nbtscan. And that was because I needed to go back to the .104 machine and enable network file and printer sharing. If a machine won't show the network neighborhood, that could be the reason why. Usually it puts a prompt at the top of the window, to fix it. Paul |
#7
|
|||
|
|||
Can't Print
OGee wrote:
PC B nbtscan.exe 192.168.1.0/24 sees PC A and all other PCs. ipconfig agrees. All are in the same group. All are in 192.168.1 PC X a Win Pro PC sees the same. I did verify that PC A shares the printer. And I can print from PC A. If I go to Microsoft Windows Network is see PC A listed but clicking it I get this: --------------------------- Meow --------------------------- \\Katwin7 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 name is no longer available. --------------------------- OK --------------------------- This all used to work ! What permissions ? There are other PCs listed there and I can click on each and see folders etc, but not for PC B. They actually mention folder permissions on a shared folder, in the case of folder sharing not working properly. Now, how does printing work ? Does one machine write a file into a "queue" on another machine ? I thought the path involved "spooler" processes or something, not direct write into a folder. https://www.online-tech-tips.com/com...-peer-network/ "You might not have permission to use this network resource" In this one, the most credible item is the idea a firewall is blocking it. When the firewall wasn't blocking it previously. https://www.thewindowsclub.com/speci...nger-available "The specified network name is no longer available" ******* Note: If you've been screwing around with the network driver, you'll need to turn on file sharing and printing again. Control Panels : Network and Sharing Center : Advanced Sharing Settings and tick the "Turn On File and Printer Sharing" radio button. About the third picture down here, shows the dialog box with the three sets of radio buttons. https://www.howtogeek.com/howto/9040...s-7-and-vista/ But none of this stuff seems likely at the moment. Do you remember the history of the broken machine ? What have you done recently to the machine that is significant ? Is that machine set for full auto "Updates", such that a Cumulative update came in and did this ? How I usually get burned, is the network driver changes or the network is instantiated again (the "network number" is incremented by one), and that wipes out the previous careful setting of enabling file and printer sharing. But normally you see a warning dialog at the top of an Explorer file manager window. Usually in a short period of time, I do something that causes the warning dialog to appear. And then I know I just screwed it up. Just noticing stuff like that, and keeping track of changes, helps reduce the number of possibilities you might have to consider. I'm not an IT guy, and I don't have a giant flowchart for networking with every possibility noted down. The only ones I can tell you about, are the ones that got me a time or two. Paul |
Thread Tools | |
Display Modes | |
|
|