TerryWeir
asked on
Print Services in Netware 6.5 and SUSE LINUX Enterprise Server 9
Hello all,
I am currently running a Netware 3.12 Server (IPX only) with printers attached to DOS workstations. The Netware server also hosts all of the DBF files for a FoxPro 2.6 installation. The clients on the network that access the printers and FoxPro are either DOS or Windows 98 running a DOS FoxPro window or FoxPro for Windows 2.6. I have no webserver or need for this part of my network to get out to the internet right now, so that simplifies things a bit
There are so many places that I need to upgrade that it is hard to know where to start. I cannot buy a new Windows XP client since the DOS FoxPro won't run effectively and the FPW2.6 has problems addressing the printers in my Netware Print Queues.
So I am thinking that perhaps a new Netware server, and therefore Print Server, may be in order. I am looking for a little help and explanation of the capabilities of the two newest OSs from Novell. Here are my broad-stroke questions:
1. I have read up on the iPrint server system that comes with Netware 6.5. This is a TCP/IP based print solution, which would necessitate the replacement of all of the DOS boxes with attached printers. I would need to use at least Windows 98 if not XP. Is this correct? Is there much of a bridge between IPX Print Queues or does everything have to go to TCP/IP?
2. In terms of the Linux OS, how would that handle printers? Would I need Linux drivers for my printers, or can I store Windows/generic drivers for the printers either on the server or each individual client?
I am open to move to either system, though I am leery of moving to Linux due to my inexperience with it and the perception that even this newest release will require a large amount of configuration out of the box to get a network up and running.
Any input is appreciated. Should I post this in a Linux section too, or will Netware suffice?
I am currently running a Netware 3.12 Server (IPX only) with printers attached to DOS workstations. The Netware server also hosts all of the DBF files for a FoxPro 2.6 installation. The clients on the network that access the printers and FoxPro are either DOS or Windows 98 running a DOS FoxPro window or FoxPro for Windows 2.6. I have no webserver or need for this part of my network to get out to the internet right now, so that simplifies things a bit
There are so many places that I need to upgrade that it is hard to know where to start. I cannot buy a new Windows XP client since the DOS FoxPro won't run effectively and the FPW2.6 has problems addressing the printers in my Netware Print Queues.
So I am thinking that perhaps a new Netware server, and therefore Print Server, may be in order. I am looking for a little help and explanation of the capabilities of the two newest OSs from Novell. Here are my broad-stroke questions:
1. I have read up on the iPrint server system that comes with Netware 6.5. This is a TCP/IP based print solution, which would necessitate the replacement of all of the DOS boxes with attached printers. I would need to use at least Windows 98 if not XP. Is this correct? Is there much of a bridge between IPX Print Queues or does everything have to go to TCP/IP?
2. In terms of the Linux OS, how would that handle printers? Would I need Linux drivers for my printers, or can I store Windows/generic drivers for the printers either on the server or each individual client?
I am open to move to either system, though I am leery of moving to Linux due to my inexperience with it and the perception that even this newest release will require a large amount of configuration out of the box to get a network up and running.
Any input is appreciated. Should I post this in a Linux section too, or will Netware suffice?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Oops, I meant "to NetWare 6.5" - I'm not suggesting you're not using NetWare now... ;)
Psi - doesn't OES ship with the 6.5 SP3 overlay?
"doesn't OES ship with the 6.5 SP3 overlay?"
Not exactly.
NetWare v6.5 SP3 essentially transforms the server into OES-NetWare. There are some differences, and while they're not earthshattering ones (having to do mainly with VO, eDirectory and iManager) it isn't accurate to say that "OES ships with ... SP3", because fundamentally, its still a NetWare v6.5 server and not OES. Altho I'll concede that its akin to the difference between a green banana and a yellow banana.
Not exactly.
NetWare v6.5 SP3 essentially transforms the server into OES-NetWare. There are some differences, and while they're not earthshattering ones (having to do mainly with VO, eDirectory and iManager) it isn't accurate to say that "OES ships with ... SP3", because fundamentally, its still a NetWare v6.5 server and not OES. Altho I'll concede that its akin to the difference between a green banana and a yellow banana.
SO, OES-NetWare IS NetWare 6.5SP3, so it is, in essence, the overlay, and the only reason to use the overlay if you get the OES media is when OES-NetWare's first SP comes out, which will be NetWare 6.5SP4...
"OES-NetWare's first SP comes out, which will be NetWare 6.5SP4... "
I don't think OES-NetWare SP1 == NetWare v6.5 SP4 is a true assertion. At least, that was not what I got out of BrainShare. The NetWare v6.5 SP roadmap was different from the OES-NetWare SP roadmap, as best I recall. I don't have the BrainShare materials in front of me, but I got the distinct impression that OES-NetWare and NetWare v6.5 would diverge at some point in the near future.
I don't think OES-NetWare SP1 == NetWare v6.5 SP4 is a true assertion. At least, that was not what I got out of BrainShare. The NetWare v6.5 SP roadmap was different from the OES-NetWare SP roadmap, as best I recall. I don't have the BrainShare materials in front of me, but I got the distinct impression that OES-NetWare and NetWare v6.5 would diverge at some point in the near future.
ASKER
Wow, you check back on Monday and you guys were busy this weekend! I am glad to hear that NWv6.5 offers a "kinder, gentler" upgrade path. The way that my environment is pieced together, step by step is the only reasonable way to upgrade.
Based upon what I am reading, I think that I will stay away from the SLES option for now. That may be the only route in the future, but I think that I will give SUSE (and my knowledge of it) more time to develop beofre I run down that road.
I have downloaded the CD images for the NWv6.5 trial. I do not think that it is SP3, but I'll check. Maybe I can get the update for it. I think that I will convert a spare PC to a test server and see how things go..
THanks for your help. on this. I'm sure that I will have questions later when I dig into the install, but you guys have given me a good direction to go in
Based upon what I am reading, I think that I will stay away from the SLES option for now. That may be the only route in the future, but I think that I will give SUSE (and my knowledge of it) more time to develop beofre I run down that road.
I have downloaded the CD images for the NWv6.5 trial. I do not think that it is SP3, but I'll check. Maybe I can get the update for it. I think that I will convert a spare PC to a test server and see how things go..
THanks for your help. on this. I'm sure that I will have questions later when I dig into the install, but you guys have given me a good direction to go in
If you go to http://support.novell.com/filefinder/18197/index.html, look for the 6.5 SP3 overlay ISO's (should be 2 of them)
NW65PRODSP3.ISO and NW65OSSP3.ISO
NW65PRODSP3.ISO and NW65OSSP3.ISO
On the server, flag the databases shareable (and I think, transactional) and use the SET CLIENT FILE CACHING ENABLED = OFF and SET LEVEL 2 OPLOCKS ENABLED = OFF, and on the client side turn off oplocks as well in the Novell client properties: in the Win9x client32, in advanced settings, set Opportunistic Locking off and set True Commit on, and in the WinNT/2K/XP client, set File Caching off and File Commit on. If I forgot anything, I'll bet PsiCop remembers...