Network Access is Denied
 

I have a Snap 4100 - 4.0.860. I have a logon script that maps a few drives to the snap server. After a while, when I click on and drives mapped to the snap server, I get a "Network Access is Denied" error message. It happens on XP and 2000 with different users (I'm an admin, others are plain users). If you reboot the snap or disconnect and then reconnect the mapped drive, it works again. This started happening over the last month or so and I can't for the life of me trace it back to any changes made to the snap configuration or the AD config. We're running 2000 AD and the snap authenticates off of the domain. This problem was happening with SnapOS3 so I upgraded to 4 to see if it would help, but nothing has helped so far. Any ideas?

Re: Network Access is Denied
 

Do you have your server (most likely), or any computer associated with the snap running automatic updates? Microsoft may have slipped one in on you at 3:00 AM that has screwed you up. Just a thought...

Re: Network Access is Denied
 

We do use WSUS. But today for instance, I logged in at 9:00am and by my post at 3:00pm I had gotten the error message. Since I am the lone admin and I have set up all servers for Automatic Updates to reboot around 5:00am, I don't think this is the problem. It's like a timeout. But it doesn't want to recover.

Re: Network Access is Denied
 

It could be possible

As the only fix in .860 was to fix AD and such in 2003 after an MS patch

Re: Network Access is Denied
 

Sounds just like this problem. Except it's happening on 2000 and XP and I'm using a static IP.

http://forums.us.dell.com/supportfor...essage.id=2134

I remember coming across a document that mentioned changing the auto disconnect time in the registry but I can't find it anymore. I thought it mentioned that it had to be done on the server though.

Re: Network Access is Denied
 

If it is an auto disconnect issue, it seems like you would have had it all the time and not just in the past month or so. My thought about that automatic updates wasn't that the computer "just" updated and caused a problem becuse of the update process, but rather that MS released a patch that your server downloaded and that patch is causing the timeout issue. Intertesting problem though...I'll do a little digging of my own and see what I come up with.