Cannot connect to a mapped drive from windows 7 professional 64 bit

I have a windows 7 professional, 64 bit client, have mapped drives to two different servers, one is fine to shared drives on a windows 2003 server, the other mapped drives to the 2nd windows 2003 server will not connect.  I have unjoined from the domain, rejoined the domain, logged in as a different user, cannot map the drive to this server.  The only microsoft troubleshoot is to make sure the device can accept print and file connections.

 File Print and sharing is turned on on the windows 2003 server.  I cannot map a drive on any machine in the domain to this shared folder. This was working fine. We added nothing, did nothing to the server nor the workstation and the user cannot connect to the drive.  We need the drive as this is an application server that this users every day.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Emmanuel AdebayoGlobal Windows Infrastructure Engineer - ConsultantCommented:

Can you access the shared by IP?
Can you access the shared by hostname?

Check HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA this should be 1

manch03Author Commented:
No, could not access the shared drive by ip or host name.  It just stopped working.  I had this happen again to a different client machine.  Discovered it was symantec endpoint manager.  uninstalled from the server and everything works.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
manch03Author Commented:
I resolved this issue by removing Symantec Endpoint Manager from the workstation.  This resolved the issue.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.