How To Install Netbeui On Windows 7
Remaining Submit Skip this Thank you! Home How to Install NetBEUI on Windows XP The files remote host or network may be down. Netbeui Protocol Windows 7.
I have had a Windows XP computer networked to my OS/2 computer for years. I access the volumes and print on the attached printer. Now I want to move to Win7. Apart from the huge reinstall of applications I have to do I in the Windows environment I have a conceptual blockage with working out how to retain that connection if possible?
XP connects because I have Netbeui working on it. Netbeui is not available for Win7. I have never understood SAMBA or how to get it to work. Another option is NFS but the reading and the potential cut and try seems it will blow out. Anyone here can offer some clues?
Thanks, Victor Bien To reply by e-mail edit this address to the correct form: vbien at attglobal dot net System: Gigabyte GS-MA74GM-S2 mb, AMD Athlon II X2 socket AM3 CPU, 2 GB DDR2 RAM, ATI Radeon X300 video, Soundblaster Live soundcard, on-board NIC, SATA primary disk, IDE secondary disks, LG CD burner, InitIO scsi hba, HP 5p scanner, cable internet access via LAN, Lexmark E310 laser printer. MCP2, FP5, 14.103aW4 kernel, C: FAT16 540MB, D: HPFS 2.8GB, E: JFS 470 GB, F: JFS 100 GB, G: JFS 7.2 GB, H: JFS 7.2 GB, USB stick or hard disk connect facility, always run OD 1.53 Tab Launch pad with XWorkplace XPager, PM Fax 3.00.05e, some PIMs, Screen Util, Apache 2, ftpd, PMMail 2.20.2382, Firefox ver 3.6.8, DeScribe 5.0.6 and a couple of Win-OS2 programs. Doug Bissett 05.11.11 8:18. On Sat, 5 Nov 2011 09:56:19 UTC, Victor Bien wrote: I have had a Windows XP computer networked to my OS/2 computer for years.
I access the volumes and print on the attached printer. Now I want to move to Win7. Apart from the huge reinstall of applications I have to do I in the Windows environment I have a conceptual blockage with working out how to retain that connection if possible? XP connects because I have Netbeui working on it. Netbeui is not available for Win7. I have never understood SAMBA or how to get it to work.
Apparently (I haven't tried it), you can install the NETBEUI that works with XP, to Win7. SAMBA does work, but I have never found a combination of parts that actually work reliably. All you really need is the client part (EVFS or NETDRIVE) to connect to a windows machine. SAMBA itself is only needed if you wish to connect Win7 to an eCS machine.
Another option is NFS but the reading and the potential cut and try seems it will blow out. Anyone here can offer some clues? ThanksVictor Bien It is probably a good idea to learn about SAMBA, since modern versions of windows simply don't want to work with the older PEER networking, and MS seems to be going out of their way to make sure that it doesn't work. The other main reason to change is to get support for files that are larger than 2 GB. From the eComStation of Doug Bissett dougb007 at telus dot net (Please make the obvious changes, to e-mail me) Bob Plyler 07.11.11 4:19. On 05:56 AM, Victor Bien wrote: I have had a Windows XP computer networked to my OS/2 computer for years. I access the volumes and print on the attached printer.
Now I want to move to Win7. Apart from the huge reinstall of applications I have to do I in the Windows environment I have a conceptual blockage with working out how to retain that connection if possible? XP connects because I have Netbeui working on it. Netbeui is not available for Win7. I have never understood SAMBA or how to get it to work.
Install Netbeui On Windows 7
Another option is NFS but the reading and the potential cut and try seems it will blow out. Anyone here can offer some clues?
ThanksVictor Bien AFAIK, TCPBEUI works. Bob Plyler Peter Brown 07.11.11 5:34. Hi Victor Victor Bien wrote: I have had a Windows XP computer networked to my OS/2 computer for years. I access the volumes and print on the attached printer.
Now I want to move to Win7. Apart from the huge reinstall of applications I have to do I in the Windows environment I have a conceptual blockage with working out how to retain that connection if possible? XP connects because I have Netbeui working on it.
Netbeui is not available for Win7. I have never understood SAMBA or how to get it to work. Another option is NFS but the reading and the potential cut and try seems it will blow out. Anyone here can offer some clues?
ThanksVictor Bien For sharing files you could try ftp - FireFTP is a useful addon to Firefox/Seamonkey. Does the printer have an ip address or is it a shared printer? Regards Pete john.@nospam.com.au 06.11.11 14:47. In, Victor Bien writes: I have had a Windows XP computer networked to my OS/2 computer for years. I access the volumes and print on the attached printer. Now I want to move to Win7. Apart from the huge reinstall of applications I have to do I in the Windows environment I have a conceptual blockage with working out how to retain that connection if possible?
XP connects because I have Netbeui working on it. Netbeui is not available for Win7. I have never understood SAMBA or how to get it to work. Another option is NFS but the reading and the potential cut and try seems it will blow out. Anyone here can offer some clues? I reluctantly switched protocol to Netbios/TCPIP, which is included in 4.52. It was relatively painless.
I maintained the security of my Windoze box by denying it access to the router. Mike Luther 07.11.11 19:55. The problem about allowing use of Netbios/TCPIP with OS/2 itself is that it is possible for an external source outside of even your 4.52 OS/2 box that is connected to the Internet to puncture your OS/2 box itself! I have actually seen where external virus operations can attack even an OS/2 box using this protocol to dump files into the OS/2 box in virtually every directory!
Now that done, sure, maybe they are WIndows viri stuff. And that doesn't work on an OS/2 box, unless, per chance, you have the device driver(s) also installed on your OS/2 box to let it interface to, say, an internal OS/2 box on your network behind the router. Another naughty vector for trouble. There is more! If you can play this stunt, you can also modify, say, the CONFIG.SYS file to 'run' something else on startup that is punched in to your OS/2 box that way! Or, groan, even a DOS nasty starting point issue in even the conventional AUTOEXEC.BAT on it. I have seen this contamination for real on several OS/2 boxes in the past with Netbios/TCPIP installed and it has been a MESS to decontaminate the boxes.
As well I have even actually seen a contamination issue where remote TCPIP probing has been done to even modify the motherboard BIOS settings on an OS/2 4.52 box to slam in the keyboard man-in-the-middle snoopie. I.STRONGLY recommend that one does not use Netbios/TCPIP on an OS/2 box if there is any way to avoid it. - Sleep well; OS2's still awake!;) Mike Luther Rodney Pont 08.11.11 1:12. On Tue, 08 Nov 2011 03:55:12 +0000, Mike Luther wrote: I have seen this contamination for real on several OS/2 boxes in the past with Netbios/TCPIP installed and it has been a MESS to decontaminate the boxes.
As well I have even actually seen a contamination issue where remote TCPIP probing has been done to even modify the motherboard BIOS settings on an OS/2 4.52 box to slam in the keyboard man-in-the-middle snoopie. I.STRONGLY recommend that one does not use Netbios/TCPIP on an OS/2 box if there is any way to avoid it. Just block ports 137/138 and 139 to/from the internet. Then you can safely use it internally only.
Regards - Rodney Pont The from address exists but is mostly dumped, please send any emails to the address below e-mail rpont (at) gmail (dot) com Victor Bien 08.11.11 3:35. It's a shared printer. I use FTP for file access. I run the OS/2 FTP server and swap files from a Vista laptop which won't connect via Windows networking. I use to make the FTP server available to the internet to allow fetching files when I'm at client's sites but was so troubled by 'hammering' - troublemakers making repeated attempts to login and threatening havoc, I deleted the port forwarding to the OS/2 FTP. I now safely FTP within my LAN only.
(I installed a secure FTP server on my XP machine - it gets hammered as well but it has an anti-hammering facility to throw the troublemakers off). I could buy a small print server with a tcp/ip connection I suppose. I've never tried to print from OS/2 to a print server. Can I assume it'll all be straightforward. That'll just mean that trying to connect the OS/2 to the Windows world is all getting too hard? Regards Pete - Peter Flass 08.11.11 4:36.
On 11/7/2011 10:55 PM, Mike Luther wrote: The problem about allowing use of Netbios/TCPIP with OS/2 itself is that it is possible for an external source outside of even your 4.52 OS/2 box that is connected to the Internet to puncture your OS/2 box itself! I have actually seen where external virus operations can attack even an OS/2 box using this protocol to dump files into the OS/2 box in virtually every directory!
Now that done, sure, maybe they are WIndows viri stuff. And that doesn't work on an OS/2 box, unless, per chanceyou have the device driver(s) also installed on your OS/2 box to let it interface to, say, an internal OS/2 box on your network behind the router. Another naughty vector for trouble. There is more! If you can play this stunt, you can also modify, say, the CONFIG.SYS file to 'run' something else on startup that is punched in to your OS/2 box that way! Or, groan, even a DOS nasty starting point issue in even the conventional AUTOEXEC.BAT on it. Simple enough to fix if you have a firewall router: Just don't allow NETBIOS/TCP to pass thru the router.
I use it to share files on my home network between OS/2, Linux, and windoze, but not externally. Peter Brown 08.11.11 5:31. I don't know how current it is, but I use a Zonet ZPS2102 here on my LAN. I have Warp Server, eCS 1.03, eCS 1.2, Linux Mint 8 and 11 systems on the LAN and all can make use of the print server and the printer connected to it.
I chose the Zonet ZPS2102 in particular as it had a USB-2 port on it and I wanted to be able to drive the printer, a Brother HL-5050, at full speed from older systems that did not have such support. I could also connect two additional printers to the server, but have no need at this point to do so. Dave Dave Paul Ratcliffe 08.11.11 10:19. On Tue, 08 Nov 2011 07:36:37 -0500, Peter Flass wrote: On 11/7/2011 10:55 PM, Mike Luther wrote: The problem about allowing use of Netbios/TCPIP with OS/2 itself is that it is possible for an external source outside of even your 4.52 OS/2 box that is connected to the Internet to puncture your OS/2 box itself! Simple enough to fix if you have a firewall router: Just don't allow NETBIOS/TCP to pass thru the router.
I use it to share files on my home network between OS/2, Linux, and windoze, but not externally. Yes, to anyone with even half a brain it is trivial to fix. Most routers used for domestic stuff are NAT routers anyway, so are blocked by default. That's doesn't apply to Luther though as he has considerably less than half a brain. Trevor Hemsley 08.11.11 14:18.
On Tue, 8 Nov 2011 03:55:12 UTC in comp.os.os2.misc, Mike Luther wrote: I have actually seen where external virus operations can attack even an OS/2 box using this protocol to dump files into the OS/2 box in virtually every directory! Oh, please, what these viruses do is look at all your network shares and try to write copies of themselves to them. There's nothing particularly special about this.
They don't 'puncture' OS/2, they just find the drives that are mapped and write to them. Trevor Hemsley, Brighton, UK Trevor dot Hemsley at ntlworld dot com Dave Yeo 08.11.11 16:16. I have never seen, or heard of, a windows virus actually succeed in what it is meant to do, however, I expect that some viruses will actually do something on OS/2. I would not be too surprised to find out that some system crashes, and/or, Browser crashes, are caused by various viruses attempting to do their thing. The above scenario could be caused by a windows machine executing a virus that spreads infected files to every open network share that it can find. That doesn't mean that OS/2 will actually run the files (which may be possible if they are run by ODIN, or the like), but they still take up room on the disk, and if any windows machine accesses them, the windows machine will probably be infected.
Victor Bien 15.11.11 2:38. I read up on this particular print server but am rather discouraged to chase it. The reviews out there are not good. I tried to find some discussion about what makes one print server better than another one but it will take a lot of time to get a good handle on the subject. My understanding of a print server is almost a complete vacuum!
How do they work? How do they differ one from the other? At the simplest would the thing take bytes from the LAN cable and just past it through to the USB port? If that is the case why do some of them have to have Windows driver installed? If there is such an animal as a 'dumb' print server OS/2 could print to it couldn't it?
I mean the spooler and the OS/2 printer driver (Lexmark E310 in my case) would just shove the data out through the network port instead of the USB port I'm presently using, find the IP address of the print server and then just flow through it to the printer and you have your printouts? You get my drift? What criteria do I use to ascertain which print server to try? I may try to buy one via eBay. I do have a local 'corner shop computer shop' who lets me try out gear on try and see basis and perhaps I could identify a suitable one that way.
My fundamental problem is I don't know how a print server works! I don't know what I'm looking for! If I can get my OS/2 computer to print through a print server and I can swap files with Filezilla and the OS/2 FTP server then my problem to keep it ticking away with any Windows computer will be solved. Victor Bien Peter Brown 15.11.11 9:00. On Sat, 5 Nov 2011 09:56:19 UTC, Victor Bien wrote: I have had a Windows XP computer networked to my OS/2 computer for years. I access the volumes and print on the attached printer. Now I want to move to Win7.
Apart from the huge reinstall of applications I have to do I in the Windows environment I have a conceptual blockage with working out how to retain that connection if possible? XP connects because I have Netbeui working on it. Netbeui is not available for Win7. I have never understood SAMBA or how to get it to work.
Another option is NFS but the reading and the potential cut and try seems it will blow out. Anyone here can offer some clues? ThanksVictor Bien I would strongly suggest that you disable SMB2 on any Windows Vista or Windows 7 machine. It just does not play well with others. Google 'disable SMB2' to get the details. Chuck McKinnis Victor Bien 28.04.12 15:25. Well it's several months down the track and I'm back on this project/issues/problems.
I've downloaded and installed the eCS Samba WPI packs. The doco says the setup is all done and I don't have to worry about the manual installation section. However, now that the WPIs are installed, protocol.ini and config.sys suitably edited and the computer restarted it's obviously not complete. There is no REXX setup facility, there is no smbd process running, there is no samba.conf except an old one back in 2000 when I tried to have a go then. What's missing? The documentation is very sparse - not surprising since all of it is a volunteers effort. There is one spot to download 4 zip files but when you click on the fourth one the page that comes up is blank!!??
So I'm back to the point why I did not follow through trying to get Samba working on OS/2 back in 2000. (If emailing edit the following into the correct form: vbien at attglobal dot net, thanks).
Andreas Kohl 29.04.12 23:25. That was interesting reading but it doesn't help me get anywhere. I failed to make clear that I want the Samba server (I'm not so interested in the client) working so I can connect to my OS/2 4.52 from Windows 7. I feel sure that when I get it working correctly I'll get connection because I have an NAS which has a firmware Linux and it appears as a drive in Win 7. The basic Samba is ported from Linux. Up to now I've worked happily away with XP talking to my OS/2 repository machine over netbeui. I tried installing netbeui on Win 7 and can't do it.
(The Win 7 I'm talking about is the superb 64 bit version). I can use Filezilla to access files on the OS/2 talking to the OS/2 plain FTP server but that's not the same as network access (on the XP the OS/2 folders and files act just like its local disk); and I want access to the printer attached to OS/2. From the above I know I can use a print server but the trouble with that is I get more clutter in my Study. I'm led to believe that eCS has got a basic server working (at least that is what the page says).
Trouble is when I've done 'everything' from that page it's not complete. Where do I turn to? I intend to try quite hard to get success along this approach before giving up if I can't get anywhere.
Andreas Kohl 30.04.12 9:48. Sorry for inadvertently misleading you folk about where I'm. I got overwhelemed by the eCS web page and completely failed to notice the downloads for the server stuff which I'm now aware of. I'll be doing that shortly and let you know how I get on. I want Samba to get a proper network drive and network printer connection and from my observation with the Linux based NAS drive which just connects without any fuss my hope and expectation is that once I have a server running my OS/2 will just connect. I want my OS/2 computer to continue to be network drive and network print server like with XP - no limitation of file transfer size, no limitations at all! - the computer then just appears just like a local volume on the Windows computer.
Why do I keep my OS/2 computer? I keep all manner of notes with DeScribe, reposit all e-mail messages back to 1996, use the original IBM PIMS to keep addresses and phone numbers, keep other quick memo notes, run PMFax which reposits faxes back at least 6 months, run the solid HP Scanjet 5p scanner which is so solidly built it still works like nothing has happened for 17 years. I resist being driven by the culture of built-in obsolesence. As far as I'm concerned the aforementioned apps are as fresh as they were from the day they were published!
The hardware running my OS/2 has gone through at least three or four generations. Barry Landy 01.05.12 12:38. On Tue, 1 May 2012, Victor Bien wrote::On 1/05/2012 2:48 AM, Andreas Kohl wrote:: Hello,:: It seems, you cannot change security settings on your Win Client thats: connecting to your OS/2-Server?:: But why samba, do you need to transfer big files or similar?: Or do you have to connect via Netbios over TCP to other Windows servers?:: Andreas::Sorry for inadvertently misleading you folk about where I'm.
I got:overwhelemed by the eCS web page and completely failed to notice the downloads:for the server stuff which I'm now aware of. I'll be doing that shortly and:let you know how I get on.::I want Samba to get a proper network drive and network printer connection and:from my observation with the Linux based NAS drive which just connects without:any fuss my hope and expectation is that once I have a server running my OS/2:will just connect. I want my OS/2 computer to continue to be network drive:and network print server like with XP - no limitation of file transfer size,:no limitations at all!
- the computer then just appears just like a local:volume on the Windows computer.::Why do I keep my OS/2 computer? I keep all manner of notes with DeScribe,:reposit all e-mail messages back to 1996, use the original IBM PIMS to keep:addresses and phone numbers, keep other quick memo notes, run PMFax which:reposits faxes back at least 6 months, run the solid HP Scanjet 5p scanner:which is so solidly built it still works like nothing has happened for 17:years. I resist being driven by the culture of built-in obsolesence. As far:as I'm concerned the aforementioned apps are as fresh as they were from the:day they were published! The hardware running my OS/2 has gone through at:least three or four generations. FWIW I also run PIMS for addresses and phone nummbers.
Until the advent of Google Calendar I used it for appointments also. Barry Landy Email: Remove nospam in from address 192, Gilbert Road, Cambridge CB4 3PB Victor Bien 01.05.12 17:53. On 6/11/2011 2:18 AM, Doug Bissett wrote: On Sat, 5 Nov 2011 09:56:19 UTC, Victor Bien wrote: I have had a Windows XP computer networked to my OS/2 computer for years. I access the volumes and print on the attached printer. Now I want to move to Win7.
Apart from the huge reinstall of applications I have to do I in the Windows environment I have a conceptual blockage with working out how to retain that connection if possible? XP connects because I have Netbeui working on it. Netbeui is not available for Win7. I have never understood SAMBA or how to get it to work.
Apparently (I haven't tried it), you can install the NETBEUI that works with XP, to Win7. SAMBA does work, but I have never found a combination of parts that actually work reliably. All you really need is the client part (EVFS or NETDRIVE) to connect to a windows machine. SAMBA itself is only needed if you wish to connect Win7 to an eCS machine.
Another option is NFS but the reading and the potential cut and try seems it will blow out. Anyone here can offer some clues? ThanksVictor Bien It is probably a good idea to learn about SAMBA, since modern versions of windows simply don't want to work with the older PEER networkingand MS seems to be going out of their way to make sure that it doesn't work. The other main reason to change is to get support for files that are larger than 2 GB. eCS's Samba server package installed fairly easily as the page claimed.
After slightly further editing of config.sys (to put in two LIBPATH spots where the Samba packge is installed) and rebooting I got connection! This is confirmed for all three Windows computers: XP SP3, Vista laptop and the new 64 bit Windows 7 I'm working up to replace the XP. Connecting to the OS/2 disks/volumes is 100%. I test copied a folder with over 2000 files occupying about 25 MB and it came across in a jiff. A big accolade from me to those who put that all together, in WPI form as well, which made installation indeed as simple as in Windows or the Mac.
A WPS configuration folder is created and one can complete the installation and make further adjustments with GUI 'widgets'. The installation gives one the option of creating a new Samba configuration from scratch or porting over one's IBM LAN Manager settings.
I chose the latter. I'll be thinking and suggesting how the above page may be improved although in my case I fell over badly due to rushing and being mentally scattered: trying to do multiple things, not computer related where the computer system can't be off-line for long.
There is one problem to be solved: I can't print to the printers which are Samba shared. When I do a test print you can see a brief Samba message popup saying various things are happening but no job appears in the OS/2 printer window; the printer light blinks hopefully but nothing prints. Because of thi I might still have to go back to the IBM LAN manager for a while longer. That's not hard to do - just copy the IBM LAN version of config.sys to be the active one and the same with IBMCOM protocol.ini and reboot. (If emailing edit the following into the correct form: vbien at attglobal dot net, thanks). Alex Taylor 02.05.12 6:09.
Steps To Install Windows 7
On Mon, 30 Apr 2012 08:24:44 UTC, Victor Bien wrote: I'm led to believe that eCS has got a basic server working (at least that is what the page says). Trouble is when I've done 'everything' from that page it's not complete. So I'm lost.
Where do I turn to? I intend to try quite hard to get success along this approach before giving up if I can't get anywhere. There is a newsgroup/mailing list for the OS/2 Samba port - you might have better luck posting your questions there: gmane.org.netlabs.samba.user on. Alex Taylor Fukushima, Japan Please take off hat when replying. Martinot 28.02.15 14:08. Victor Bien wrote: I want Samba to get a proper network drive and network printer connection and from my observation with the Linux based NAS drive which just connects without any fuss my hope and expectation is that once I have a server running my OS/2 will just connect. I want my OS/2 computer to continue to be network drive and network print server like with XP - no limitation of file transfer size, no limitations at all!
- the computer then just appears just like a local volume on the Windows computer. Why do I keep my OS/2 computer? Rsorder reviews. I keep all manner of notes with DeScribe, reposit all e-mail messages back to 1996, use the original IBM PIMS to keep addresses and phone numbers, keep other quick memo notesrun PMFax which reposits faxes back at least 6 months, run the solid HP Scanjet 5p scanner which is so solidly built it still works like nothing has happened for 17 years. I resist being driven by the culture of built-in obsolesence.
As far as I'm concerned the aforementioned apps are as fresh as they were from the day they were published! The hardware running my OS/2 has gone through at least three or four generations.
More power to you!:) BTW: Do you not want to sync your files to cloud solutions, or your PIMS data to your phone and other mobile devices? I would personally really miss that. br, martinot.
I want to use the Netbeui network protocol in a 32-bit Windows 7 system. I keep seeing the question, 'Why would you want to bother doing that?'
The reason is that we have some old equipment which needs some old software to operate it which does not understand TCP/IP and does understand Netbeui. The provider company is giving us good support. I have followed their instructions for copying Netbeui files into my system directories and running an executable which installs Netbeui as an active protocol. The software runs, but it cannot communicate with the equipment. I went into advanced settings and I was able to move the Netbeui protocol to the top of the binding list. Still nothing.
If I move straight back to the XP machine I want to replace, it works fine. So the problem has to be in the Windows 7 configuration. I'm bringing the question to EE thinking that this might be an OS question. I'm guessing the solution to this might be something easy and obvious that's staring me in the face. What am I missing?
Could their be a port issue?