check your radius secrets?
check your gateway ips?
check your netmasks?
i cant think of any good reson that you are seeing what you are seeing
unless it is radius or dns related or some setting in the pm3 reguarding
pm3 ip setup or radius setup or dns setup in the pm3
On Fri, 2 Jan 1998, Lee Verberne wrote:
>
>
> > ----------
> > From: Lee Verberne[SMTP:NECROMANCER@NET-2000.NET]
> > Sent: Friday, January 02, 1998 6:45:40 AM
> > To: portmaster-users@livingston.com
> > Subject: (PM) duplicate requests
> > Auto forwarded by a Rule
> >
> Hi;
> I have several Livingston (Lucent) PM3's....
> we are trying to reset the IP's for my class 'C'.
> We have diligently read the manual to no avail.
>
> Specificlly, we are getting this error message from Radius when we
> restart everything:
>
> Thu Jan 1 13:52:50 1998: [6042] dropping duplicate request for id 1 from 191.255.249.72
> Thu Jan 1 13:52:55 1998: [6042] dropping duplicate request for id 1 from 206.103.109.149
> Thu Jan 1 13:53:01 1998: [6042] dropping duplicate request for id 1
> from 206.103.109.149
>
> 206.103.109.149 is the IP that we want to change the PM to. I have
> no idea what 191.255.249.72 is.
>
> This problem effectively stops any of our users from logging on
> unless they are in the users table on the PM3. This error message
> will continue until we change the IP back to the original IP. When we
> do change it back to the original IP, it works sometimes. We
> currently only have one PM in operation because of this problem and
> one PM can not nearly support our userbase.
>
> All IPs have been added to the radius clients file and radius has
> been restarted. I even went so far as to reboot the radius server.
>
> One other rather odd thing, When I changed the Ip on the PM using the
> command:
> set ether0 addr 206.103.109.100 (different PM)
> Local (ether0) address changed from 206.103.109.91 to 206.103.109.100
>
> At this point my telnet session was cut off. I tried to ping the
> PM and it didn't reply. I then tried to ping 206.103.109.100 and it
> replied. I was able to telnet to the server at 206.103.109.100, but
> radius was still showing the error message from 206.103.109.91. I
> did not save the settings and I did not reboot. It just changed IP
> addresses. (partially)
>
> We need to get this resolved as soon as possible. Lucent tech support
> is closed through Sunday. Our customers are getting rather angry and
> needless to say, that is not good.
>
> Mike Federico
> Lee Verberne
> Net-2000, Inc.
> -
> To unsubscribe, email 'majordomo@livingston.com' with
> 'unsubscribe portmaster-users' in the body of the message.
> -
> To unsubscribe, email 'majordomo@livingston.com' with
> 'unsubscribe portmaster-users' in the body of the message.
>
Robert H. Hanson
422 West Riverside Cutting Edge Communications, Inc.
Suite #516
Spokane, Wa. 99201 Regional Commercial Internet Service Provider
(509) 444-INET email: roberth@cet.com - http://www.cet.com/
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.