The 4 users that are affected are using:
1. Windows 3.1 with Netscape's dialer
2. Windows NT (3.51 I think) using some form of modem pool and a
script I think.
3. Macintosh using some form of script with MacTCP 2.0.6, MacPPP
2.2.0 and MacOS 7.5.5
4. Forget what the other user is using.
I had realized after a while (before finding out what each user was using)
that the common factor was the fact that these users were either using some
form of script or non "automatic" method of obtaining their PPP
connections.
I tested this by logging on from my Win95 machine after "opening a terminal
window after dialing" and manually logging in. Sure enough, my info was
missing for that call as well.
After some more testing, I went into the Max into Terminal Server mode and
typed in "show users" and it displayed the IP address for the users who
aren't showing one in Emerald.
I don't know if RadiusNT (in my case, it's still .52) has anything to do
with it or not, but as I said, the first time this problem popped up was
immediately after upgrading the Max to 5.0A. The callers experience no
problems apparently.
Josh Hillman
hillman@talstar.com
> > I was just wondering if there is a reason that clients that log in
> > with windows 3.1 using trumpet etc, do not register an IP address in
> > the online tab in emerald. Is this normal, or am I missing a
> > setting?
>
> I believe there is a problem with receiving the Framed-Address
> in accounting when the login was manual entered. If your
> trumpet is designed for scription, trying ripping out the bottom
> of the script which does the authentication, and enabling
> PAP and see if it changes the behavior.