title: What allows a Windows authentication username to work (flow) between 2 servers?
body: <p>Typical ISP setup.  One server is the web server, another is the DB SQL server.  There is a local administrator account, let's say XYZ, created on both machines.  So when I log in remotely, I am either WebServer\XYZ or DBServer\XYZ, depending where I log in.</p>
  
  <p>Now, when I login to SQL Server SSMS on DBServer using Windows Authentication, and execute "SELECT SUSER_NAME()", I get DBServer\XYZ.  That makes sense since it's picking up the fact that I logged in with those credentials.</p>
  
  <p>Now, move over to the WebServer.  I remotely login as WebServer\XYZ. I've installed the SQL client components there.  When I launch SSMS, choose the DBServer, login with Windows Authentication, and execute "SELECT SUSER_NAME()", I somehow get DBSERVER\XYZ, instead of what I would assume should be WebServer\XYZ.  </p>
  
  <p>Somehow, the XYZ from the WebServer becomes the XYZ from the DBServer.  Why is that?  How does that happen?  Surely, it can't just be because the names happen to be the same?</p>
  
  <p>I've heard of trusted domains, but neither machine is a Domain Controller, so I don't have access to that info.  How can I tell if it's trusted or not, without the GUI tools?</p>
  
  <p>The reason I ask the question is because, I'm trying to implement the same thing on my XP laptop (using Virtual PC), so I can imitate the production environment, but I'm not having any luck. </p>