Hello Tunde -
Thanks for sending the files.
It sounds to me like you have a routing problem on the Windows box when it is on a different subnet. I suspect you will need to add a default gateway or perhaps a static route so that the radius requests are sent to the correct place.
regards
Hugh
On Thursday, Jan 9, 2003, at 21:31 Australia/Melbourne, Ayotunde Itayemi wrote:
Hi All, Hi Hugh,
Happy new year.
I seem to be having problems with configuring a NAS on a different subnet from the radius server.
If I put the NAS on the same subnet as radiator, it works fine, but once I put it on another subnet,
it complains that the radius server cannot be located. The NAS is a Windows 2000 server/advanced
server box.
Please find attached my radius.cfg and extract from the radius logfile (trace 4 :-) showing that at least
some packets are reaching the radius server. The ip address of the NAS box when it is not working is
80.247.159.98. When it is working the ip address is 80.247.140.51
I have some other boxes on different subnets (from the radius server) authenticating users against
the same radius server but these NASes are patton RAS boxes.
I have re-installed the Windows box many times but still no luck.
Regards,
Tunde Itayemi.
<radius.cfg><logfile.txt>
-- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence.
=== Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
