Re: [ActiveDir] Accessing share

[Sunil Shetty]

Title: Message

Thanks joe for suggestions.   The machine had stored the previous connection session in registry as it restores the share connection when you log in again, i simply disconnected the share and logged the machine again with new user/pass it worked.   Thanks   regards, Sunil Shetty ----- Original Message ----- From: Joe To: [EMAIL PROTECTED] Sent: Tuesday, August 26, 2003 5:52 PM Subject: RE: [ActiveDir] Accessing share This really isn't an AD question and the subnets should have nothing to do with it either. The domain piece is only marginally involved as well.   Basically you are trying to make a NetBIOS connection to a machine that you already have a NetBIOS connection to. The way NetBIOS connects (aka SMB or CIFS) connections work with Windows is that you create an authenticated pipe between machines and then your requests flow through that pipe. You have a couple of options.   1. Break the previously generated connection. You should be able to do this with NET USE * /DELETE. You could also do it by typing NET USE to enumerate your connections and then NET USE DEVICE: /DELETE or NET USER \\machine\share /DELETE depending on how the connection is set up.   2. You can establish a new pipe using one of the other naming formats. This is kind of tricky because you have to know how you are already connected or you have to try the different methods to find how you don't have a connection already. Basically somewhere internally where Windows maintains its session info, its lookup is by machinename supplied, so if you supply a different format for the machine you can generally make another connection. The three main formats are NETBIOS NAME, FQDN, and IP. NetBIOS name is what you normally call your machine when you call it by its name (and you aren't calling it a cuss word) - like for instance the machine I am typing this on is MAINPRO, this name is resolvable via NetBIOS resolution which depending on the PC configuration could be Broadcast, WINS, or LMHOSTS file. The FQDN is the full name with the domain scope attached, again in this example my machine is MAINPRO.JOEHOME.COM, the FQDN is resolvable through normal IP resolution like DNS or HOSTS files or broadcast or the system can also fall back to the NETBIOS methods. Finally you can use the IP address like say 209.247.228.201. The IP address doesn't have to go through much name resolution except to MAC address eventually.   Anyway, if you don't want to break your other pipe because you don't know what you will break, you can attempt to make a connection with one of the other naming formats. Most likely the connection you already have is with the NetBIOS Name. So you can skip that one and try the others. So the different types of connections would look like   NetBIOS Name Connection net use x: \\mainpro\sharename   FQDN Connection net use x: \\mainpro.joehome.com\sharename   IP Connection net use x: \\209.247.228.201\sharename   Hope that helps out. The comical thing about this is that I was just quizzing one of my really good friends about this type of stuff yesterday and I have now totally given out the answer to a question I asked. :o)     joe   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sunil Shetty Sent: Tuesday, August 26, 2003 5:02 AM To: [EMAIL PROTECTED] Subject: [ActiveDir] Accessing share hi all,   I have two machine in different subnet, one is logged into domain controller and the other one is not, and now when i try to access the share of one which is logged into domain controller thru the one which is not in DC, it gives me error - Credentials supplied conflict with existing set of credentials   Any idea, pls suggest.   regards, Sunil Shetty