UNC + IP connections to local host + remote host fails.

I have a windows 2008 R2 server. I can ping all the other servers in the domain but if I do a \\computername\share I get a "windows cannot access \\computername\share"

- Nslookup for the computer DNS name comes back fine.

- Pinging the computer comes back fine

- \\localhost\c$ gives me the same error, going by IP instead of UNC also fails

- Net share shows that the C$, IPC$ and ADMIN$ are all shared out

- Other servers in the domain are able to connect to shares on the server in question without problems.

- Windows firewall is off as well

Because of this problem  I can't update group policy either on the server. It can't connect to SYSVOL

I've looked but i can't find a solution anywhere

group policy
iamuserAsked:
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.

Amitabh SinghAWS Certified Solution Architect | L3 IT Specialist for CloudCommented:
0
iamuserAuthor Commented:
I did see the document but I'm not looking to install additional software. I want to fix the problem I'm having right now.
0
David AtkinTechnical DirectorCommented:
Hello,

Any AD related errors in the event logs?  

Do a dcdiag to see if there are any errors.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

iamuserAuthor Commented:
I have not seen any errors in AD related to this server. When this problem started I thought it was because it was due to a bad policy in the OU that this server was in. I moved it to the default "computer" OU hoping that this problem would be resolved. It was only then that i realized that Group Policy wasn't being processed correctly. The group policy that's failing is the default group policy. But this policy works because the other servers have no problems applying it. Error below

The processing of Group policy failed. Windows attempted to read the file \\domain\sysvol\domain\policies\guid\gpt.ini from domain controller and was not successful.

I know gp fails because it can't s see that share on the DC
0
iamuserAuthor Commented:
so the problem is I can't update GP to see if it's a GP issue because the server can't see any network shares. But other servers can connect to this server via network share.
0
iamuserAuthor Commented:
It's been resolved. I found the problem. TCP/IP HELPER was turned off and disabled. Once i turned it back on I was able to get to network shares again.
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
iamuserAuthor Commented:
I found answer myself
0
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
Active Directory

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.