gold%smaug.decnet%mghccc@HUSC6.BITNET (SMAUG::GOLD) (01/12/90)
We are in the process of setting up a Novell network (Advanced Netware 286) in our department. There are a couple of questions that I was hoping could be answered by the experienced users on the Net. 1) While there are probably a lot of quality Mail packages available for Novell, I was wondering if there were one or two that are more useful (and recognize the commands) for sending letters on BITNET, INTERNET, ARPANET, etc.). Please let me know of your positive and/or negative experiences in this regard. 2) I would like to eventually be able to System Manage several Novell Networks from a remote PC during work hours and "off" hours. These Novell networks will be at different locations. From past letters that I've seen to NOVELL@SUVM, people seem to say that it is better to attach the modem in a Workstation in the local network as opposed to the File Server. I can forsee two problems with this solution (although maybe I'm overlooking something). a) When I want to communicate remotely during working hours, the Workstation with the modem will have to be free (or we will have to buy a dedicated Workstation with an extremely limited budget). What if I log on remotly and the Workstation owner then needs to use the Workstation? I will not have my own Workstation at each LAN that I am System Managing. b) When I want to communicate remotely during "off" hours (say Midnight), the Workstation will have to have been left on all night (not just the File Server). I would have to hope that the Workstation owner remembered to leave the Workstation turned on. Are there any hardware problems with leaving the File Server and/or Workstation on 24 hours per day (with Screen Saver software, of course)? It seems that it makes more sense to have a modem in the File Server (at least, in theory). As this theory goes (or is it a fantasy?), a Workstation would not be tied up when I connect to this LAN from a remote source. Also, any User on this LAN would (should) be able to use this modem from their Workstation (one at a time, of course). As you can see, I obviously am not very familiar with Novell. There must be some points that I'm missing. I would be very greatful to anyone that can shed some light on this subject! Thanks in advance, - Mark Gold INTERNET: gold%smaug.decnet@mghccc.harvard.edu
gold%smaug.decnet%mghccc@HUSC6.BITNET (SMAUG::GOLD) (01/16/90)
We are in the process of setting up a Novell network (Advanced Netware 286) in our department. There are a couple of questions that I was hoping could be answered by the experienced users on the Net. 1) While there are probably a lot of quality Mail packages available for Novell, I was wondering if there were one or two that are more useful (and recognize the commands) for sending letters on BITNET, INTERNET, ARPANET, etc.). Please let me know of your positive and/or negative experiences in this regard. 2) I would like to eventually be able to System Manage several Novell Networks from a remote PC during work hours and "off" hours. These Novell networks will be at different locations. From past letters that I've seen to NOVELL@SUVM, people seem to say that it is better to attach the modem in a Workstation in the local network as opposed to the File Server. I can forsee two problems with this solution (although maybe I'm overlooking something). a) When I want to communicate remotely during working hours, the Workstation with the modem will have to be free (or we will have to buy a dedicated Workstation with an extremely limited budget). What if I log on remotly and the Workstation owner then needs to use the Workstation? I will not have my own Workstation at each LAN that I am System Managing. b) When I want to communicate remotely during "off" hours (say Midnight), the Workstation will have to have been left on all night (not just the File Server). I would have to hope that the Workstation owner remembered to leave the Workstation turned on. Are there any hardware problems with leaving the File Server and/or Workstation on 24 hours per day (with Screen Saver software, of course)? It seems that it makes more sense to have a modem in the File Server (at least, in theory). As this theory goes (or is it a fantasy?), a Workstation would not be tied up when I connect to this LAN from a remote source. Also, any User on this LAN would (should) be able to use this modem from their Workstation (one at a time, of course). As you can see, I obviously am not very familiar with Novell. There must be some points that I'm missing. I would be very greatful to anyone that can shed some light on this subject! Thanks in advance, - Mark Gold INTERNET: gold%smaug.decnet@mghccc.harvard.edu