I'll go out on a limb and tell you to contact Bob Kivey directly, and he'll
arrange with Peter to get it working for you. We have had an incredible
time making server port access work, and Peter has done an awesome job in
working with us, building new versions of Radius 3 to get it solved.
Director of Operations
BOSS Internet Group
At 08:19 AM 1/26/2000 -0600, you wrote:
>I guess I will keep posting this until I'm either kicked off this list or it
>I can't get the Server Port Access restrictions to work with RadiusNT 3.0.
>Although I have enabled this feature on the RadiusNT Administration
>"Advanced" tab (and saved from File, save), added the servers in the Emerald
>Admin..RadiusNT Button...Server tab with "Name" (Server), "IP Address", and
>"Secret" all correctly and set up the ports correctly (Re-port and save to
>automatically re-port). Also set up in the Emerald Admin...RadiusNT
>Button....Server Port Access tab, the specific server to allow access to the
>NAS ports. I have verified that they are listed in the ServerPort table and
>ServerAccess Table, and have restarted RadiusNT. All I get then from a
>radius -x15 window is the following using radlogin:
>radrecv: Request from host 7f000001 (localhost) code=1, id=154, length=83
> User-Name = "joeblow"
> NAS-Identifier = 127.0.0.1
> NAS-Identifier = "Localhost"
> NAS-Port = 0
> Caller-Id = "1115551212"
> Password = "\361\240\232$w|\315E\022\227C'\342\306\367i"
>Checking for duplicate logins.
>Checking for port access.
>The request simply times out. The exact same setup worked perfect with 2.5
>BTW - I also ran the emer25_up.sql upgrade without error.
>Network Administration Staff
>North Central Kansas Community Network
>For more information about this list (including removal) go to:
For more information about this list (including removal) go to: