Path: utzoo!attcan!uunet!husc6!bloom-beacon!bu-cs!purdue!decwrl!labrea!Portia!Jessica!morgan From: morgan@Jessica.stanford.edu (RL "Bob" Morgan) Newsgroups: comp.dcom.lans Subject: Re: 3Com's 3+Share v.1.3.1 ?s Message-ID: <1888@Portia.Stanford.EDU> Date: 27 Apr 89 23:09:37 GMT References: <425@uncmed.med.unc.edu> Sender: USENET News System Reply-To: morgan@Jessica.stanford.edu (RL "Bob" Morgan) Organization: Stanford University Lines: 21 In article <425@uncmed.med.unc.edu> goldston@uncmed.med.unc.edu () writes: >I recently received the upgrade from 3+Share v.1.2.1 to 3+Share v.1.3.1. I >heard a rumor several months ago that the latest version (1.3.1) would sup- >port multiple name servers on the same network. Is this true? Has anyone >tried it? How well did it work? Thanks. As far as I know this is *not* true. We've been bugging 3Com for quite a while to give us this capability, and it's always too expensive or too much trouble or there's a new version coming or ... I know they did this for Hughes in Southern Calif initially, so 3Plus could be used on their very extended LAN, but it seems that they (3Com) really don't want anyone else to have it. My impression is that they want to use this as a ploy to encourage people to move to 3+open, since it presumably will not have this limitation. (My impression is that the current 3+open doesn't use a Name service at all but a PC-LAN-style distributed naming scheme.) - RL "Bob" Morgan Networking Systems Stanford