Cannot map network drives after accedental shutdown of a Win2003 server

We can not map any network drives after windows 2003 server accedentely rebooted.  We also cannot print to share printers.  If i go to the server i can map a drive and print.  But i cannot map a drive nor print from the client machines(WIn XP, VISTA and Win 7)
adnankAsked:
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.

jordanrogCommented:
what role is the server? DC or Print Sever, both, File server. I would check firewall and sharing settings. Are you using a domain or enterprise admin to do things, like map the network drives, on the client machine. Do the drives have permission to domain users to connect to.  I would look at those things.
0
adnankAuthor Commented:
It is DC, File server and Print server and also DNS server.
0
adnankAuthor Commented:
Even domain admin cannot access network drive.
0
Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

cantorisCommented:
If you can map them locally but not remotely, check the firewall.
0
adnankAuthor Commented:
Firewall is off on that server.
0
linrafCommented:
The server has network access out after this problem?
If not, may be a problem with ipsec didn't start because of a port conflict.
http://blogs.technet.com/sbs/archive/2008/07/17/some-services-may-fail-to-start-or-may-not-work-properly-after-installing-ms08-037-951746-and-951748.aspx
0
joenswCommented:
hi
when you try to map drive from client what is the message
 
try net use z: \\servername\sharename   from cmd

0
adnankAuthor Commented:
HI,
Symantec network protection was blocking the network connection.  As soon as i stop the only network protection, I was able to access network drive and printers.
0

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
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 Networking

From novice to tech pro — start learning today.