hhg1@GTE.COM (Hallett German) (11/22/89)
A user's PC-NFS was working fine until they installed an INTEL Inboard. Although it initially worked, it has been troublesome since. It appears to take forever on the NET YPSET and says that x is not a YP server on domain yyy. No other PC_NFS machine has it. A colleague says that it appears that the drivers higher than the IP level are not working. I originally thought Interrupt contention but it appears to be something else like memory conflict. Has anyone else had this problem? I know it is not the network and the connection to the terminal server is ok. Any and all suggestions would be welcomed. Hal German GTE Labs 617-466-2290 NESUG BBS 508-263-1499 M&tu 7:30 am-6:30 pm
bryan@intvax.UUCP (Jon R Bryan) (11/22/89)
From article <7833@bunny.GTE.COM>, by hhg1@GTE.COM (Hallett German): > A user's PC-NFS was working fine until they installed an INTEL Inboard. > Although it initially worked, it has been troublesome since. > Is this Inboard in an XT or an AT? I have one in my old XT and run PC-NFS with no trouble. In fact, I even load some of the drivers in high RAM using Quarterdeck's QEMM386 memory manager. I set up the 3Com 3C503 Ethernet card for IRQ2. The only problem I've run into is that Telnet won't run within Desqview (but Mail will...go figure).