<div>
Is there a firewall between the domain servers / computers or on the DCs, GCs, FSMO role servers?<br />
<br />
Take a look at this:<br />
<a href="http://support.microsoft.com/kb/179442" rel="ugc">http://support.microsoft.com/kb/179442</a>
</div>


<div>
Also make sure that each side properly recognizes which DNS(s) are authoritative for the Domain in question. &nbsp;If a system tries to use the wrong DNS to resolve the Account then all you will get is the SID. &nbsp;Generally this would be correct if the Trust is correctly established and should not be anything &quot;extra&quot; that you have to do,...so maybe recreating the Trust like <b>TheGeezer2010</b> said may reveal if there is a problem there.
</div>


<div>
I dont believe the trust to be the issue. I can go on any other system within domain2 and add a user from domain1 without a problem.<br />
<br />
The error appears only one this one machine. Ive thought about removing and readding it to the domain in hopes that would fix it but its a main production database server that I cant easily get a downtime for. Hoping to find a non impacting solution
</div>


<div>
If the trust is not the issue try the following to see if it highlights any problems :-<br />
<br />
Download and install the Support Tools and run the folowing<br />
<br />
dcdiag /s:&lt;DC_Name&gt; /v &gt;c:\dcdiag.txt<br />
<br />
let us know if this throws up any issues. Also does this log anything in the event logs on either your database machine and/or Dcs ?
</div>


<div>
Also I will go ahead and try to reset the trust
</div>


<div>
<u>I dont believe the trust to be the issue. I can go on any other system within domain2 and add a user from domain1 without a problem.</u><br />
<br />
Is this machine using the same DNS in it's TCP/IP specs as the machine that do work?<br />
Is there any other DNS listed on that Nic or on another Nic?<br />
If it has multiple Nic does the correct nic with the correct DNS Server listed as the first Nic in the binding order.<br />
Does the Nic that has the DNS setting using the correct DNS Suffix? &nbsp;Sometimes it is just better to leave that DNS Suffix blank
</div>


<div>
Just a heads up problem fixed. So i went ahead and tried to remake the trust. This did end up being the issue after all. Still confused why one system out of all the rest would have a issue while the rest still worked though.<br />
<br />
<br />
thanks for your help!
</div>


<div>
<div class="content wysiwyg-content">
Ok so I have 2 domains. They have a 2 way trust between them. On one particular system if<br />
&nbsp;I add a user from the first domain over to the second it allows me to do so but once I hit apply<br />
&nbsp;it turns then name into a long SID number and wont allow me to actually connect to the system<br />
&nbsp;from the first domain.<br />
<br />
I can connect to the box from a workgroup or a completely seperate domain without issue.<br />
but when trying to access a share from the trusted domains its a no go. I have no issues on any other<br />
servers in either domain just this one system. The OS is windows 2k3.<br />
<br />
If anyone could please help I would appreciate it. If any more info is needed I can provide<br />
<a href="https://filedb.experts-exchange.com/incoming/2011/07_w29/478045/user-error.jpg" target="_blank" class="file-inline" title="username error (21 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>user-error.jpg</a>
</div>
</div>


user-error.jpg

Ok so I have 2 domains. They have a 2 way trust between them. On one particular system if
 I add a user from the first domain over to the second it allows me to do so but once I hit apply
 it turns then name into a long SID number and wont allow me to actually connect to the system
 from the first domain.

I can connect to the box from a workgroup or a completely seperate domain without issue.
but when trying to access a share from the trusted domains its a no go. I have no issues on any other
servers in either domain just this one system. The OS is windows 2k3.

If anyone could please help I would appreciate it. If any more info is needed I can provide

2 domain trust...when adding a user from one domain to another system shows namw as sid not username

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.

Microsoft Legacy OS

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.