Hi..
i have 5pc's in my office on network. networking was going fine but suddenly i got a problem that i cannot access my Server computer. server can access all pc's but no one can access server. i can see server on network but when i tried to access from any other pc it gives this message "Server is not accessible you might not have permission to use this network recourse. Contact with administrator of this server to find out that you have access permission or not. Logon faluire: the user has not been garented the request logon type at this computer."

Please if any one can help me.

If you haven't already, reboot the server. Then try to access it normally from a desktop. Check the event logs for any changes around the time you first noticed this problem. Then check the server resources and see if the authorized users have been deleted or changed. Your desktops' security tokens are being rejected by the server, so you need to find out what changed...

P.S. Also run a full virus scan and spyware scan...look for hacking attempts...from inside your network and outside your network.

HTH

Make sure your primary dns server is the ip address of your server if your running windows 2000 or 2003 server.

Thanx Friends
I try all those things finally i got that there is a Spybot.worm. I install Norton Antivirus and Norton Internet Security it through out the virus and also tell me that there is hacker trying to connect throug internet.

Yeah, i was having the same problem, just about to install nortons and try my luck. here goes

The problem being \\computername is not accessible. and/or your home network gives error "not accessible you might not have permission'Access is Denied. Please contact your system administrator.'

You may get that error if your LSA\restrictanonymous regkey is set to hexadecimal '1', which would be found at

HKLM\SYSTEM\CurrentControlSet\Control\Lsa\restrictanonymous. I set that to evade the common LSA exploit, but it messed up my home network, so I got a firewall and set it back to 0, now everything's fine again, and working properly.