sylvia@chopin.udel.edu (Sylvia M Berta) (05/15/91)
Hi ... we've got a small problem right now, and I'm hoping someone can offer a solution. We've been running a 2.15c network since last Fall, supporting about 60 IBM/IBM compatibles, and 16 Mac II's, all on ether. We do have LocalTalk set up for two printers for the Mac side, and have two HP laserjets on the DOS side. We had no major problems last semester. Recently we started maxing out the number of files open, at which time all printing on both sides (DOS and Mac) would hang/stall/bomb, and the network would essentially die. During the month prior to this happening, the server (PS/2 model 80) was crashing intermittantly, giving us a GENERAL PROTECTION ERROR. We regen'ed the OS, added more memory to the server, replaced the mother board, etc. and we haven't had that error message recently. But we are now without our Mac printing. Running Mac 2.0 VAP, we can see the queues from the Novell side (PCONSOLE and from the console)...it tells us that the Apple printer queue is currently on-line, servicing 1 print queue, but from the Chooser, no printers show up. As I said, the printing was working fine until about a week ago. Now it's the pits! 8-) Any help would be welcome. Thanks in advance ... Syl Berta
dd@intuit.intuit.COM (David DelGreco) (05/17/91)
Try MACSETUP. You need to *publish* the the queues, then reboot the server. You're probably running low on memory. It's been happening to us for months. We are almost done setting up a new server to deal with the problem. In FCONSOLE (s<enter>s<enter>), look at Dynamic Memory 1. On our server the max is 18,000 something. When the current goes over about 16,500 for any length of time, the Mac VAP seems to just melt right out of the server. First the print queues go, then Macs can't log into the network. Later it will start affecting the PCs, but we usually catch it way before then. I could be wrong about your case, but this is what happened to us. dd
dd@intuit.intuit.COM (David DelGreco) (05/17/91)
Try MACSETUP. You need to *publish* the the queues, then reboot the server. You're probably running low on memory. It's been happening to us for months. We are almost done setting up a new server to deal with the problem. In FCONSOLE (s<enter>s<enter>), look at Dynamic Memory 1. On our server the max is 18,000 something. When the current goes over about 16,500 for any length of time, the Mac VAP seems to just melt right out of the server. First the print queues go, then Macs can't log into the network. Later it will start affecting the PCs, but we usually catch it way before then. I could be wrong about your case, but this is what happened to us. dd