------=_NextPart_000_004D_01BEE4D5.BDBDEBA0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
According to Ascend, the terminal servers will send all these =
requests any time the server is reset, or if the routing is changed, or =
for that matter if the configuration of the TNT is altered. Well, we =
don't modify our config too often, and we only cycle the power once a =
month on each server, so we can live with that... Anyway, we've created =
all the accounts they told us to create, and the problem persists. They =
said to talk with IEA-Software about it, according to Ascend there are =
others running Emerald Radius that have overcome this problem. Anybody =
seen this?
We've seen it all too often but we didn't find a work around. We got =
the same BS story from Ascend too. Our only workaround was to just =
ignore the entries in the radlogs.
------=_NextPart_000_004D_01BEE4D5.BDBDEBA0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
According to Ascend, the terminal =servers will=20 send all these requests any time the server is reset, or if the =routing is=20 changed, or for that matter if the configuration of the TNT is=20 altered. Well, we don't modify our config too often, and we =only cycle=20 the power once a month on each server, so we can live with =that... =20 Anyway, we've created all the accounts they told us to create, and =the=20 problem persists. They said to talk with IEA-Software about =it,=20 according to Ascend there are others running Emerald Radius that =have=20 overcome this problem. Anybody seen =this?