Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We recently had a problem crop up with one of our remote facilities, i'm not a system admin, and we are currently without one, but I will try to explain the best I can.

Employees at the remote site are not able to access some of the servers here with file shares. The remote site connects to our main site here through a Cisco ASA 5505 VPN, the remote site has its own domain controller, DC4, which should be replicating with the DCs at the main site, DC1 and DC5.

All our shared network drives are hosted on a server, FILE1, that is at the main site. Trying to browse to that server using \FILE1 gives the error "Target logon name is incorrect". nslookup and pinging FILE1 from DC4 by both hostname and IP address work, and browsing to the file shares from \ works just fine. There are also some servers which are able to be browsed completely fine by hostname, or IP, and another server that cannot be browsed to by either.

Looking at the event viewer for DC4 at the remote site, there are a lot of Kerberos error 4 listed under the system tab.

Accessing the main DC from DC4 results in the same "Target logon name is incorrect" error, but the reverse works just fine. I can get to file shares on DC4 from DC1 or DC5 at the main site.

DC4 and DC1 are running Windows Server 2003, and DC5 is running Windows Server 2008 R2.

Any help would be GREATLY appreciated!

share|improve this question
Are you sure the servers are replicating OK? I have read a few pages and it seems to narrow down to computer name issues or DC replication.… – Big Chris Jul 23 '14 at 16:23
They may not be. I'll read that post and see what I can find out. – Matt Fogleman Jul 24 '14 at 17:01

You must log in to answer this question.

Browse other questions tagged .