failed to receive Accounting Response

[tnt at kalik.net]

>If you mean when I type a some command on cisco shell, in the cisco
>console already I show you (much more), else you mean a radius server
>then I must disappoint  you there is a silent, nothing to do!
>
>If you consider for important all debug information on radius when user
>login-run some command-log
>

Yes, radius debug is important. It shows that radius server is sending
Accounting-Response now:

>rad_recv: Accounting-Request packet from host 192.168.255.10 port 1813,
>id=92, length=93
>        NAS-IP-Address = 192.168.255.10
>        NAS-Port = 1
>        NAS-Port-Type = Virtual
>        User-Name = "userA"
>        Calling-Station-Id = "192.168.255.116"
>        Acct-Status-Type = Start
>        Acct-Authentic = RADIUS
>        Service-Type = NAS-Prompt-User
>        Acct-Session-Id = "00000108"
>        Acct-Delay-Time = 0
..
>Sending Accounting-Response of id 92 to 192.168.255.10 port 1813
>Finished request 1.
..
>rad_recv: Accounting-Request packet from host 192.168.255.10 port 1813,
>id=93, length=105
>        NAS-IP-Address = 192.168.255.10
>        NAS-Port = 1
>        NAS-Port-Type = Virtual
>        User-Name = "userA"
>        Calling-Station-Id = "192.168.255.116"
>        Acct-Status-Type = Stop
>        Acct-Authentic = RADIUS
>        Service-Type = NAS-Prompt-User
>        Acct-Session-Id = "00000108"
>        Acct-Terminate-Cause = User-Request
>        Acct-Session-Time = 14
>        Acct-Delay-Time = 0
..
>Sending Accounting-Response of id 93 to 192.168.255.10 port 1813
>Finished request 2.

Time to check firewall and routing and find out why is it not getting
back to the NAS.

Ivan Kalik
Kalik Informatika ISP