Dear Fellow Platypus & Radiator Users,
Sorry for the cross post but I am really at wits end and not sure what
to do.
Here's the deal, We have 2 RADIUS servers running, a primary
and a secondary. Our Primary RADIUS server is Radiator running on an NT
server along side Platypus. Our secondary Radius server is Livingston
Radius version 2.1 running on a BSDI 3.1 Unix box.
Our terminal or RAS servers are all Livingston/Lucent PM3's running code
3.8c2. We have 3 in the main office that support 28.8 through ISDN
connections and all have PRI lines from Ameritech. The 4th is at a
remote office but has a channalized T1 (from Sprint) so it only supports
connection up to 56k.
With the above setup we are seeing ALOT of customers not being
disconnected prorperly.....on all 4 systems. For example, A customer
will call in, stay connected for 30 minutes and then terminate the call.
The Portmaster however is still showing them connected. Unless we go
out and manually reset the lines the "ghost users" will stay connected
it seems indefinatly. As a test, I left one user connected I knew had
terminated the session because I phoned them. After 2 days they were
still connected! The only we thing we have not tested is if a session
is still active and the user dials back in, what happens.....we are not
sure.
This had been going on for several days since we installed Radiator.
Since it was getting to hard to track we switched the Radius Servers so
that the Unix box was now the primary and Radiator was the secondary.
We rebooted all the PM's to make sure there were no "ghost sessions"
and waited to see what would happend. After running for 2 days
everyone was being disconnected properly so to make sure I was not
insane I switched back, making Radiator the Primary and Unix the
secondary and we are back to the same problem. We have been running
with Radiator as the primary since Thursday. It is Sunday morning and
we have several users that have been connected 1 to 2 days. This is not
a common occurence for most of these people as they are low end users
averaging 25 to 30 hours a month. Yes, we have our abusers but these
"ghost sessions" seem to be happening to almost all of our customers
I think I can rule out the phone lines since it is happening on all the
lines and as stated, 3 are from Ameritech and 1 is from Sprint.
I am not sure if the problem is with my Radiator cfg file or something
in Platypus. If anyone has any hints or ideas I will love to hear them.
Also, can someone share the .cfg file with me ? It is possible I am
missing something in there......right now I am using <AuthBy Emerald>
and have the RadiusNT SQL hooks in Platypus.
What I don't undersand is why or how are these sessions are staying
active ? If a user on the other end disconnects the call I would think
the Portmasters wouldn't care about Radiator or Platypus and it would
just terminate the session and clear the line.
Again, any hints, tips, pointers, help, etc. would be greatly
appreciated.
Thank You,
Todd Knaus
President
CISNet, Inc.
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
