problem connecting to server shares

I have a domain with two 2003 servers one of which is the pdc and two windows 2000 server dc

cannot connect to the unc path of the pdc server. eg \\server , I receive the following error

"Logon failure: The target account name is incorrect."

but can connect to the ip address eg \\192.168.0.1

when i ping the name it resolves to the ip address

i have  added the server name to the local host file (no difference)

I have the checked the shares/security of the sysvol folder

have rebooted numerous times along with gpupdate

I have ran ipconfig /flushdns & ipconfig /registerdns

when logged into the pdc I can connect to the unc path on the server itself

there is no time difference between the machines.

I have checked nbtstat - n all seems OK

all client machines have this issue ( again rebooted numerous times )

does anyone have any ideas
gerpaqitAsked:
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.

CIGHNCommented:
Try disabling the windows firewall and see if you can connect...also try setting up the WINS by adding the IP of the other DC as the WINS and also try making sure the DNS server listed is correct. And one more thought...make sure that each of the DNS on each DC have the other DC's listed.
0
eridzoneCommented:
there can be two types of problems

First DNS
check host A record in forward lookup zone

second check following services on PDC, these services must be running to access network shares (most likely for this case)
Computer Browser
Server
Workstation

check also file and printer sharing is enabled on your NIC like in attached image

file-and-printer-sharing.jpg
0
gerpaqitAuthor Commented:
Hi

thanks for the suggestions have taken a look at the dns on all DC's all resolve correctly, I have checked the netbios names from each machine and they all resolve fine.
the windows firewall is disabled with no other third party firewall installed.
all the services mentioned are running also
also file and print is enabled under the NIC properties
again the issue lies with files shared from only 1 server (the pdc emulator)
any other ideas?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

eridzoneCommented:
on which PC you have checked all these ? i am sure it was your PDC

run "net share" on PDC what are the results
0
eridzoneCommented:
it seems like a netbios problem
ping -a servername

nbtstat -a servername, see if there is any conflict. check if you have any duplicate names on your network, there shouldn't be.

if all above is OK and fine then go to this, it will solve your problem

reset your secure channel password of any client machine with respect to your PDC and then try to access by name
On clients those are experiencing this issue, disable the Kerberos Key Distribution Center service (KDC). To do so:

   1. Click Start, point to Programs, click Administrative Tools, and then click Services.
   2. Double-click KDC, set the startup type to Disabled, and then restart the computer.

After the computer restarts, use the Netdom utility to reset the secure channels between these Clients and the PDC Emulator operations master role holder. To do so, run the following command from the domain controllers other than the PDC Emulator operations master role holder:
netdom resetpwd /server:server_name /userd:domain_name\administrator /passwordd:administrator_password
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
eridzoneCommented:
here in netdom command, run this on any of your client
netdom resetpwd /server:server_name(your PDC) /userd:domain_name\administrator(domain admin) /passwordd:administrator_password
0
gerpaqitAuthor Commented:

Ran DCDIAG got this

DC Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial non skippeable tests
   
   Testing server: HQ\ADAM
      Starting test: Connectivity
         ......................... ADAM passed test Connectivity

Doing primary tests
   
   Testing server: HQ\ADAM
      Starting test: Replications
         [Replications Check,ADAM] A recent replication attempt failed:
            From LIMDCFS01 to ADAM
            Naming Context: CN=Schema,CN=Configuration,DC=lys,DC=local
            The replication generated an error (5):
            Access is denied.
            The failure occurred at 2010-04-20 09:47.13.
            The last success occurred at 2010-03-08 09:50.56.
            1037 failures have occurred since the last success.
         [LIMDCFS01] DsBind() failed with error -2146893022,
         The target principal name is incorrect..
         [Replications Check,ADAM] A recent replication attempt failed:
            From LIMDCFS01 to ADAM
            Naming Context: CN=Configuration,DC=lys,DC=local
            The replication generated an error (5):
            Access is denied.
            The failure occurred at 2010-04-20 09:53.15.
            The last success occurred at 2010-03-08 09:50.56.
            6909 failures have occurred since the last success.
         [Replications Check,ADAM] A recent replication attempt failed:
            From LIMDCFS01 to ADAM
            Naming Context: DC=lys,DC=local
            The replication generated an error (5):
            Access is denied.
            The failure occurred at 2010-04-20 10:14.47.
            The last success occurred at 2010-03-08 09:50.56.
            7915 failures have occurred since the last success.
         ......................... ADAM passed test Replications
      Starting test: NCSecDesc
         ......................... ADAM passed test NCSecDesc
      Starting test: NetLogons
         ......................... ADAM passed test NetLogons
      Starting test: Advertising
         ......................... ADAM passed test Advertising
      Starting test: KnowsOfRoleHolders
         Warning: LIMDCFS01 is the Schema Owner, but is not responding to DS RPC Bind.
         [LIMDCFS01] LDAP bind failed with error 31,
         A device attached to the system is not functioning..
         Warning: LIMDCFS01 is the Schema Owner, but is not responding to LDAP Bind.
         Warning: LIMDCFS01 is the Domain Owner, but is not responding to DS RPC Bind.
         Warning: LIMDCFS01 is the Domain Owner, but is not responding to LDAP Bind.
         Warning: LIMDCFS01 is the PDC Owner, but is not responding to DS RPC Bind.
         Warning: LIMDCFS01 is the PDC Owner, but is not responding to LDAP Bind.
         Warning: LIMDCFS01 is the Rid Owner, but is not responding to DS RPC Bind.
         Warning: LIMDCFS01 is the Rid Owner, but is not responding to LDAP Bind.
         Warning: LIMDCFS01 is the Infrastructure Update Owner, but is not responding to DS RPC Bind.
         Warning: LIMDCFS01 is the Infrastructure Update Owner, but is not responding to LDAP Bind.
         ......................... ADAM failed test KnowsOfRoleHolders
      Starting test: RidManager
         [ADAM] DsBindWithCred() failed with error -2146893022. The target principal name is incorrect.
         ......................... ADAM failed test RidManager
      Starting test: MachineAccount
         ......................... ADAM passed test MachineAccount
      Starting test: Services
         ......................... ADAM passed test Services
      Starting test: ObjectsReplicated
         ......................... ADAM passed test ObjectsReplicated
      Starting test: frssysvol
         There are errors after the SYSVOL has been shared.
         The SYSVOL can prevent the AD from starting.
         ......................... ADAM passed test frssysvol
      Starting test: kccevent
         An Warning Event occured.  EventID: 0x800004F1
            Time Generated: 04/20/2010   10:08:40
            (Event String could not be retrieved)
         An Warning Event occured.  EventID: 0x800004F1
            Time Generated: 04/20/2010   10:09:03
            (Event String could not be retrieved)
         An Warning Event occured.  EventID: 0x800004F1
            Time Generated: 04/20/2010   10:09:26
            (Event String could not be retrieved)
         ......................... ADAM failed test kccevent
      Starting test: systemlog
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 04/20/2010   10:10:35
            Event String: Driver Samsung CLP-510 Series required for

         An Error Event occured.  EventID: 0x00000452
            Time Generated: 04/20/2010   10:10:35
            Event String: The printer could not be installed.
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 04/20/2010   10:10:36
            Event String: Driver Adobe PDF Converter required for printer

         An Error Event occured.  EventID: 0x00000452
            Time Generated: 04/20/2010   10:10:36
            Event String: The printer could not be installed.
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 04/20/2010   10:10:36
            Event String: Driver Microsoft XPS Document Writer required for

         An Error Event occured.  EventID: 0x00000452
            Time Generated: 04/20/2010   10:10:36
            Event String: The printer could not be installed.
         ......................... ADAM failed test systemlog
   
   Running enterprise tests on : lys.local
      Starting test: Intersite
         ......................... lys.local passed test Intersite
      Starting test: FsmoCheck
         ......................... lys.local passed test FsmoCheck
0
eridzoneCommented:
i think you should reset the password before condition is more worse.
0
gerpaqitAuthor Commented:
the issue was with the roldes on the server.  i moved all of the roles to one server and demoted the "old PDC to a member server.....all was well after that!
0
gerpaqitAuthor Commented:
thanks for your help!
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
Microsoft Server OS

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.