NetBEUI printing: "[MyNetworkName]' is not accessible."
NetBEUI printing: "[MyNetworkName]' is not accessible."
1) A longstanding issue: If I open the Desktop Network Icon and select Entire Network, I get Microsoft Windows Network. Clicking on that gets my workgroup (peer-to-peer) network's correct name. But clicking on that generates an error message: "MyNetworkName is not accessible. The network name cannot be found." (Of course, "MyNetworkName" is not my network's real name, which I never post publicly.)
However, if I have already opened a connection to my wife's Transfer Stuff folder (as explained below), I don't get that error message, but instead I get access to her transfer stuff folder with no Outsider login or password needed.
I want a way to access the network (after logging on to the network using the Outsider name and password discussed below), without having to first send a dummy message to my wife's Transfer Stuff folder (using the procedure explained below).
Everything above is symmetrical between our family's two computers. That is, my wife also wants a way to access the network (after logging on to the network using the outsider name andpassword), without having to first send a dummy message to my Transfer Stuff folder.
2) A New Issue. Last May I acquired an HP Officejet Pro 8000 A809a wired printer (my 1991 Deskjet 1200C finally died), connected to my computer using USB. (I couldn't get the intended Network connection to work.) But I am unable to share this printer with my wife's computer.
After selling me the printer and delivering it, HP voice tech support told me that they no longer supported Windows 2000 (although the needed Win2k software and drivers are available on HP's website). That's an understandable decision on HP's part, but I am somewhat annoyed by not having support, especially after having paid $45 extra for "total care" warranty and support. That's why I am hoping to get some help here.
Since the Officejet Pro 8000 A809a manual mentions neither NetBEUI nor NetBios (but only TCP/IP), I am guessing that the printer requires TCP/IP, not only for a pure Network (non-USB) connection, but also for sharing. But if I can get my question 1) answered, maybe I will be able to get printer sharing to work even on NetBEUI.
If the printer definitely requires TCP/IP, I will have to abandon NetBEUI, and I will need to know how to set up a TCP/IP network that separates local network connections from Internet connections.
thread578-679415: Printer sharing with NetBEUI (now closed) was started by Ancalagon (TechnicalUser), with two computers on a NetBEUI local network, who was trying to share a printer located on his XP computer with his Win2k printer.
The following quotation from Ancalagon's thread describes also my situation.
"I have 2 PC's networked via Linksys BEFSR41." . . .
"For security reasons I am only using TCP/IP for the Internet connection, and I have removed the binding for TCP/IP to File and Printer Sharing and also from Client for MS Networks on both PC's.
"I have successfully installed NetBeui on both computers.
"I have defined the same workgroup name on both computers, and the NetBeui protocol is bound to File and Printer Sharing and also to Client for MS Networks."
In my situation (and I think also in Ancalagon's situation) there is no domain network anywhere in sight.
Both of us have been unable to share a printer.
My situation differs from Ancalagon's in these ways.
Instead of a mix of XP and Win2k computers, I have two Win2kSp4 laptops (yes, I know that sticking with Win2k has risks, but I am knowingly taking those risks for reasons that are not relevant here), mine and my wife's. Each computer has a shared "Transfer stuff" folder. And each computer has a "SendTo" folder, each including as a target the other computer's "Transfer stuff" folder.
On each computer, the transfer stuff folder's permissions include the computer's own Administrator and its own Restricted (Limited) User, and also an "Outsider" user, listed in each computer's "Users and Groups," having a password (the same on each computer, and different from the password needed to log on to the computer itself.)
The transfer stuff folders work with no problem. If I have a file I want to send my wife, I select it, right-click it, select SendTo my wife's computer's Transfer Stuff folder, am asked for the Outsider name and password which I enter, and the file immediately goes to my wife (assuming her computer is turned on).
Alternatively, I can open my Desktop Network icon, which has a shortcut to my wife's Transfer Stuff folder, and after going through the same Outsider name and password routine used by SendTo, her Transfer Stuff folder opens and I can drag any file or folder into it.
But to share a printer, in Ancalagon's thread, Serbtastic said that sharing the printer (omitting the XP settings) would "need to populate the lmhosts files on both machines with the following:
"W2KIP W2KNAME #PRE"
"W2KIP is the W2K machine's IP address
"W2KNAME is the W2K machine's name."
"Then, run nbtstat -R to refresh the remote cache name table, and you should be able to see the shares on the other machine by going to Start - Run - and typing \\NAME"
I am guessing that "lmhosts" means Lmhosts not Imhosts, because I have only an Lmhost.sam sample file, never used.
I'm not sure whether in Lmhost.sam the .sam extension refers to sample and should be omitted in actual use, or refers to Security Accounts Manager and should be retained in the filename. (But I'm guessing the .sam should be retained.)
The sample LMhost.sam sample file uses numeric addresses, and I don't know how to find out what those are.
In a response to Serbtastic, Ancalagon wrote "wouldn't I only populate the LMHOSTS file if I was using NetBEUI OVER TCP/IP??"
Serbtastic answered that "The lmhosts file is used for netbios name resolution." But I don't see how that answered Ancalagon's question --- and the issue here is NetBEUI rather than NetBios (although I do vaguely understand that NetBEUI is a sort of variant to NetBios).
And I can't find either "LMHost" or "nbtstat" in HP's Officejet Pro 8000 HP UserGuide-c01659070.pdf.
Finally, even if Serbtastic's suggestions enabled printer sharing, I don't think they would solve my question 1).
In short, I'm incredibly ignorant about all of this stuff (calling myself a TechnicalUser is a gross exaggeration but it was the best description of me in the available choices, although I do know some computing things).
So I will very much appreciate any comments, suggestions, or help (detailed if possible).
Professor Emeritus of Economics
San Jose State University
San Jose, California