kung@maven.u.washington.edu (01/18/91)
I am interested in linking XNS based xerox workstations together with Novell Based PC's. The most important service for me is Email services. The file services or printer services are secondary. Interesting mix huh? Darwei Kung kung@max.u.washington.edu
vdra_ltd@uhura.cc.rochester.edu (Valerie Drake) (01/19/91)
In <1991Jan17.202331.1@maven.u.washington.edu> kung@maven.u.washington.edu writes: >I am interested in linking XNS based xerox workstations together with Novell >Based PC's. The most important service for me is Email services. The file >services or printer services are secondary. Interesting mix huh? >Darwei Kung >kung@max.u.washington.edu Although the two operating systems are basically incompatible, you can set up a workstation which will talk to and be logged in on both. The workstation needs to have 2 network boards in it, configured for different interrupts and memory addresses. Configure the drivers for each net os to the different interrupts. For instance if you have an Enet card set for int 4 and one for int 5, configure the IPX file for int 4, and the xns enet.sys driver for int 5. Load the XNS drivers and login to XNS first, then load ipx and net3 and login to Netware. your netware drives will start ABOVE the last XNS drive. I have set this up to work both with XNS and with 3com 3+. Email me if you need anymore details.
kenh@techbook.com (Ken Haynes) (01/19/91)
In article <1991Jan17.202331.1@maven.u.washington.edu> kung@maven.u.washington.edu writes: >I am interested in linking XNS based xerox workstations together with Novell >Based PC's. The most important service for me is Email services. The file >services or printer services are secondary. Interesting mix huh? What's even more interesting is that the Novell IPX/SPX protocol is a variation/modification of the XNS protocol from XEROX! I've never heard of this mix before, and although the lower layers are cousins, the upper layers of the protocols are different enough to prevent a seamless connection. Have you checked with Novell re: an XNS protocol stack? Ken -- ****************************************************************************** Network Support Services: Ken Haynes, Certified Netware Engineer
sph@logitek.co.uk (Stephen Hope) (01/23/91)
vdra_ltd@uhura.cc.rochester.edu (Valerie Drake) writes: >In <1991Jan17.202331.1@maven.u.washington.edu> kung@maven.u.washington.edu writes: >>I am interested in linking XNS based xerox workstations together with Novell >>Based PC's. The most important service for me is Email services. The file >>services or printer services are secondary. Interesting mix huh? >>Darwei Kung >>kung@max.u.washington.edu >Although the two operating systems are basically incompatible, you can set >up a workstation which will talk to and be logged in on both. The workstation >needs to have 2 network boards in it, configured for different interrupts and >memory addresses. Configure the drivers for each net os to the different >interrupts. For instance if you have an Enet card set for int 4 and one for >int 5, configure the IPX file for int 4, and the xns enet.sys driver for >int 5. Load the XNS drivers and login to XNS first, then load ipx and >net3 and login to Netware. your netware drives will start ABOVE the last >XNS drive. >I have set this up to work both with XNS and with 3com 3+. >Email me if you need anymore details. The above scenario is not the only way to do this. 3Com 3+Open (which supports XNS and other protocols) can also support Novell server connections from the same PC, sharing the same LAN card. 3Com have written an ipx to NDIS driver for this. It will work on DOS PCs with 3+Open 1.1 Our support people (who have to handle both types of LAN software) use this with 3Com Ethernet cards internally. Just as a matter of interest, the same systems also support TCP/IP, using 3Coms PCS/TCP. There can be problems with the amount of free RAM available, but the Novell and TCP/IP protocols stacks can be unloaded when not required.
martino@logitek.co.uk (Martin O'Nions) (01/28/91)
sph@logitek.co.uk (Stephen Hope) writes: >Our support people (who have to handle both types of LAN software) use this >with 3Com Ethernet cards internally. Just as a matter of interest, the same >systems also support TCP/IP, using 3Coms PCS/TCP. O.K. For the benefit of those of you who spotted our deliberate mistake, we do of course use 3+ Open TCP, which works with DPA and the NDIS drivers, rather than PCS/TCP which was designed for use with the older MINDS drivers. It does work however, honest! (this posting was produced from a telnet session using 3+ Open TCP over 3+ Open connectivity for NetWare (IPX stack) over XNS). Martin -- DISCLAIMER: All My Own Work (Unless stated otherwise) -------------------------------------------------------------------------- Martin O'Nions Logitek Group Support martino@logitek.co.uk -------------------------------------------------------------------------- Down the drinking well / Which the plumber built her Aunt Mathilda fell / - We should buy a filter.... (Harry Graham - Ruthless Rhymes for Heartless Homes)