qiming@earth.unsw.oz (Qiming Zhou) (09/26/90)
Hello, I think this topic has been covered before but I have not kept the track. I am currently managing a PC-based LAN using Novell NetWare as well as some Sun workstations networed via TCP/IP. I have tried for quite a long time to make the PC LAN talk to TCP/IP. I know that there is some commercial software such as FTP's PC/TCP which can do this but I cannot really spend a lot of money for this. Then the question is the PD products such as NCSA's TCP/IP (or clones?). I have gone through a lot of information about this and finally worked out that if I want to make things working smoonthly I have to change the network protocol from Novell's 802.3 to 8137 using the program ECONFIG. I have tried and everything appears to work. Here is the problem. After I have modified NET$OS.EXE using ECONFIG, I can no longer communicate with other Novell servers on the campus (there are about 15 of them). After reading through the document I relise that every server has to be ECONFIGed and every workstation has to run packet driver - this is totally out of question here, unfortunately. Then I started to look through some old news and documents and discovered someone else also had similar problem and it appears that there are some solutions for this, but I do not have the clue where can I get help. Could anyone help me to solve the problem? Is there any packet drivers that support both 802.3 and 8137 packet protocols? Any information is greatly appreciated. Our system configuations: Thin Ethernet Cables IBM-PC, AT, 386s Server is a AT compatible 386 with a NE2000 Ethernet card Most workstations use Racal NI5210, NI6510 Ethernet cards Some workstations use Western Digital WD8003E Ethernet cards Some laptop computers (Toshiba) use Toshiba Ethernet cards We are running Novell Advanced NetWare v2.15 on the server v3.01 on workstations. Thanks in advance. Qiming Zhou Phone: 61-2-697-4400 School of Geography FAX: 61-2-313-7878 The University of New South Wales Internet: qiming@earth.gas.unsw.OZ.AU
jbreeden@netcom.UUCP (John Breeden) (09/27/90)
In article <862@usage.csd.unsw.oz.au> qiming@earth.unsw.oz (Qiming Zhou) writes: > >Here is the problem. After I have modified NET$OS.EXE using ECONFIG, I >can no longer communicate with other Novell servers on the campus (there >are about 15 of them). After reading through the document I relise that >every server has to be ECONFIGed and every workstation has to run packet >driver - this is totally out of question here, unfortunately. > >Then I started to look through some old news and documents and discovered >someone else also had similar problem and it appears that there are some >solutions for this, but I do not have the clue where can I get help. > >Could anyone help me to solve the problem? Is there any packet drivers >that support both 802.3 and 8137 packet protocols? Any information is >greatly appreciated. > The current packet drivers from Clarkson (release 7) support either DIX or 802.3 via a command line switch. I was always under the impression that if you mixed other 802.3 traffic with 802.3/Netware on the same wire that you would/could crash Novell servers, thus the need to run Netware in DIX. Something to do with Novell's weird handling of the 802.2 header (and how their stack handled it). You could always stick another card in your server, configure one card for DIX, the other for 802.3 and connect the 802.3 side to your other novell servers. -- John Robert Breeden, netcom!jbreeden@apple.com, apple!netcom!jbreeden, ATTMAIL:!jbreeden ------------------------------------------------------------------- "The nice thing about standards is that you have so many to choose from. If you don't like any of them, you just wait for next year's model."
nelson@sun.soe.clarkson.edu (Russ Nelson) (09/28/90)
In article <862@usage.csd.unsw.oz.au> qiming@earth.unsw.oz (Qiming Zhou) writes:
Could anyone help me to solve the problem? Is there any packet drivers
that support both 802.3 and 8137 packet protocols? Any information is
greatly appreciated.
Yes, the 7.x packet drivers have a switch that converts from one to the
other.
Server is a AT compatible 386 with a NE2000 Ethernet card
Most workstations use Racal NI5210, NI6510 Ethernet cards
Some workstations use Western Digital WD8003E Ethernet cards
Some laptop computers (Toshiba) use Toshiba Ethernet cards
We have packet drivers for all of the above except the Toshiba, unless
the Toshiba Ethernet card is compatible with something else (ne1000?).
The Clarkson packet driver collection
Availability
The Clarkson collection of packet drivers is available by FTP, by
archive-server, and by modem. They come in two flavors -- executables
only (drivers.arc), and source+executables (driverss.arc). All of the
following instructions apply to both drivers.arc and driverss.arc.
Mail:
I distribute the packet drivers on a 1.2 MB 5.25" disk, or a 720K 3.5"
disk. You can send me a check for $20, or you can send me a purchse
order and I will bill you for $22. NY residents add 7% sales tax,
overseas orders add $3 for shipping. If you send a check, please be
sure it is in US dollars -- the bank charges me $15 to convert checks
drawn in foreign currencies.
Russell Nelson
11 Grant St.
Potsdam, NY 13676
FTP:
sun.soe.clarkson.edu:/pub/ka9q/drivers.arc
grape.ecs.clarkson.edu:/e/tcpip/drivers.arc
Archive-server:
Send mail to archive-server@sun.soe.clarkson.edu and put the following
command as the body of your message:
help
This will send you a help message. Reading this help message will tell
you how to fetch the packet drivers.
Modem:
Call the Clarkson Heath User's Group's BBS: (315)268-6667, 8N1,
1200/2400 Baud, 24 hours. Change to file area 24 and download drivers.arc.
--
--russ (nelson@clutx [.bitnet | .clarkson.edu]) Russ.Nelson@$315.268.6667
It's better to get mugged than to live a life of fear -- Freeman Dyson