Unable to access the network

[T Bubbles]

Good afternoon!

Hoping someone can help me as I am in greate need of assistance.

We are running a network with ten computers that are all on Windows 7 Professional SP1. Our server is on Windows Server 2008 SP2 64-bit. On our server we are using Sage Peachtree Complete Accounting 2012. When an end user went to login to Peachtree this morning she received an error message that stated "An error occurred while reconnecting P: to //Servername/Peachtree/Company Microsoft Windows Network. The user cound not be found. The connection has not been restored". When taking a look at the mapped drive in "Computer", it showed a red X on the network drive. I tried to open the mapped drive to access the program files on the server, but after freezing for about 3 minutes I received an error message stating "Windows cannot access //Servername. You have not have permission to access //Servername. Contact your network administrator to request access."

This user is part of the administrator's group. She was out of the office for a couple of days, but it was working fine at the time she left. The system was shut down and not turned on until she returned this morning. Network Discovery is turned on and so is file sharing. She is able to print to the printer that is connected to our server, and able to access the internet. However Peachtree is unreachable due to not network access.

This happened with one other user and we eventually had to re-create his account. The new account worked just fine. I am concerned that it will continue and I will not be able to re-create all of our users.

Any assistance with this would be most appreciated.

Respectfully,

[silvano]

Verify that the account is not locked out, and reset the users' network/windows password.

[Slaters Kustum Machines]

Long shot, but have you checked to make sure her time / date is correct?

[T Bubbles]

I have tried resetting the account and date/time is correct.

[silvano]

Did you try logging in with her credentials from another machine? Remapping drives? Gpudate /force? What all have you tried?

[YeOldeStonecat]

*Can we assume that the server is a domain controller...and is running active directory? And hopefully not in "workgroup mode"?
*Can we assume that the workstations are logging into the domain? Not a local logon?
*If the above is true..the workstations MUST use the LAN IP of their server as their DNS server....not the router, not the ISPs DNS servers, not some public safe DNS like OpenDNS. If they are not using the servers IP for their DNS, active directory will not function for them. I often see the common mistake done of letting the router still run DHCP for the network after a server is put into the network. The server really should do DHCP...and needs to hand out its IP for DNS. The server MUST use itself for the DNS server in TCP properties also, else active directory will not function internally.