ronc@XLNVAX.EXCELAN.COM (Ron Cully) (01/17/90)
> We are currently looking into ways to connect a Novell network > (which is using IBM token-ring adapters) onto a TCP/IP network. > I am aware of Wollongong and Interlan software available to do > this. Has anyone else tried modifying the Clarkson "stuff" to > do this, or have you found any other ways to accomplish this? > > Maria Neugebauer > When you say you want to connect a Novell network, what exactly do you mean. There are many different aspects of connecting a Novell network to TCP/IP. Do you mean you want IPX over TCP/IP routing, do you want TCP/IP client access from NetWare clients, do you want TCP/IP host access to NetWare servers, etc.. There is one way for you to connect into TCP/IP networks for a number of things if you have a VAX and are willing to purchase some software for it. In your situation, you can install a NetWare router (formerly and incorrectly known as a bridge) so you connect the Novell network to a Ethernet network. On the Ethernet, you install a VAX with NetWare for VMS, LAN Service NFS, and either Multinet or LAN Service for VMS (TCP/IP host based and front-end-processor based respectively). All of these products are available from Novell. Alternately, you can use another TCP/IP implmenetation on the VAX (if one all ready exists) like Wollongong, DEC, CMC etc.. LAN Service NFS will work with Wollogong and DEC, but other transport dependent NFS implmentations (like Wollongong's) should work too. I have experience with the LAN Service NFS, Multinet, and NetWare for VMS configuration and I recommend it (but then I'm biased being from Novell). Anyway, with the VAX configured this way, you get the following functionality: 1. NetWare clients see the VAX as a typical NetWare server 2. NetWare clients can use TES to log directly into the VAX. From there, the NetWare user is effectively a remote terminal to the VAX and the user has access to all VAX applications. Hence, the user can then Telnet from the VAX to any other TCP/IP hosts and FTP files to/from other non-NFS hosts. The user also has access to SMTP mail. 3. NFS clients (e.g. Suns or PCs with PC-NFS) on the Ethernet can mount volumes on the VAX. These volumes can be the same directories used by the NetWare clients. Hence, NFS clients and NetWare clients can share files. Conversely, NetWare clients can access files deposited by the NFS clients. 4. Non-NFS TCP/IP hosts can access NetWare files on the VAX through FTP. This may be too expensive for some sites but it does offer a lot of unique functionality which is unavailable otherwise (at least to date). Hope this offers something useful (if not to you, someone else). Ron Cully Product Marketing Engineer NetWare for VMS
D1MARIA@AKRONVM.BITNET (Maria Neugebauer) (01/17/90)
We are currently looking into ways to connect a Novell network (which is using IBM token-ring adapters) onto a TCP/IP network. I am aware of Wollongong and Interlan software available to do this. Has anyone else tried modifying the Clarkson "stuff" to do this, or have you found any other ways to accomplish this? Maria Neugebauer University of Akron Internet: d1maria@vm1.cc.uakron.edu Computer Center Bitnet: d1maria@akronvm
LAUSSEGG@AWIWUW11.BITNET (Robert Laussegger) (01/17/90)
Maria.. It really depends on what you will do. We are running TCP/IP on an IBM host, connected via Ethernet and Novell with mixed configuration. That means we are using Token Ring adapters as well as Ethernet and PC-Lan boards. The only problem that occurs in the moment is the need of rebooting after using Novell to get any connection via TCP/IP. The drivers we are using are depending on the LAN-adapter. I will check if there is any freeware for these Token Ring adapters. I am also checking the suggested solutions (see above in the list *questions*) using Novell and TCP/IP at the same time. I can give you results in a few days. If you speak german (and your name sounds like that) send me direct mail it would be easier. Robert <LAUSSEGG@AWIWUW11.BITNET>