Thank you. I wasn't aware of them and it looks like they did the trick.
Doesn't seem like this would have been too hard for IEA to respond on the
list. Again, thank you.
Network Administration Staff
North Central Kansas Community Network
----- Original Message -----
From: Marshall Morgan <email@example.com>
Sent: Wednesday, January 26, 2000 8:52 AM
Subject: RE: [RadiusNT] ??? Hmm, Guess I will just keep posting this...
> Did you download the upgrade/patch for 3.0?
> Marshall Morgan
> Internet Doorway, Inc. (aka NETDOOR)
> > -----Original Message-----
> > From: firstname.lastname@example.org
> > [mailto:email@example.com]On Behalf Of Todd K. Tuttle
> > Sent: Wednesday, January 26, 2000 8:17 AM
> > To: RadiusNT ListServ
> > Subject: [RadiusNT] ??? Hmm, Guess I will just keep posting this...
> > I guess I will keep posting this until I'm either kicked off this list
> > gets answered...
> > I can't get the Server Port Access restrictions to work with RadiusNT
> > Although I have enabled this feature on the RadiusNT Administration
> > "Advanced" tab (and saved from File, save), added the servers in the
> > Admin..RadiusNT Button...Server tab with "Name" (Server), "IP Address",
> > "Secret" all correctly and set up the ports correctly (Re-port and save
> > automatically re-port). Also set up in the Emerald Admin...RadiusNT
> > Button....Server Port Access tab, the specific server to allow access to
> > NAS ports. I have verified that they are listed in the ServerPort table
> > 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,
> > 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
> > Any clues?
> > BTW - I also ran the emer25_up.sql upgrade without error.
For more information about this list (including removal) go to: