Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uwm.edu!bionet!ames!excelan!keith From: keith@excelan.COM (Keith Brown) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: NOVELL/TCP-IP/PACKET DRIVER : How do you get them to work together? Keywords: NOVELL IPX Message-ID: <1532@excelan.COM> Date: 12 Jul 90 04:18:46 GMT References: <475@usperb.Dayton.NCR.COM> Sender: news@excelan.COM Reply-To: keith@ca.excelan.com (Keith Brown) Distribution: usa Organization: Excelan, A Novell Co., San Jose, CA. Lines: 72 In article <475@usperb.Dayton.NCR.COM> daved@usperb.Dayton.NCR.COM (Dave Dresselhouse) writes: > >My problem/question is this: > I've not yet modified the Server to look at the 8137 format packets, > but when I invoke NET3 on the workstation after loading the Packet Driver, > PC/TCP and the new IPX, the PC just hangs. No "Can't connect" message. Well, NET3 takes a little time to give up hope of finding a file server but it should return the machine to you eventually. Before loading IPX/NET3, make sure PCTCP is working. That will tell you if you've loaded the PD up correctly for your board configuration. > > If I modify the Server to look at 8137 packets, and the new IPX/NET3 > combination still doesn't work, will I be able to connect to the Server > from an 802.3 workstation and reset it to look at 802.3 again? No. But read on..... > (I have > this fear that once I modify the server for 8137 and the new workstation > software doesn't work, I'll be locked out of the server with no way > to put it back the way it was). Never fear. All is redeemable! At least it should be. I'm assuming that you've been using an IPX.COM that has been linked to go straight to your ethernet hardware until now. This IPX.COM is likely to be "econfig"able (check, some aren't! If this is an NE1000 and you've been using an IPX.COM linked with our driver though, it is!) so if you econfig your server and the PD shell doesn't work at the workstation, you can revert to your old IPX.COM in an "econfig"d incarnation to connect to your server and set things back the way they were. Assuming your server has a single ethernet card installed, configured as LAN A, log into it from a DOS workstation as supervisor and do something like this: F:\SYSTEM> copy net$os.exe net$os.old - Better safe than sorry! F:\SYSTEM> econfig net$os.exe a:e 8137 Reboot the server and try your PD IPX.COM and NET3 at a workstation. If it all goes horribly wrong, take your old, straight to the metal IPX.COM and: C:\BIN> copy IPX.COM IPXETH.COM C:\BIN> econfig IPXETH.COM shell:e 8137 <- *CHECK THIS WORKS FIRST (BEFORE MESSING WITH YOUR SERVER)* C:\BIN> IPXETH C:\BIN> NET3 F:\SYSTEM> copy net$os.old net$os.exe F:\SYSTEM> econfig net$os.exe a:n Remember to revert to the non econfig'd IPX.COM at the workstation too! > >Has anyone been successful with this? Yes. Me... I thought this was worth posting as "econfig" has a tendancy to confuse folk and this might kill a few birds with one stone with regards to it's usage. Keith ---------------------------------------------------------------------------- Keith Brown Phone: (408) 473 8308 Novell San Jose Development Centre Fax: (408) 433 0775 San Jose, California 95131 Net: keith@novell.COM ----------------------------------------------------------------------------