I think what you are looking for is to turn on shared profiles which will enable multiple sessions up on the same user-id it's under IP-GLOBAL : tnt>set shared-prof? shared-prof: When TRUE multiple users may share a connection profile, as long as IP addresses are not duplicated. Boolean field, 'no' or 'yes' tnt1.> -- ------ Jason Nealis Sr. Director Internet Operations RCN (NASDAQ) RCNC On Wed, Jul 26, 2000 at 12:50:52AM +0100, James Courtier-Dutton stated > Hello > >From the commands.html manual page: > LAN security error: > A PPP session has failed authentication, another session by the same name > already exists, or remote authentication timed out. > I don't know if you are allowed multiple logins with the same name or not. I > heard there might be a switch setting in TAOS to turn off the name checking, > but I can't remember it, sorry! > Cheers > James > > This might help. I am not sure how accurate it will be. > c101 p67 > The MAX unit successfully negotiated LCP and authentication > with the dialin client. The MAX unit disconnected the call during > IP routing (IPCP) negotiation, which typically occurs because the > computer's IP address (configured on the MAX unit) does not > match the configuration of the IP address of the dialin client or > because the MAX unit has no available IP address from its pool to > assign to dialin client. > 45c 60p > While the session was active, the MAX unit received a Terminate > Request from the user's PPP application. Typically, Typically, the > call was a successful session., and the user has disconnected the > session from the dialin client's PPP application. > 47c 63p > The MAX unit successfully completed LCP negotiation and > authentication. The configuration of the user's PPP application did > not match the MAX unit's PPP configuration. The two devices > could not successfully negotiate any Network Control Protocols > (NCPs) (IP routing, IPX routing, AppleTalk routing, or bridging). > Both the MAX unit and the dialin client must be configured to > successfully negotiate at least one NCP. > > > ----- Original Message ----- > From: "Bill Merrill" <wyrm at shore.net> > To: <ascend-users at max.bungi.com> > Sent: Tuesday, July 25, 2000 6:26 PM > Subject: (ASCEND) Multiple connections using same username > > > > Hello once again. I am hoping someone will be able to help. We have users > > that can get a dynamically assigned IP address, and hence can use the same > > username to connect with multiple computers. We keep track of usage, so > > that is not a problem. The problem lies in that since switching over to > > the TNT, multiple connections with the same username are no longer > > possible. The Livingston Portmasters do it without a problem. I am > > including some info to maybe help describe the issue: > > > > Model: MaxTNT-2AC > > Rev: 7.2.3 > > Radius: Merit > > > > Jul 25 10:29:24 cmbr1-tnt.wharf.shore.net 1/9: [1/9/1/0] > > STOP: 'nqrdial at shore.net'; cause 101.; progress 67.; host 209.192.186.231 > > [MBID 1094; ->1980] [nqrdial at shore.net] > > Jul 25 10:30:02 cmbr1-tnt.wharf.shore.net 1/9: [1/9/38/0] LAN security > > error, nqrdial at shore.net [MBID 1546; ->1980] [nqrdial at shore.net] > > Jul 25 10:30:04 cmbr1-tnt.wharf.shore.net 1/9: [1/9/38/0] > > STOP: 'nqrdial at shore.net'; cause 101.; progress 67.; host 209.192.186.235 > > [MBID 1546; ->1980] [nqrdial at shore.net] > > Jul 25 10:30:37 cmbr1-tnt.wharf.shore.net 1/9: [1/9/34/0] LAN security > > error, nqrdial at shore.net [MBID 410; ->1980] [nqrdial at shore.net] > > Jul 25 10:30:40 cmbr1-tnt.wharf.shore.net 1/9: [1/9/34/0] > > STOP: 'nqrdial at shore.net'; cause 101.; progress 67.; host 209.192.186.243 > > [MBID 410; ->1980] [nqrdial at shore.net] > > Jul 25 10:31:06 cmbr1-tnt.wharf.shore.net 1/5: [1/5/40/0] LAN security > > error, nqrdial at shore.net [MBID 260; ->1980] [nqrdial at shore.net] > > Jul 25 10:31:08 cmbr1-tnt.wharf.shore.net 1/5: [1/5/40/0] > > STOP: 'nqrdial at shore.net'; cause 101.; progress 67.; host 209.192.186.247 > > [MBID 260; ->1980] [nqrdial at shore.net] > > Jul 25 10:32:30 cmbr1-tnt.wharf.shore.net 1/7: [1/7/44/0] > > STOP: 'nqrdial at shore.net'; cause 45.; progress 60.; host 209.192.186.193 > > [MBID 149; ->1980] [nqrdial at shore.net] Jul 25 12:57:26 > > cmbr1-tnt.wharf.shore.net 1/6: [1/6/13/0] > > STOP: 'nqrdial at shore.net'; cause 47.; progress 63.; host 209.192.186.97 > > [MBID 618; ->1980] [nqrdial at shore.net] > > Jul 25 13:02:30 cmbr1-tnt.wharf.shore.net 1/6: [1/6/13/0] > > STOP: 'nqrdial at shore.net'; cause 11.; progress 60.; host 209.192.186.107 > > [MBID 232; ->1980] [nqrdial at shore.net] > > Jul 25 13:14:16 cmbr1-tnt.wharf.shore.net 1/7: [1/7/29/0] > > STOP: 'nqrdial at shore.net'; cause 45.; progress 60.; host 209.192.186.170 > > [MBID 349; ->1980] [nqrdial at shore.net] > > Jul 25 13:15:33 cmbr1-tnt.wharf.shore.net 1/10: [1/10/31/0] > > STOP: 'nqrdial at shore.net'; cause 45.; progress 60.; host 209.192.186.224 > > [MBID 1259; ->1980] [nqrdial at shore.net] > > > > I know the cause 45; progress 60 are regular disconnects. The others are > > just an example of this particular users issue. I appreciate any help or > > tips you might be able to share. > > > > > > Regards, > > > > Bill Merrill, CCNA > > Network Operations > > Shore.Net - A PRIMUS Company > > > > ++ Ascend Users Mailing List ++ > > To unsubscribe: send unsubscribe to ascend-users-request at bungi.com > > To get FAQ'd: <http://www.nealis.net/ascend/faq> > > ++ Ascend Users Mailing List ++ > To unsubscribe: send unsubscribe to ascend-users-request at bungi.com > To get FAQ'd: <http://www.nealis.net/ascend/faq> -- ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request at bungi.com To get FAQ'd: <http://www.nealis.net/ascend/faq>