Article View: comp.dcom.lans.ethernet
Article #1009Problem with BYU/IPX over NDIS
From: Tan Sen Teck
Date: Thu, 21 Jan 1993 04:34
Date: Thu, 21 Jan 1993 04:34
43 lines
2740 bytes
2740 bytes
Hope I've got the right newsgroup, folks.
I'm currently trying to setup a netware 3.11 network using FTP Software's
PC/TCP v2.11 with generic packet driver ethdrv and BYU's IPX implementation
over SMC's NDIS device driver. The setup consists of the following software
and their respective version numbers:
Protman.sys v1.1 - Protocol Manager from Microsoft
SMCMAC.DOS v1.19 - SMC's NDIS ethernet adapter driver
dis_pkt.gup v1.30 - FTP Software's mac/dis Packet Driver Convertor
netbind.exe v1.1 - Microsoft's netbind program
byuipx.com - IPX/SPX v3.10 with BYU Packet Driver v2.01
netx.com v3.26 - Netware shell
ethdrv.exe v2.11 - FTP Software's generic TCP kernal
The whole setup on the client workstation works fine. I can communicate
with my netware server and UNIX hosts concurrently from within Windows 3.1.
Trouble starts when the network utilization goes up to about 30-35 percent.
I start to get Network Error on Server; Error sending on network. Abort,
Retry? messages while operating from DOS (Windows not loaded) and complete
hanging of the station when operating from Windows 3.1. It got so bad at
certain times that the station is not even able to bootup onto the
netware network. I've got another station experiencing the same problem,
but after changing the setup to just plain ipx.com without the BYU/NDIS
stuff, the station works albeit slightly slower, when traffic is at 30
percent. At one time I had both stations running side-by-side. The one
with the straight ipx.com was chugging away merrily, whilst the BYU/IPX
station was hanging all the time. Both stations run fine when network
utilization is at about 10-20 percent. I'm running coax thin ethernet
RG58A/U Type cable segments with Synoptics Repeaters and Cisco Routers.
All the stations and server are on the same segment. The heavy traffic
is usually generated by our Sun Workstations in that segment.
Has anyone out there come across this problem. Is there a FAQ site
I can look up for answers? I need help quick! The new network is
scheduled to be up in the next couple of weeks.
Mr. Tan Sen Teck.
Analyst/Programmer
Institute of Systems Science
National University of Singapore.
Internet: senteck@iss.nus.sg
Technical Details
Message-ID:
<1993Jan21.043408.3154@nuscc.nus.sg>Path:
arc1-ca.pugleaf.net!sparky!uunet!spool.mu.edu!yale.edu!newsserver.jvnc.net!newsserver.technet.sg!nuscc!senteckShow Full Headers
Complete Article Headers
Newsgroups: comp.dcom.lans.ethernet Path: arc1-ca.pugleaf.net!sparky!uunet!spool.mu.edu!yale.edu!newsserver.jvnc.net!newsserver.technet.sg!nuscc!senteck From: senteck@iss.nus.sg (Tan Sen Teck) Subject: Problem with BYU/IPX over NDIS Message-ID: <1993Jan21.043408.3154@nuscc.nus.sg> Sender: usenet@nuscc.nus.sg Organization: Institute of Systems Science, NUS, Singapore X-Newsreader: Tin 1.1 PL4 Date: Thu, 21 Jan 1993 04:34:08 GMT Lines: 44