Hi Andrew
Thanks for the advice
have changed the log file from 10% to 1 gig for its autogrowth, autoshrink
is not enabled unless it is enabled by default. it does have a restricted
growth in begabytes currently set at 2,097,152
the database itself is still set at 10 persent but unrestricted. the current
size on disk for these two files are database=47meg log=84meg and that is
with almost a year worth of data so you can see it is not a very busy database
i will monitor it now with the change and see if the problem improves

thanks again
paul

Hi Again Andrew

I think you are misinterpreting NAS for network attached storeage but not in
this case it is Network Access Server as in a big cisco access router with
multiple incoming lines to one ethernet.
as far as the sql goes it is all contained in one machine a windows 2003
server running sql 2005 it is a domain controller and runs dns for dial in
users (this is africa - we still use dial up quite extensively) let me try
give you the whole picture in a frame work you may follow a little easier.

immagine you have a large wide area network with 10 ADSL users in each of
ten towns (100 users) dotted accross the country. each user needs to
authenticate in his closest town so a Network Access Server "NAS" is located
in each of the ten towns. Each access server is connected via the internet to
one central user database or authentication server and requests for access to
the internet are all processed form there respective towns to this one
machine. So as to keep a record of who logged on and when, each request for
access (allowed or rejected) is stored in the sql database wich also runs on
the same central authentication server.
so the records for who logged on and when, from anywhere in the country and
the amount of data they transmitted are all stored here. The access requests
are just that, access request packets and the amount of data they transfer
comes in an accounting packet. All these packets are sent using the standard
RADIUS (Remote Access Dial In User Service) protocol from The NAS to the
authentication server. And this is my problem. I can see the packets arrive
at the server because the event log tells me so but it also (within the same
event) tells me they cannot be handed on to the sql  hence

the log file location. Ensure that the log file location is accessible, has
available space, can be written to, and that the directory or SQL server name
is valid.

The log file being where Windows IAS sends the packet after it has received
it and authenticated the user against the active directory - In our case, SQL

It is still doing it periodically. I set up the profiler and left it running
till an error occured but have not had a chance to examine the results yet (
I am about to)

Hope this helps you to help me and i really appretiate your help

regards paul

PS are you with microsoft or just a group user ?