|
|
|||||||
I have a line in my kixtart script for creating a drive mapping on a server that is not a member of my AD domain. So far it has been working fine, but for some reason it stopped working this morning. Code: use L: /d My DNS entries and WINS entries for the server are working properly. Passwords have not changed. The local user account on WEB-SVR is not disabled. I was able to manually map a network drive using the exact information from the script. Does anyone know if this might be a caching issue or syntax issue? Perhaps there is a better way to map a network drive on a server that is outside and AD domain???? Thanks for any help, Matthew |
||||||||
|
|
|||||||
Perhaps it is an alternate creds issue. Be careful not to "touch" that server with any other creds prior to the mapping. As soon as you touch it, it forges an IPC pipe using those creds, forbidding further access with alternate creds. |
||||||||
|
|
|||||||
Great info Les. Thanks |
||||||||
|
|
|||||||
Solved my problem: I needed to add quotation marks around my domainname\username. I have a '-' in the real server name. I checked the remote server's event log and found that the characters before the '-' were being passed as the user name, not the entire domainname\username combination. Phew!! |
||||||||
|
|
|||||||
But you said it was working fine before this morning... how could that be? |
||||||||
|
|
|||||||
I'm little doubtfull. and have you tried deleting the ipc$ connectiong? that is the last connection that keeps you stuck with the user's own default credentials. |
||||||||
|
|
|||||||
Quick description: There are three domains DomainA, DomainB, DomainC. No trust relationships between any of the domains. My users are in DomainA. Originally this server was in DomainB. About 6 months ago the server was moved to DomainC. The logon script was not changed at that time but still worked even though it referenced a user from DomainB. Last week the script stopped working. No obvious network problems were occuring. I made the changes illustrated in the posts above and the mapping worked again. This time, however, a user account from the local computer was used instead of Domain based user credentials. Also, QUOTES were added around the domain\username due to a unique character being in the server's name. |
||||||||
|
|
|||||||
Might be time to clean up the different domains. Why three domains with the users in one and the servers in another one? |
||||||||
|
|
|||||||
Hmm.... Interesting story. My primary user domain existed before any other domains. Another agency existed with their domain but there was never a reason to share resources. The third domain was created because the idea was that, there would be so many outerlying agencies attaching to the new resource that neither of the existing domains wanted the "alien" presence on their systems. Thus, a third domain was created. However, the project did not mature as planned and no outside agencies joined the project. So, we reengineered the domain structure and moved the resources into the second domain. The third domain is now dismantled and we have to proper communication between the first and second domains now. ... In a nut shell.... |