Re: IEA RadiusNT + PM3 question?

Zak Wolfinger ( (no email) )
Tue, 31 Mar 1998 17:43:26 -0500

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Previous message: Dale E. Reed Jr.: "Re: IEA RadiusNT + PM3 question?"
Next message: Zak Wolfinger: "Re: IEA RadiusNT + PM3 question?"
Maybe in reply to: Zak Wolfinger: "IEA RadiusNT + PM3 question?"
Next in thread: Zak Wolfinger: "Re: IEA RadiusNT + PM3 question?"

This is a multi-part message in MIME format.

------=_NextPart_000_0009_01BD5CCC.821D8B60
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Ok you asked for it! Attached is the output of ipconfig
/all on the NT server. Here is the configuration of the
PM3:

Ether0 = 208.209.5.65/26
Gateway = 208.209.5.130
Authentic = 206.64.229.11
Alternate = 206.64.229.19
Accounting = 206.64.229.11
Accounting 2 = 206.64.229.19

The NT server is also our NTMail server so it has a ton (a
whole class C) of IP's on it. Basically here is the
configuration:

Main IP address assigned to the NIC = 206.64.229.11 Mask
255.255.255.0 Gateway 206.64.229.1
Secondary IP's assigned via the Advanced section =
208.237.130.2 thru 208.237.130.254 mask 255.255.255.0
gateway 208.237.130.1.

And to summerize the problem, the PM3 always sends the
authentication request to 206.64.229.11 but sometimes the
ack comes back from 208.237.130.2 (it is always either
206.64.229.11 or 208.237.130.2 - never any other IP).

I have temporarily worked around the problem by assigning
the alternate and accounting2 to 208.237.130.2, but this
completely throws out the idea of a backup radius server.

-----Original Message-----
From: Dale E. Reed Jr. <daler@iea-software.com>
To: ntisp@emerald.iea.com <ntisp@emerald.iea.com>
Date: Tuesday, March 31, 1998 5:02 PM
Subject: Re: IEA RadiusNT + PM3 question?

Zak Wolfinger wrote:
>
> PM3-2 in a remote POP.
> Authenticating with Radius against IEA's Radius NT 1.16.60
>
> Authentication requests only work about 1/2 the time.
> Running Radius NT in debug mode, I see the
username/password
> come in to the radius server and see an ACK packet being
> sent back out. According to a Livingston/Lucent tech,
the
> problem is that 1/2 the time the ACK packet comes back
from
> the main IP assigned to the NIC in the NT server (user is
> authenticated). The rest of the time the ACK packet comes
> back showing a secondary address on the NT server (user is
> NOT authenticated since the ACK is coming from an
"unknown"
> server).
>
> I have the same versions of NT (4.0 SP3) and IEA's Radius
> (1.16.60) and the dictionairy file (1.6) an another server
> and it works fine there. The ACK packets always show that
> they are coming from the MAIN IP address assigned to the
> NIC.
>
> I have no idea what would cause this behavior. Can anyone
> clue me in?

Are all of the IPs assigned to the NIC in the same class c?
Its rather difficult to really get to the bottom of the
issue without seeing a full "ipconfig /all" along with
the IPs your terminal server is configured to use.

--Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NTFAQsInternet Solutions for Today |http://www.iea-software.com

----------------------------------------------------------NTISP Mailing List listserver@emerald.iea.com

------=_NextPart_000_0009_01BD5CCC.821D8B60Content-Type: text/plain; name="ipconfig.txt"Content-Transfer-Encoding: 7bitContent-Disposition: attachment; filename="ipconfig.txt"

Windows NT IP Configuration

Host Name . . . . . . . . . : pluto.cyberlink.com DNS Servers . . . . . . . . : 206.64.229.2 206.64.229.7 206.64.228.3 Node Type . . . . . . . . . : Broadcast

NetBIOS Scope ID. . . . . . :

IP Routing Enabled. . . . . : No

WINS Proxy Enabled. . . . . : No

NetBIOS Resolution Uses DNS : No

Ethernet adapter NE20001:

Description . . . . . . . . : Novell 2000 Adapter.

Physical Address. . . . . . : 00-02-67-7A-1D-A2

DHCP Enabled. . . . . . . . : No

IP Address. . . . . . . . . : 208.237.130.254