We have 2 domains that are on a 2-way transitive trust. Domain A and B. All users and production servers are on Domain A, while Domain B has servers that are used for development and testing.
To replace a server (Server 2003 R2 - Virtual Source Safe 2005) that was on Domain A, I have built a new server (Server 2003 R2 - Virtual Source Safe 2005) on Domain B . The VSS data is located on a separate partition on the server and the data folder is shared out, with full control, to users on Domain A.
Here's my problem:
The way developers will establish a connection to the share is to map a drive to that share on their local machines (which are logged into Domain A). Then they connect their VSS clients to the share via the drive mapping. However, when they create the mapping and every time they attempt to access the drive, they are prompted to authenticate. Sometimes they can get in and other times they get an error that says the logon was unsuccessful.
This behavior is completely inconsistent but usually they will only be able to login if they use only their domain A username and NOT domaina\username or username@domaina.com
If they restart or log off and log back on to the domain, that mapped drive will show up as disconnected.. so they need to authenticate to it again. The client computers are a mix of XP, Vista and Windows 7. Results are always unpredictable. This was not happening when VSS was installed on the server that was on domain A, which is why I think it could be a domain trust issue.
The firewall is open from the clients on Domain A to the server on Domain B. I have tested by creating another share on another server on domain B and it also does the same thing.
I just don't understand what's happening.. Anybody?
